| MLDonkey | |
| Programming Language: | OCaml, with some C and assembly |
| Operating System: | Microsoft Windows, OS X, Unix-like, MorphOS |
| Genre: | P2P file sharing |
| License: | GPL-2.0-or-later |
MLDonkey is an open-source, multi-protocol, peer-to-peer file sharing application that runs as a back-end server application on many platforms. It can be controlled through a user interface provided by one of many separate front-ends, including a Web interface, telnet interface and over a dozen native client programs.
Originally a Linux client for the eDonkey protocol, it now runs on many flavors of Unix-like, OS X, Microsoft Windows and MorphOS and supports numerous peer-to-peer protocols.
It is written in OCaml, with some C and some assembly.
Development of the software began in late 2001. The original developer of MLDonkey is Fabrice Le Fessant from INRIA. It was originally conceived as an effort to spread the use of OCaml in the open source community.[1]
In January 2003, Slyck.com reported brief friction between MLDonkey developers and the official Overnet MetaMachine developers, which denounced MLDonkey as a "rogue client", allegedly for incorrect behavior on the network.[2]
Versions before 3.0 have a known security vulnerability that allows an attacker with access to the web interface to read any file on the file system.[3]
Features of MLdonkey core:
Written in the OCaml programming language and licensed under the GPL-2.0-or-later license, the application separates the user interface (which can be a web browser, telnet, or a third-party GUI application) and the code that interacts with the peer-to-peer networks.
MLDonkey is able to connect simultaneously to different peers using different network protocols. In addition it can download and merge parts of one file from different network protocols[4] although this feature is currently documented as experimental. MLDonkey runs in a terminal session and does not require a GUI environment, saving memory and processing resources. Behavior is controlled by editable configuration files, or—in a more user friendly fashion—from a separate user interface.
From release 2.9.0 (2007) on, support for gnutella and G2 are no longer compiled in by default as both plugins are buggy and currently unmaintained;[5] however, it is still possible to compile them in by making the appropriate setting in the configuration file.[6]
General references