eDonkey2000 (shortened also ed2k) is on the one hand the name of a file sharing net in the Internet, on the other hand the name of the first Clients for this net.
With ed2k both the Peer ton Peer principle, and the Client server principle are used. One calls the software, which is installed from the user to the participation in the net, nevertheless Client.
Originally could Internet user the file sharing net only with the software eDonkey2000 von MetaMachine use. The separation between Overnet, existing first, and eDonkey was waived. 2002 developed from discontent with the original eDonkey2000-Client the eMule project, in order to create an alternative Client on open SOURCE basis. Approximately to this time the trend went to few servers with many Usern from many servers with few Usern too. If still 300-350 servers served 200,000 Clients in May 2002, 2003 60 servers were responsible for 1.5 million Clients in November.
In October 2004 the eDonkey network overhauled the nearly TRACK network in view to the user numbers (heise news), used by KaZaA: 70 servers served 2.5 million Clients. To 14. May 2005 was exceeded the 4-Millionen-Nutzer-Grenze. (slyck news). After the developers on the part of the RIAA with legal means had threatened the original eDonkey software, these stopped the advancement because of missing money for legal counter measures occasionally. In March 2006 the inventor and developer of the network, announced Jed McCaleb, the resumption of the advancement. At this time the network counted about 3.5 million user.
Legal proceeding gave it also against server operators. Thus on 21 February 2006 at the time largest servers "Razorback 2,0 was separated "from the Belgian police from the net. Due to the enormous data set no connecting data on non removable disk were stored, why any information of the large main memory was lost to 16 GB when switching off. To disconnection of the Razorback server a Fakeserver went into enterprise under same name.
With the help of on the left of a server to the server list or a file can be taken up to the Download list of the Clients. The following left show exemplarily their structure:
ed2k-Benutzer can pass this ed2k-Link on to other ed2k-Benutzer, which shows left always to the same file (whereby the file name does not play a role, it is only size and Hash value crucially). Therefore several file names are also often in the circulation, some Clients can to the user a list of the file names found in the net indicate to the same file, so that the user can select one of these file names.
The Client tries to develop a connection to a server. The server software is a program particularly written for this purpose. In principle each Internet user cannot make a ed2k-Server available, this is however for users with Internet tying up under 2 MBit/sec. because of the high network load meaningful.
The operators by ed2k-Servern deviated to use the original server software eDonkey2000 "more dserver". Instead an optimized version of Lugdunum is used "more eserver". Thus for example the user numbers per server, with remained the same range as well as hardware requirements could be substantially increased.
The following communication between Client and servers essentially takes place:
The servers administer thus only one index of the approved files and the pertinent Client addresses. A server stores and sends no files away, but only meta data over the files.
Since the net load of the servers with increasing popularity of the ed2k-Netzwerks continues to rise ever, different concepts were developed, as the servers were to be relieved. In the meantime most Clients in a the position is to compress their data traffic with the server with the help of the zlib library to save and data transmission rate at expense of CCU time in such a way. The probably most radical beginning was however that to convert the eDonkey net to a serverless net. The original ed2k-Entwickler built in addition first a new Client (Overnet), which operated completely without servers with the help of the Kademlia algorithm. As soon as one is connected with another Overnet Client once, one receives a list with Clients, which one can ask on the search for a certain file. If a Client does not have the file (by the way the rule), white it at least, which is topologically closer other Client of the file and can help. Overnet worked well, suffered however from the fact that the search for files went very slowly in front, and a significant part of the range of the Clients as Overhead for the search was lost. One got off the beginning to make eDonkey completely serverless again. A goal was now no more to abolish the servers completely to search but parallel to the server-supported search also serverless and to relieve so the servers. This functionality was integrated as the first into the original eDonkey Client, which became thereby the eDonkey Hybridclient.
In the meantime also the developer team of the most popular Clients, eMule, a Hybridclient in the beta test, has their implementation of the Kademlia algorithm differs however somewhat from that of the eDonkey Clients. In the meantime is this eMule Kademlia Client the official eMule Client.
As soon as a Client was informed by the server about other Clients, he tries to connect itself with these. In the following the Clients Peers is called, since they are posed directly and the ed2k-Server in this part of the data communication plays no more role.
A Peer has a limited number of Upload places (Slots). Each Peer, which requests a file with another Peer, occupies a Slot with this. If all Slots is occupied, the Peers comes into a waiting list (queue) and must wait, until they are to.
The Peers can download a file at the same time of several sources and shorten thus the Download time. At the same time they can send the finished parts away (Chunks) its still running Downloads to other Peers.
We found here 5 related websites.
Index | Privacy | Terms Of Use | Sitemap | Feedback