napster.txt

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

	Example:

	"random band - random song.mp3" 7d733c1e7419674744768db71bff8bcd-2557521 2558199 128 44100 159 lefty 3437166285 4

	SlavaNap examples:

	request: FILENAME CONTAINS "sunshine"
	possible reply: "c:\MP3\Emma Bunton - Sunshine On A Rainy Day.mp3" 00000000000000000000000000000000 4118494 128 44100 257 CyberAlien 3437166285 6

	request: FILENAME CONTAINS "sunshine" SHOW_QUEUE
	possible reply: "c:\MP3\Emma Bunton - Sunshine On A Rainy Day.mp3" 00000000000000000000000000000000 4118494 128 44100 257 CyberAlien 3437166285 6 n/a
	possible reply: "c:\MP3\Emma Bunton - Sunshine On A Rainy Day.mp3" 00000000000000000000000000000000 4118494 128 44100 257 CyberAlien 3437166285 6 2
	possible reply: "c:\MP3\Emma Bunton - Sunshine On A Rainy Day.mp3" 00000000000000000000000000000000 4118494 128 44100 257 CyberAlien 3437166285 6 -1

	request: FILENAME CONTAINS "sunshine" SHOW_SOFTWARE
	possible reply: "c:\MP3\Emma Bunton - Sunshine On A Rainy Day.mp3" 00000000000000000000000000000000 4118494 128 44100 257 CyberAlien 3437166285 6 "v2.0 BETA 10.4"
	possible reply: "c:\MP3\Emma Bunton - Sunshine On A Rainy Day.mp3" 00000000000000000000000000000000 4118494 128 44100 257 CyberAlien 3437166285 6 CQ_EX

	request: FILENAME CONTAINS "sunshine" SHOW_SOFTWARE SHOW_QUEUE
	possible reply: "c:\MP3\Emma Bunton - Sunshine On A Rainy Day.mp3" 00000000000000000000000000000000 4118494 128 44100 257 CyberAlien 3437166285 6 n/a "v2.0 BETA 10.4"
	possible reply: "c:\MP3\Emma Bunton - Sunshine On A Rainy Day.mp3" 00000000000000000000000000000000 4118494 128 44100 257 CyberAlien 3437166285 6 0 CQ_EX

