GetRight was already able to download the same file from several HTTP/FTP mirrors at once, a feature common in many download managers. So a client would use all that to build a url: For the case of Multi-File torrents, the 'url-list' should be a root folder where a client could add the same "name" and "path/file" to create the URL for the request.Ĥ:infod5:filesld6:lengthi949e4:pathl10: Readme.txte torrent info section to make a folder, then use the "path/file" items from the info section within that folder. Normally, BitTorrent clients use the "name" from the. And I've read that they added WebSeeding, apparently using this method!įor Multi-File torrents, this gets a bit more interesting. torrent files from did include a http seed in this way. This should make it easier on Torrent generators and let them treat this field same for single file and multi-file torrents. If the "url-list" URL ends in a slash, " /" the client should add the "name" from the torrent to make the full URL. 'url-list' = either a single item or a list of normal URLs.įor example (on multiple lines for readability): torrent metadata file but not part of the "info" section. I always think it's a good sign if something can be done without making anybody else change anything! torrent file as well as any mirrors you want. It just takes more clicking for a user.with GetRight, you have to click on the. torrent format was extended to include just a list of mirrors, it can be done without any changes to either the. Requires people other than BitTorrent client authors to do something :) Since just about every HTTP/FTP server already allows resuming, all existing servers can be used without any changes with the method GetRight is using. I've seen another HTTP Seeding proposal.Some small changes to the piece selection methods can really reduce the number of connections and restarts needed on the HTTP/FTP side.Compared to the size of a file, the overhead for the extra bit in the.And clients that don't recognize it would still get the benefit from peers able to send them pieces originally from a HTTP/FTP server.
It doesn't break or change anything for clients that don't recognize it.And that's not even using the "acceleration" in GetRight to download from multiple HTTP/FTP servers at once. I frequently get a download rate from a single HTTP/FTP server that is faster than a BitTorrent download with many peers and seeds (and far faster than any single peer). It sometimes can take awhile to get a full piece so the There's always an "unchoked seed" where anybody can get started.There are several advantages to this to this addition: Why shouldn't a BitTorrent client be able to download fromĮither source, putting all the parts together into one complete file (and even sharing out the pieces it gets from other sources to
Many websites that list a BitTorrent™ download also list a plain old HTTP or FTP link for the same file for those people
0 kommentar(er)
