Re: [Mldonkey-users] 2.02-20 working great!

[MLdonkey]

>  AFAIK this is default for eMules. 

Unfortunately. As I said before, the original protocol did not do
that, and edonkey/overnet/mldonkey clients are not ready for that,
they just don't understand why the blocks they have asked for don't
arrive. This is the kind of change that looks harmless, but that may
have unexpected results. Emule, as mldonkey, is just a guest on the
edonkey network, it can add new features, but it should not change the
existing rules, especially when the official client does not support
them.

> This should help spreading of files. 

I can see how it can help getting credits from more emule clients, ie
you don't want to send too much to one client, since just a small
amount is needed to get a good rank in its queue, but you want to have
a small credit on as many clients as possible. 

For spreading the file, the probability that one client downloads
different chunks is higher than the probability that different clients
download different chunks. I would prefer mirroring the entire file on
another client than pushing different parts of the file (often the
same chunks in fact) on different clients.

> You're disconnected after 1 chunk.  Correct me if I'm wrong.

>From what I've seen, you are not disconnected. Emule just wait for you
to do something. Emule knows what to do. edonkey/overnet/mldonkey
don't know what to do. So, after a timeout, they are
disconnected. That's at least what I have inferred from reading emule
code and from my downloads.

- MLDonkey