I really had a horrible experience sometime back, while downloading a software of around 2 GB. Where a network would die down and chrome would discard the partial download.
I ran a site a couple of years ago that did this very thing, but it was quickly overwhelmed with illegal content..
There are 'downloaders' to deal with this kind of issue. That said, torrents are most optimal for a non-stable network connection.
Me too. And it was _Apple_ providing the download, for crissakes.
Tim Cook, is that you? (I don't think Tim Cook would do that).
Bittorrent support is a legacy feature; I don't think I've seen Amazon advertise it for several years.
It seems like an arbitrary limit, but an adequate one for the time being.
If (for whatever reason) you choose to use S3 as your tracker, then you just need to commit to breaking your >5GB content lumps up into multiple pieces.
I have 60gb files in S3, and saturating available bandwidth to download them in a reasonable time frame if they're not in the same country is actually a bit of a challenge.
Bit torrent would be one of the fastest and fault tolerant ways to retrieve the files, so it not being available stings a bit.
While I'm trying to download large files on consumer internet, I'd imagine that huge files between geographic locations and server grade connections would face a similar problem.
The torrent library to use is libtorrent.
It works well if you're on a non-throttled network and has support for local peer discovery which is great for testing (install from a local torrent seed, or another device). Apart from bandwidth saving it's also very convenient to let libtorrent handle consistency checks and resuming of transfers.
ipfs looks interesting, have you published your port?
[0] http://web.archive.org/web/20060421112025/http://docs.amazon...
https://noisemore.wordpress.com/2006/03/14/amazon-s3-has-bit...
Tried it with a few clients: Transmission does not seem to work, though (both web client, and GTK): "Tracker gave HTTP response code 404..."; rtorrent seems to be able to download (but looks like no upload?); deluge downloads well and also kickstarts the transmission clients.
I wonder what's unacceptable in the Amazon infrastructure for transmission... And the 80kb/s max seed rate mentioned in the comments might be a showstopper already.
Unless you have a bunch of seeds, that are essentially permanent, it's pretty useless.
Javascript is disabled or is unavailable in your browser. To use the AWS Documentation, Javascript must be enabled.
...really? Their documentation is perfectly readable without it. All the links are real, bookmarkable links; even the buttons for the PDF, forums, and Kindle version work.
Does anyone have a link that explains why browsers won't do this, or at least a brief explanation?
