Gnutella Forums - Bandwidth Optimisations of Gnutella Protocol

Firstly - please note that I am not a programmer and may be aware of all the things that can be done with the Gnutella protocol.

I run an ISP in NZ and we have the problem currently that filesharing is using up a significant portion of our expensive International Link.
We can slow down filesharing protocols, but then our users complain.

If there was a way for our users to prefer downloads from each other, and then other users in NZ, and then lastly from overseas sites it would improve download speeds for users, save us money and ultimately increase the value of filesharing.

My ideas would be:
- A user on our system logs onto the Gnutella network and searches for a file
- If another user on our ISP is logged on and has that file, then that file is preferred - and hence the transfer costs us no money and is fast to download for the user
- Other files are then given as options in the search from other ISP's in NZ, and then lastly from overseas - but these are lower down the list.
- If the file is downloded from another ISP in NZ - similar benefit although the capacity does cost us something (connection to peering points etc)
- If the file has to be downloaded from overseas, then it would be great if we could 'cache' that file on a central server on our network, so that next time the file is downloaded either we or another user can serve it up.
- this would save significant bandwidth on files such as the latest ******* ****** song being downloaded, because it should only come down once on our International link - instead of almost every time as it is now.

is there any way of setting up a system so that we could say re-direct the DNS for router.limewire.com and then prefer local requests and also is there any way to cache PTP traffic? - or at least provide a local peer with lots of popular files....