Enrico Minack
2004-Aug-06 14:57 UTC
[icecast-dev] official communication protocol definition / documentation?
Hello, I am looking for a documentation of the communication protocolls icecast is capable of: ICY, XAUDIOCAST and a modified HTTP. In order to write client software being capable of all available features I was searching on the net for those documentations but no luck so far. How come? Isn't this protocoll documented? How does the developer team know what options and functins are available in the protocoll? Just by the already written code? I'd appreciate some hints, regards, Enrico M. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Michael Smith
2004-Aug-06 14:57 UTC
[icecast-dev] official communication protocol definition / documentation?
On Sunday 08 February 2004 18:19, Enrico Minack wrote:> Hello, > > I am looking for a documentation of the communication protocolls icecast is > capable of: ICY, XAUDIOCAST and a modified HTTP. In order to write client > software being capable of all available features I was searching on the net > for those documentations but no luck so far. How come? Isn't this protocoll > documented? How does the developer team know what options and functins are > available in the protocoll? Just by the already written code? >We should fully document our main source protocol - which is a slightly modified HTTP, but haven't. Sorry about that. I'll cover it later in this email. The other protocols are supported solely for backwards compatibility with older systems - you should refer to documentation for those systems for protocol details. For icecast 2, the primary source protocol is HTTP, with one modification: a new HTTP method, "SOURCE", is introduced. When a SOURCE request is received, icecast2 adds the incoming stream as a mountpoint using the request-URI in the SOURCE request. The request must be authenticated using HTTP BASIC auth. That's all there it to it! There's also some stuff for compatibility with other systems (icecast 1.x, shoutcast) for mp3 metadata - this isn't documented by us either, but is widely documented elsewhere (search for 'mp3 shoutcast metadata protocol'). Mike --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Arc Riley
2004-Aug-06 14:57 UTC
[icecast-dev] official communication protocol definition / documentation?
On Sun, Feb 08, 2004 at 08:19:51AM +0100, Enrico Minack wrote:> Hello, > > I am looking for a documentation of the communication protocolls icecast is > capable of: ICY, XAUDIOCAST and a modified HTTP. In order to write client > software being capable of all available features I was searching on the net > for those documentations but no luck so far. How come? Isn't this protocoll > documented? How does the developer team know what options and functins are > available in the protocoll? Just by the already written code?You should use libshout2. It's a handy dandy library that handles all these protocols, as well as pacing the rate of data streaming from the source, etc. If you're really set on reinventing the wheel, you could always check out libshout2's source code to see how it works. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> > I am looking for a documentation of the communication protocolls icecastis> > capable of: ICY, XAUDIOCAST and a modified HTTP... > You should use libshout2. It's a handy dandy library...Yeah, I am familiar with this library, but as I know this is just for sources. I am more interested in requirements clients have to meet, what header response options are available, and which have to be implemented in both server and clients (not sources). Main reason why I am asking is that I'd like to know whether clients like mpg123, zinf or winamp can be expected to be capable of handling HTTP-Location responses. One more detail about Icecast2 that I'd like to know is whether there is any load-balancing feature implemented or about to be implement? Since there is this Master-Slave-Feature, is the Master capable of moving the client to a slave registered at the Master? I haven't found information concerning that in the official documentation and I also haven't had a look into the sources yet. Thanks, Enrico M. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.