202 (0xca)	end of search response from server [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: (empty)

203 (0xcb)	download request [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <nick> "<filename>"

	client requests to download <filename> from <nick>.  client expects
	to make an outgoing connection to <nick> on their specified data
	port.

	Example:

	mred "C:\Program Files\Napster\generic cowboy song.mp3"

	SEE ALSO: 500 alternate download request

204 (0xcc)	download ack [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> <ip> <port> "<filename>" <md5> <linespeed>

	server sends this message in response to a 203 request.

	<nick> is the user who has the file
	<ip> is an unsigned long integer representing the ip address
	<port> is the port <nick> is listening on
	<filename> is the file to retrieve
	<md5> is the md5 sum
	<linespeed> is the user's connection speed (see login(2))

	Example:

	lefty 4877911892 6699 "generic band - generic song.mp3" 10fe9e623b1962da85eea61df7ac1f69 3

205 (0xcd)	private message to/from another user [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> <message>

	note the same type is used for a client sending a msg or recieving one

206 (0xce)	get error [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> "<filename>"

	the server sends this message when the file that the user has
	requested to download is unavailable (such as the user is not logged
	in).

207 (0xcf)	add hotlist entry [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <user>

	This message is used to add additional entries to the client's
	hotlist.  The server will send 209 and 210 messages when a user
	on the hotlist has logged in or out, respectively.

208 (0xd0)	hotlist [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <user>

	This message is used to send the initial list of hotlist entries
	during the initial login process.  It is normally send prior to
	to the add file (100) commands.  To add more entries to the hotlist
	after the initial list is sent, clients should use the 207 message
	instead.

209 (0xd1)	user signon [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user> <speed>

	server is notifying client that a user in their hotlist, <user>,
	has signed on the server with link <speed>

210 (0xd2)	user signoff [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user>

	server is notifying client that a user on their hotlist, <user>, has
	signed off the server.

	this message is also sent by the server when the client attempts to
	browse a nonexistent client.

211 (0xd3)	browse a user's files [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick>

	the client sends this message when it wants to get a list of the files
	shared by a specific client

212 (0xd4)	browse response [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> "<filename>" <md5> <size> <bitrate> <frequency> <time>

	<nick> is the user contributing the file
	<filename> is the mp3 file contributed
	<md5> is the has of the mp3 file
	<size> is the file size in bytes
	<bitrate> is the mp3 bitrate in kbps
	<frequence> is the sampling frequency in Hz
	<time> is the play time in seconds

	Example:

	foouser "generic band - generic song.mp3" b92870e0d41bc8e698cf2f0a1ddfeac7 443332 128 44100 60

213 (0xd5)	end of browse list [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<nick> [ip]

	indicates no more entries in the browse list for <user>.  <ip> gives
	the client's IP address.

214 (0xd6)	server stats [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	client: no data
	server: <users> <# files> <size> ["GB" <myfiles>]

	<size> is approximate total library size in gigabytes
	this message is sent by the server occasionaly without request
	"GB" text is added by Napster server since version 10.3
	<myfiles> is number of files shared by user.

	Example:

	old:  553 64692 254
	new:  553 64692 254 GB 102

215 (0xd7)	request resume [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<checksum> <filesize>

	client is requesting a list of all users which have the file with
	the characteristics.  the server responds with a list of 216 messages
	for each match, followed by a 217 message to terminate the list

216 (0xd8)	resume search response [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user> <ip> <port> <filename> <checksum> <size> <speed>

	this message contains the matches for the resume request (215).  the
	list is terminated by a 217 message.

217 (0xd9)	end of resume search list [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	no data.

	this messag terminates a list of 216 messages initiated by a 215
	client request

218 (0xda)	downloading file [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	no body.

	client sends this message to the server to indicate they are in the
	process of downloading a file.  this adds 1 to the download count
	which the server maintains.

219 (0xdb)	download complete [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	no body.

	client sends this message to the server to indicate they have
	completed the file for which a prior 218 message was sent.  this
	subtracts one from the download count the server maintains

220 (0xdc)	uploading file [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	no body.

	client sends this message to indicate they are uploading a file.
	this adds one to the upload count maintained by the server.

221 (0xdd)	upload complete [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	no body.

	client sends this message when they are finished uploading a file.
	this subtracts one from the upload count maintained by the server.

300 (0x12c)	optional ports [CLIENT]

	[NAPSTER]

	<port>

	This command allows the client to specify optional ports to try for
	data connections if the one currently in use is unreachable by other
	parties. Ignored by OpenNap and SlavaNap.

301 (0x12d)	hotlist ack [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <user>

	server is notifying client that <user> has successfully be added to
	their hotlist

302 (0x12e)	hotlist error [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <user>

	server is notifying client that it was unable to add <user> to their
	hotlist.  [can you only add registered nicks to your hotlist? -ed]

303 (0x12f)	remove user from hotlist [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	Format: <user>

	client is notifying the server that it no longer wishes to request
	notifications about <user> when they sign on or off the server.  no
	response is sent in return.

310	??? [CLIENT, SERVER]

	[NAPSTER]

	client: no data
	server: 0

	unknown command.  server returns 0 regardless of any parameters

316	client disconnect??? [CLIENT, SERVER]

	[NAPSTER,OPENNAP]

	client: no data
	server: 0

	The server sends this message with a value of `0' when the client is
	about to be disconnected.

	It is unkonwn what this command does when issued by the client.  The
	server appears to send the 316 message without disconnected the client
	in this case.

	[the server seems to send this message if you send it a numeric
	greater than 1000.  the server will also disconnect you after
	sending this message.  -ed]

320 (0x140)	user ignore list [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	client: no data
	server: <count>

	client request to display the list of ignored users.
	server returns the number of users being ignored

321 (0x141)	user ignore list entry [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user>

	server sends each ignored nick in response to a 320 request.  the
	list is terminated by a 320 message with the number of ignored users.

322 (0x142)	add user to ignore list [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user>

	server acks the request by returning the nick

323 (0x143)	remove user from ignore list [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user>

	server acks the request by returning the nick to be removed from
	the ignore list.

324 (0x144)	user is not ignored [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user>

	server indicates that <user> is not currently ignored in response to
	a 323 request.

325 (0x145)	user is already ignored [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<user>

	server indicates the specified user is already on the user's ignore
	list

326 (0x146)	clear ignore list [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	client: no data.
	server: <count>

	client requests the server clear its ignore list.  server returns the
	number of entries removed from the ignore list.

330 (0x14a)	blocked ip list [CLIENT]
	[NAPSTER]

332 (0x14c)	block ip [CLIENT]
	[NAPSTER]

333 (0x14d)	unblock ip [CLIENT]
	[NAPSTER]

400 (0x190)	join channel [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel-name>

	the client sends this command to join a channel

401 (0x191)	part channel [CLIENT, SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel-name>

	The client sends this command to part a channel.  Server sends this
	message to indicate that the client has parted the channel.  Note
	that this is sometimes sent even when the client has not requested,
	so a client _must_ be prepared to accept it at any time.

402 (0x192)	send public message [CLIENT]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <message>

403 (0x193)	public message [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <nick> <text>

	this message is sent by the server when a client sends a public message
	to a channel.

	Example:

	80's espinozaf hello...hola

404 (0x194)	error message [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<text>

	This message is used to send general error messages to a client that
	is logged in.  Note: Message 0 is only sent during the login process.

	Examples:

	User nosuchuser is not currently online.
	Channel #nosuchchannel does not exist!
	permission denied
	ping failed, blah is not online

405 (0x195)	join acknowledge [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel>

	the server sends this message to the client to acknowlege that it
	has joined the requested channel (400)
	Note: <channel> in this message can be different from one sent in 400
	and client must be ready to join another channel instead of requested.
	
406 (0x196)	join message [SERVER]

	[NAPSTER,OPENNAP,SLAVANAP]

	<channel> <user> <sharing> <link-type>

	<user> has joined <channel>

	Example:

	80's WilmaFlinstone 12 2

407 (0x197)	user parted channel [SERVER]