OpenNap is an open SOURCE Napster clone and facilitates the exchange of files between different users in the Internet. OpenNap offers same basic functionality as Napster servers at that time, in addition the search for files, UP and Download of files, of files of another user and a Chat function belongs both between two individual users and on basis of public areas. Besides it is to be connected possible several servers with one another, around more Clients with one another to left.
OpenNap is a command line program without graphic user surface and can on many pos-ix-conformal systems be begun (e.g. Linux, Unix or BSD). Also Windows is supported. Because it concerns free software, everyone can put a server on. Since at the end of of 2001 is not however any longer developed OpenNap (S. history).
Apart from the basic functions of Napster also new was added. Like that it is for example possible not to only exchange MP3-Dateien but arbitrary file types. The was extended in such a manner that there are users with special rights for Chat areas (similar as with IRC).
Despite into the years the concept come, OpenNap enjoys and its descendants of still very large popularity. A list of active servers could be called up long time with Napigator. Since at the end of April 2004 does not exist this service however any longer, why two new (of private people operated) developed (www.naplist.com and www.gotnap.com).
The project OpenNap was registered in January 2000 with Sourceforge of drscholl. The Napster minutes was determined and published thereby by Reverse engineering. The made possible that different Clients could be written. These could participate also in the original Napster net.
StreamCast network, Inc. some professional servers maintained MusicCity during the OpenNap boom, which could administer users up to 20000 with the name. In April 2001 these were taken however by the net and short time on it was started the Peer2Peer-Client Morpheus, which was very popular some time and originally used the nearly TRACK net.
After drscholl problems with the RIAA had gotten and the servers, which it had used for test purposes, were closed, he resigned to at the end of of 2001 and stopped the development of OpenNap.
The most important Clients (beside the official Client) was for Windows file navigator, audio gnomes and WinMX, for Linux TekNap, GNapster and Lopster, and on basis of Java XNap. Most of it are not any longer developed already longer time. The only Clients, those of it to be still developed is WinMX, Lopster and XNap.
Following description applies also to (not existing any longer) the original Napster minutes.
The OpenNap network possesses a classical star topology. There is a central server, which serves all Clients. An extension of the fact is that several servers can be interconnected, so that the load is distributed on different computers. The inquiries of a Clients are then passed on to the other servers and the result to the Client is returned the delivery.
Approved files are indicated on the server. That means that a Client sends a list of these files to logging in to the server. Thereby arbitrary file types are supported. If a user starts a search, then this is handed over to the server, which thereupon its current data base pulls to rate. The results are conveyed to the Client including IP address of the possessing user. If a Download is to be started, a part of handshake is completed over the server and manufactured if the Download is only permitted to the file by the owner, a direct connection between the parties involved.
One of the large disadvantages from OpenNap is that there are no check totals or Hash values for files (although minutes plan MD5-Summen, what is also implemented, but it was practically never used). The consequence is that with file transmissions errors can occur, which remain unnoticed.
Broken off Downloads can be continued (resume). This means automatically that simultaneous shop of a file of several sources is possible. One the Clients, which implements this, is Lopster.
Communication between servers and Client touches down on TCP/IP and over instructions is completed, which consist of a binary head and an ASCII trunk. The head contains two unsigned, integral 16-bit of values in the Little Endian format. The first value specifies the length of the trunk and second the kind of the instruction.
| Head | Trunk | |
| Length | ID | Arguments by blanks separately |
| 16-bit | 16-bit | ASCII data of the length as in the head defines |
The trunk becomes -- dependent on the kind of the instruction -- when serial connection of arguments, which are separated by blank (0x32), interprets. Arguments, even the blank contained can become (like for example file names) from stating lines enclosed.
The minutes specification does not limit the size of the approved files. At present it is limited however both by the server and Clientimplementierungen on 32 and/or 31 bits (4 give and/or 2 give).
One finds a relatively exact specification of minutes on the homepage of the server implementations.
Since are a few server originated in to 2001, which uses the last version of OpenNap as basis. The most well-known of it is OpenNap NG. The most important innovation is that communication between servers and Client can be compressed around range to save and so more Clients serve.
SlavaNap is a server for the operating system Windows with a graphic surface. It possesses the same functionality in the reason as OpenNap. SlavaNap was developed up to the version 2.3.0 under the GNU general Public License, is meanwhile however Closed SOURCE. Nevertheless it is today the by far usually-used server.
CleanNap is an platform-independent implementation in the alpha stage, whose development was again taken up in June 2004. According to homepage it was reset in July 2004.
We found here 4 related websites.
Index | Privacy | Terms Of Use | Sitemap | Feedback