- Home
- XNapster
- Forum

- contact
- team

- Latest

- eCoupons

MyNapster 3.4.3

MyNapster 3.4.3 for Win32. Source code Project Page

Connects to the Gnutella Network for file sharing
Connects to for chatting
Supports Resume and Multithreaded downloading
Automatic updates
Bandwidth limiting
Share and Download any file type
Resume transfers
Network graph

MyNapster Webclient 1.0, it's a web interface into the MyNapster/Napster/Opennap Networks


Important: Do NOT use this webclient on public server. It is for personal use only. In addition it promotes leeching and not sharing. Servers running WebNap have been hammering MyNapster and have been banned.

Lincoln Stein has also written a Perl client and documentation explaining the Napster protocol. Check out: MP3-Napster-0.96.tar.gz

"The Napster protocol is asynchronous, meaning that it is event-oriented. After connecting to a Napster server, your program will begin receiving a stream of events which you are free to act on or ignore. Examples of events include PUBLIC_MESSAGE_RECVD, received when another user sends a public message to a channel, and USER_JOINS, sent when a user joins a channel. You may install code subroutines called "callbacks" in order to intercept and act on certain events. Many events are also handled internally by the module. It is also possible to issue a command to the Napster server and then wait up to a predetermined period of time for a particular event or set of events to be returned.

Because of its asynchronous operation MP3::Napster makes heavy use of Perl's Thread class. You must have a version of Perl built with the USE_THREADS compile-time option. At build and install time, MP3::Napster will check this for you and refuse to continue unless your version of Perl is threaded. Other prerequisites are Digest::MD5 and MP3::Info (both needed to handle MP3 uploads).

The Napster protocol has a peer-to-peer component. During MP3 upload and download operations between two users, one user's client will initiate a connection to the other. In order for such a connection to succeed, at least one of the clients must be listening for incoming connections on a network port. The MP3::Napster module can do this, either by listening on a hard-coded port, or by selecting a free port automatically. If you are behind a firewall and cannot make a port available for incoming connections, MP3::Napster will be able to exchange files with non-firewalled users, but not with those behind firewalls.

For more information on the Napster protocol, see, or the file "napster.txt" which accompanies this module. This file contains a partial specification of the Napster protocol, as reverse engineered by several Open Source developers."


Copyright @2000-2002 MyNapster
All trademarks are property of their respective owners.
MyNapster is no way affiliated with Napster Inc.