On Fri, Jan 8, 2010 at 11:22 AM, Gavin Andresen <[email protected]> wrote: > I wanted to learn more about App Engine and the BitTorrent protocols, > and I figured the best way to learn is by doing. So I've created > 'torrent-server'; it lets you: > > Upload arbitrarily large files into the App Engine datastore (using a > command-line python client and the App Engine remote_api, splitting > them up into pieces smaller than the maximum datastore BLOB size). > > Download them using a BitTorrent client that supports the BitTorrent > "webseed" protocols (you can also download directly via HTTP if the > file is smaller than the 10MB App Engine response limit). Downloading > large, popular files this way will save you bandwidth costs, because > the BitTorrent clients will try to get the file from each other first, > and only use your server if they can't find other clients that have > (or are downloading) pieces of the file. > > I also incorporated Allen Porter's "open-tracker" code, so torrent- > server acts as a self-contained BitTorrent serving and tracking > solution. > > Code is available (via svn checkout) at: > http://code.google.com/p/torrent-server/ > You can see it running at: http://torrent-server.appspot.com/
Oh that is fascinating, could definitely cut down on bandwidth costs if they share with each other too. Do you throttle the server so it does not send at max speed so the clients are more apt to get from each other?
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
