![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-12-11 at 00:31 -0600, Rajko M. wrote:
5) More fault tolerant. -I don't need rsync to repair anything with classic methods like wget.
That's not completely true - neither affirmation. Wget can fail, and does sometimes, although rarely. There is no filechecking in the ftp or http download protocol, not of the end result, that is (tcp has package error checking, I understand). Sometimes downloads do get errors. Even with a solid protocol as bittorrent, some people using ktorrent have complained of bad checksum (which other implementations of torrent can correct, by the way - ktorrent bug?) Nor is metalink is more fault tolerant - in my brief experience and understanding -. What it does is a final checksum of the downloaded file, but it has no error correction method embedded. You are left to download again or repair - same as with any other protocol. It is just a convenience that it does an automated final check. It would be more fault tolerant if it could, would, check the download as it progresses and re download the faulty segment - the segment could be big, but it would be better than re-downloading the whole thing. This would serve also to mark servers as "bad" if a second download from them fail again. To be fair, the protocol allows for that. But! 1) the metalinks files we were provided did not contain segment checksum and 2) the available client (aria2c) doesn't support them, anyway (dunno about wxdfast, because it refused to download anything in my system). I would be even nicer if metalink had support for rsync servers and use them to correct the end result automatically. If the idea of the sentence "More fault tolerant" means that it will download from a different server if one fails, well, ok, but I think my above observations nullify that. Either the sentence is qualified, or it is false. So... it _may_ be more fault tolerant, but it isn't, currently.
7) OpenOffice.org uses Metalinks. http://distribution.openoffice.org/p2p/magnet.html I'm removing listed magnet clients from any computer and explain users that they should not install them again. Do you think that anything listed on the same page will gain my trust?
I also don't understand that. :-? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFfq1utTMYHG2NR9URAnq8AJ9k35LXJJtVQ1NUm51buJCQF252CgCfZ5k2 FbuwZ0V4qToBQt0p5OKp1ks= =JfG9 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org