Re: [Mldonkey-users] Questions about the edonkey protocol

[Michael Kroez]

Norbert LATAILLE wrote:

> - Is there a mechanism in mldonkey to accept incoming connections for
> clients who want to upload files - at our request - ? Is this the normal
> behavior in edonkey for queued or firwalled users 

As far as I know the code, mldonkey makes no actual difference between
incoming connections for downloads requested from lowid hosts (the hosts
not reachable directly - only via a Query ID through their server) and
normal upload requests of other hosts.
Mldonkey issues for all incoming connections a QueryFile request (and
gets the reply), a QueryChunks (and gets the reply) and a JoinQueue
(and is queued at lowid hosts - or not...).
The remote host that has started the connection then only accepts
queue requests if it is a lowid host (at least emule does).
Mldonkey does not schedule lowid hosts on a regular base (This could be
possible with the lowid and the server address). It rather requests a
callback (query_id) if indirect sources are received from a server.

Another thing is, that every incoming upload request for a specific file
is not added per default to the direct reachable locations of that file
(their ip and port is given in the body of the connectreq). It only knows
them as a indirect location.
The client location may only be added if it understands the SourcesReq
directive (opcode 250 (0xFA)) (which is not the case for emule) and gives
it self as a source in the SourcesReply.
See this behaviour in read_first_message |ConnectReq (that is the first
protocol behaviour in mldonkey for all incoming connections).

Michael.