Remix.run Logo
pezgrande 7 hours ago

Was the torrent protocol considered at some point? Always surprised how little presence has in the industry considering how good the technology is.

gruez 6 hours ago | parent | next [-]

If you strip out the swarm logic (ie. downloading from multiple peers), you're just left with a protocol that transfers big files via chunks, so there's no reason that'd be faster than any other sort of download manager that supports multi-thread downloads.

https://en.wikipedia.org/wiki/Download_manager

KaiserPro an hour ago | parent | prev | next [-]

Aspera did the chunking and encryption for you, and it looked and acted like SFTP.

The cost of leaking data was/is catastrophic (as in company ending) So paying a bit of money to guarantee that your data was being sent to the right place (point to point) and couldn't leak was a worthwhile tradeoff.

For Point to point transfer torrenting is a lot higher overhead than you want. plus most clients have an anti-leaching setting, so you'd need not only a custom client, but a custom protocol as well.

The idea is sound though, have an index file with and then a list of chunks to pull over multiple TCP connections.

ambicapter 6 hours ago | parent | prev [-]

torrent is great for many-to-one type downloads but I assume GP is talking about single machine to single machine transfers.