Jack Moffitt wrote:> Why are you writing clients that don't use libshout?<p>darkice doesn't use libshout either. I guess the main reason to have a protocol is that anyone can connect using it? <p>--- >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-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.
> >Why are you writing clients that don't use libshout? > > > darkice doesn't use libshout either. > > I guess the main reason to have a protocol is that anyone can connect > using it?<p>The protocol is so close to HTTP i'm surprised everyone asks so much. I reverse engineered shoutcast in just a few hours, and here you can just read libshout and know everything about the protocol by reading the 10 line login_ice() function. I do plan to document it, but not until I've finished it. It does me no good to have everyone writing clients that must be half rewritten when my login protocol changes. libshout is there to keep people from duplicating code. It's also there for people to play with for icecast2 so that I have some freedom to change the protocol for a while (since the libshout2 api won't change much). <p>So in short, documentation will come. I hope decent docs will even be there for the first alpha release. Please be patient and in the meantime, have a look at the _login_ice() function in libshout/src/shout.c jack. --- >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-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.
On Fri, 8 Feb 2002, Akos Maroy wrote:> Jack Moffitt wrote: > > > Why are you writing clients that don't use libshout? > > darkice doesn't use libshout either. > > I guess the main reason to have a protocol is that anyone can connect > using it?Yeah, what would've happened to the web if NCSA had said "why do you need to know the details of HTTP? just use our library?" -samuel <p>--- >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-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.
On Friday, 08 February 2002 at 13:12, Samuel Hathaway wrote:> On Fri, 8 Feb 2002, Akos Maroy wrote: > > > Jack Moffitt wrote: > > > > > Why are you writing clients that don't use libshout? > > > > darkice doesn't use libshout either. > > > > I guess the main reason to have a protocol is that anyone can connect > > using it? > > Yeah, what would've happened to the web if NCSA had said "why do you need > to know the details of HTTP? just use our library?"My guess is things would be a lot better - the world would be free of a huge amount of cruft supporting broken or obsolete implementations, and more effort would have been spent improving an NCSA library. I suppose that was a rhetorical question, I'm just not sure which way it was supposed to point :) That aside, it would have been nice if we'd started with HTTP/1.1 instead of 1.0. So I'd say, give ICE time to develop and use the library for now. Once it has been pronounced stable, then you can document and reimplement it as much as you want. --- >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-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.