napster.txt

P2P NAP的C实现 P2P在网络应用中越来越流行

	<user>

	When a downloading client detects that the uploader's data port
	is unreachable, it should send a 626 message to the server with
	the nick of the user for which the connection failed.  The server
	then relays the message to the uploader, substituing the
	downloader's nickname in the message.

627 (0x273)	operator message [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	client: <text>
	server: <nick> <text>

	client request to send a message to all admins/moderators

628 (0x274)	global message [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	client: <text>
	server: <nick> <text>

	client request send a message to all users

629 (0x275)	banned users [SERVER]

	[NAPSTER]

	Format: <nick>

	when displaying the ban list for the server, this message is used
	to indicate banned nicknames.

630-639 missing

640	direct browse request [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	Client: <nick>
	Server: <nick> [ip port]

	Client: request files for <nick>
	Server: <nick> is requesting your files.  optionally, <ip> and
		<port> are given if the client getting browsed is firewalled

	This message is sent to initiate a direct client to client browsing of
	shared files.

	See section 5.3.

641	direct browse accept [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	Client: <nick>
	Server: <nick> <ip> <port>

	The client to be browsed sends this message back to the server to
	indicate it is willing to accept a direct browse from <nick>.

	The server sends this message to the requestor of the browse to
	indicate where it should connect in order to do a direct browse from
	<nick>.

	See section 5.3

642	direct browse error [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> "message"

	Server sends this messags in response to a 640 request if there is an
	error (eg. both clients are firewalled, or the browsee is not sharing
	any files).

	See section 5.3

643-649	missing

650-651	??? [CLIENT]
	[NAPSTER]

	permission denied.

652 (0x28c)	cloak user [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	sets the current user to "invisible"

653-699	missing.

700	change link speed [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<speed>

	client is notifying server that its correct link speed is <speed>,
	in the range 0-10 (see the login message for details).

701	change user password [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<password>

	client wishes to change their password

702	change email address [CLIENT]

	[NAPSTER,OPENNAP]

	<email address>

	client wishes to change their email address

703	change data port [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<port>

	client is changing the data port being listened on for file
	transfers

704-747	missing.

748	login attempt [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	the server sends this message to a logged in client when another
	client attempts to log in with the same nickname.

749	missing.

750 (0x2ee)	server ping [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

        Format: <time>

        Client pings server. Server replies with 750. <time> is in time_t
	format. Napster console command: "/sping"

	OpenNap uses <server> instead of <time> where <server> is server
	name to ping.

751 (0x2ef)	ping user [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user>

	client is attempting to determine if <user>'s connection is alive

752 (0x2f0)	pong response [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user>

	this message is sent in response to the the 751 (PING) requeset

753 (0x2f1)	change password for another user [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user> <password> "<reason>"

	allows an administrator to change the password for another user

754-769	missing.

770	??? [CLIENT]
	[NAPSTER]

	permission denied.

771	??? [CLIENT]
	[NAPSTER]

	permission denied.

772-799	missing.

800 (0x320)	reload config [CLIENT]

	[NAPSTER,OPENNAP]

	<config variable>

	resets configuration parameter to its default value

801 (0x321)	server version [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	no data.

	client request's a server's version

802-804	missing.

805	???
	[NAPSTER]

	[returns permission denied. -ed]

810 (0x32a)	set config [CLIENT]
	[NAPSTER,OPENNAP]

	<config string>

	request a change in server configuration variables

811 (0x32b)	???	[CLIENT]
	[NAPSTER]

	[returns permission denied. -ed]

820 (0x334)	clear channel [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel>

	remove all users from the specified channel

821 (0x335)	redirect client to another server [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	client: <user> <server> <port>
	server: <server> <port>
	
	This command allows an administrator to redirect clients to another
	server.

822 (0x336)	cycle client [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	client: <user> <metaserver>
	server: <metaserver>

	This commands allows an administrator to make a client restart the
	login process by first connecting to the metaserver (redirector) at
	<host>.

823 (0x337)	set channel level [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <level>

	Sets <channel> such that users must be at least <level> in order to
	enter the channel

824 (0x338)	emote [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	client: <channel> "<text>"
	server: <channel> <user> "<text>"

	A variation of the public message command to indicate an action by
	the user.  Often implemented as the "/me" command in IRC clients.

825 (0x339)	user list entry [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <user> <files shared> <speed>

	an 825 message is sent for each user in the channel specified by the
	830 message

	Example:

	Help testor3 0 3

	[This appears to be exactly the same format as the 408 message.  -ed]

826 (0x33a)	channel limit [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <limit>

	sets the maximum number of users that may enter a channel.  <limit>
	is an integer value between 0 and 999999999.  setting it higher that
	this results in the limit being set to -1.  by default, created
	channels have a limit of 200.  there appears to be no restriction on
	any channel member changing the limit, and no notification is given

827 (0x33b)	show all channels [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	no data.

	client request to show all channels, including "hidden" channels.
	the server also sends this message to terminate

828 (0x33c)	channel list [SERVER]
	
	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <users> <n1> <level> <limit> "<topic>"

	the server sends a list of 828 commands, one for each channel,
	including "hidden" channels that don't show up in the normal channel
	list.

	<level> is the mimimum user level required for entry into a channel
	<limit> is the max number of users allowed in a channel

	<n1> is either 0 or 1.  seems to be 1 if the channel was user
	created, or 0 if a predefined channel???

829 (0x33d)	kick user from channel [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <user> [ "<reason>" ]

830 (0x33e)	list users in channel [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel>

	client requests a list of all users in <channel>.  server responds
	with a 825 response for each user, followed by an 830 response with
	no data [why didn't they just use the 409 message? -ed]

831 (0x33f)	global user list [CLIENT, SERVER]

	[NAPSTER?,OPENNAP,SLAVANAP]

	no data.

	Napster returns "premission denied."
	OpenNap and SlavaNap return sequence of 832 command. List of users
	is terminated with empty 831 command.

832 (0x340)	global user list entry [SERVER]

	[OPENNAP,SLAVANAP]

	<nick> <ip>

	Response to message 831.

833-869	missing.

870	add files by directory [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: "<directory>" "<file>" <md5> <size> <bitrate> <freq> <duration>
	[ ... ]

	This command allows a client to share multiple files in the same
	directory as a shortcut to multiple 100 (share file) commands.
	<directory> is the path which should be prepended to all the given
	filenames in the rest of the command.  <file> is the name of the file
	to share *without* its directory component.  When other clients do a
	browse/share, the real path will be reported as <directory>/<file>.

	The portion of this command after the <directory> may be repeated as
	many times as necessary for files in the same directory. NOTE: most
	servers will not accept commands of length longer than 2048 bytes
	so you still may need to break up the files into multiple commands
	if there are many files in a single directory.

871-899	missing.

900     connection test [SERVER]

	[NAPSTER]

        <ip> <port> <data>

        <ip>   - string,  ip address to connect to.
        <port> - integer, port to connect to
        <data> - string,  data to send to server.

        Try to connect to <ip> on <port> for atmost 1000 seconds.  If the
        connection succeeds send the <data> to target.

	[reported by Thomas van der Heijden <[e-mail]>]

901     listen test [SERVER]

	[NAPSTER]

        <port> <timeout> <data>

        <port>    - integer, port to listen on
        <timeout> - integer, time to wait for connection in seconds
        <data>    - string,  data to send after connection has been made.

        Listen on <port> for <timeout> seconds. If a connection arrives,
        return <data> to sender.

	[reported by Thomas van der Heijden <[e-mail]>]

920	socket test [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <some_digit>

	This is sent by the Beta8+ client prior to login.
	
	SlavaNap server uses this command to detect byte order for big-endian
	clients (SlavaNap supports clients with big-endian and little-endian).

	OpenNap just ignores this command.

931	blocked file [SERVER]

	[NAPSTER,SLAVANAP]

	Format: <md5>

	This message is used by server to inform client
	that file is blocked.
	Used as reply to commands 100, 870, 10300

932	new share [CLIENT]

	[NAPSTER]

	Format: <binary data>

	This message is used by Napster 10.2+ to share
	files that have ID3v2 tags. Format of binary data:
	(C language, int = 4 bytes)

	struct{
		int    real_size; // file size without ID3 tags
		char   unknown1[4];
		char   unknown2[4];
		char   unknown3[4];
		char   unknown4[4];
		int    bitrate;
		int    frequency;
		char   unknown5[4];
		char   unknown6[4];
		char   MD5[32]; // 36-67
		char   unknown7[4];
	};