-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Sunday 2006-10-22 at 11:03 +0100, Administrator wrote:
> Can you explain what would have been happening in the week when everything
> looked OK but wasn't?
Corruption should not occur: the filename.torrent file contains checksums
of the chunks of the intended download. As chunks get downloaded whose
checksum do not match what is known in advance they should have, those
chunks would get rejected. Perhaps the peers and seers feeding the
old file would get rejected as corrupted.
Or some thing of the sort, but the end result would not be corrupted. The
download might (should) fail, of course, which is a nuisance. Downloading
the new filename.torrent and restarting would get it corrected.
It's a better protocol in this respect than ftp: I have used it to mend
incorrect ftp downloads, for instance.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFFP4C+tTMYHG2NR9URAlzGAJ4iVRT69t0SRPdiqHPmV5M882SJbACfRBJt
MATUdyZ9L1MhEF5oitrP/GU=
=3fi/
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
