Client mode |
![]() |
The client mode of Mserv is a well defined way of communicating with the server. There are two modes for client mode operation: COMPUTER and RTCOMPUTER. COMPUTER and RTCOMPUTER feature exactly the same protocol allowing the client to issue commands and receive answers back in return. In addition to this, the RTCOMPUTER clients also receive real-time asynchronous (unrequested) data. This would typically be information such as newly added tracks to the queue, users connecting and disconnecting etc. This way of communicating things as-they-happen alleviates the requirement for the client to poll the server to see what is new. The protocol is based on a textual line-by-line approach similar to standard protocols such as SMTP, NNTP, HTTP etc. The Mserv protocolConnectionMserv uses a TCP stream connection usually on port 4444. The port assigned to a server may however change at the discretion of the system administrator and as such all clients must be able to change the port they connect to at the request of the user. Once connected you will receive an automatic response, type 200. You should then issue a USER followed by PASS command, indicating in the PASS command whether you will be accepting real-time data. Read these two command specifications later in this document for further information. ResponsesAll responses to commands are formatted in the following way:
THIS DOCUMENTION HAS NOT BEEN FINISHED, THE INFORMATION BELOW IS EXAMPLE ONLYResult codesCode 220
CommandsQUIT
This command requests a graceful termination from the server. You should wait for a response to be received. HELP
This command requests help about a particular command or sub-command, and returns data Written by James Ponder, last updated 12th December 1999 |