On 07/27/10 09:51 AM, mda_ wrote:
One possibility is we could split the file, then you download each part
separately. Then the md5 checksum of each part could be checked individually. If
one gets corrupted, only that part would need to be downloaded again. You would
of course need to rebuild the constituent parts.
It may be easier to enable a bittorrent server on a mirror. A good
client will recompute all the chunks' hashes (message digests) upon
restart if a power failure should occur. Hopefully the protocol is
not prohibited by your ISP or jurisdiction.
http://en.wikipedia.org/wiki/BitTorrent_(protocol)#Creating_and_publishing_torrents
Cheers,
Don
Possibly, but that's more hassle in the short term. I don't know what's
involved. In any case, I can't do it as I don't control the server.
In contrast, I can split the files in a few minutes and compute the checksums of
each part and stick them in a directory of my own. But it would be useful to
know what the end user considers a reasonable size, based on how much he
disconnects.
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
