View Image

MLDonkey was originally intended as a pure eDonkey2000 clone, a sector that the original client never served well. Since the release of version 2, there has also been development to access other networks, most notably the eDonkey2000 offspring Overnet, BitTorrent, Kademlia and DirectConnect.

The history of MLDonkey has been lined with controversy, mostly based on the fact that the original Overnet client has always been proprietary, in terms of source code as well as transfer protocol. This has forced the MLDonkey developers to reverse engineer the basic mechanisms, but they didn't stop at that. In many cases, new functionality has been introduced, sometimes great and sometimes questionable.

The first controversy was regarding servers. MLDonkey introduced a method to connect to several servers simultaneously, thereby increasing search efficiency greatly. This was at a time when servers were relatively small, and already strained (mainly by bots). Too many users, too few servers, new solutions needed.

Later on, certain pretentious server admins became more and more interested in the numbers of users assigned to their servers, rather than in the efficiency of the network. This meant that a client connecting to more than one server was a threat to their internal "high score" competition of served users.

Complaints started to come in from eDonkey users about MLDonkey being too efficient, i.e. utilizing an unfair amount of network resources. This probably has to do with the extreme reluctance of the developers of eDonkey2000 to improve their product, which led to larger and larger servers, instead of following the approach MLDonkey stood for: increasing the connectivity of the network as a whole. But, then again, making the eDonkey2000 network too efficient would probably not be in line with the plans to develop the Overnet, which is indeed a high connectivity serverless network.

MLDonkey also featured a way to exchange file sources between clients, thereby making the servers less important, of course another threat to the pride of the server admins. Soon, a strange alliance was formed by the developer of the popular Lugdunum server and MetaMachine, the eDonkey2000 development company. This resulted in a long series of attempts to ban MLDonkey, bans which were easily worked around, and due to the nature of open source projects, also easy to deploy among users.

It is important to note that, being an open source project, the MLDonkey team have always offered their solutions to the original developers, as well as the rest of the community. This courtesy has never been returned, even though numerous pleas have been forwarded; MetaMachine insists on keeping their code and protocols proprietary.

Features:

* 100% Open Source, GPL license
* runs on Linux, Unix, Solaris, MacOSX, MorphOS and Windows
* The p2p core can run on a resource limited headless computer, with remote GUI clients accessing it over the network.
o The core is built to run as daemon for days, weeks, ever...
* Several different GUIs available, some of them developed separately.
* Multi-user support: the same core can queue and process downloads for several different users who can't see what the others are downloading.
* Several different file-sharing networks supported:
o ED2K (and Kademlia and Overnet)
o BitTorrent
o DC++
o (FastTrack, SoulSeek, Gnutella and G2 need work)
* The core can download the same file from several different networks simultaneously.
* Scriptable command-line interface available. It's possible to control all aspects of mldonkey from the CLI.
* Written in ObjectiveCaml, with some parts written in C and some in Assembly.