Hi,
thanks for your quick reaction
I would like to propose something regarding ET_COMPATIBLECLIENT?
AFAIK
cDonkey uses 1
lMule uses 2 (opcode 0x26 - working)
xMule uses 2 (opcode 0x30 - not working)
aMule uses 3 (opcode 0x30, now 0x26 - working, but not yet seen here :wink:)
Shareaza uses 4 (Hint: missing in BaseClient.cpp :wink: )
MLDonkey uses 10 (new in CVS, donkeyMain.ml, line 144)
Every day clients with flag 2 and opcode 0x26 connect to my MLDonkey,
from what I have written above I suggest they are all lMules.
From what I have read the xMule dev takes some improvements from
aMule and imports them into his source code. I will post this also on the
xMule forum but maybe you have also contact to him.
To better distinguish between lMule and xMule - which was yet impossible
because of opcode 0x30 - xMule should use flag 5.
What do you think about that?
Greetings, spiralvoice