Robin's Wiki
SearchWiki

iRATE

  • iRATE Homepage
  • Developer Notes

Documentation

  • Current Client/Server Protocol
  • XML-RPC iRATE protocol
  • External Control Plugin protocol
  • iRATE Manual

Supporting Programs

  • External Control Programs
  • Use mpg321 instead of madplay
  1. iRATE
    1. Homepage
    2. Developer page
    3. Developer wiki

  1. Protocols
    1. Current client/server
    2. XML-RPC
    3. External Control plugin

  1. Other Programs
    1. External Control programs
    2. Using mpg321 instead of madplay
IrateDev/
IrateAPI
Read PageEdit PagePage AttributesPage HistoryUpload
Printable View

The iRate server / client protocol is http-like.

Two headers are used :

  • Content-Length which is expected to have an integer containing the length in bytes of the following XML document (not compressed);
  • Content-Encoding which should be gzip.

The data stream should be a real gzip file, with gzip headers.

The default listening port is 2278. Headers are case-sensitive. Lines are ended using network standard CRLF.

When a client connects to the server it is expected to send a header and an xml-like message. The server will respond by either closing the connection or returning an xml-like message.

Both client and server exchange a TrackDatabase XML document.

Page last modified on January 12, 2005, at 02:50 AM

  1. ▲ Top ▲
  2. Edit:
  3. SideBar
  4. MenuBar
  5. BottomBar
  6. GroupHeader
  7. GroupFooter