On Sun, Feb 08, 2004 at 01:07:39PM +0100, Enrico Minack wrote:> > 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.I haven't heard or seen of this, nor do I think load balencing as you describe it could be done seamlessly without modifying the media player. I believe what you're looking for can be found in what we're doing with the IceShare project, www.iceshare.org, which is still being designed. --- >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.
On Sunday 08 February 2004 23:07, Enrico Minack wrote:> > > I am looking for a documentation of the communication protocolls > > > icecast > > is > > > > 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). >Oh, for clients, things are simpler than my previous response: just use HTTP/1.0. Icecast does not currently support everything in the HTTP specification, but more is likely to be added in the future.> 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.Icecast won't send them, but the client should support them as part of implementing HTTP (most clients probably don't). <p>>> 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?There is no load-balancing. 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.
> > One more detail about Icecast2 that I'd like to know is whether there isany> > load-balancing feature implemented or about to be implement? ... > I haven't heard or seen of this, nor do I think load balencing as you > describe it could be done seamlessly without modifying the media player.I made some tests and it turned out that Winamp, mpg123 and even MS Media Player are capable of handling HTTP-Location responses properly. Therefore it might be possible to implement an load balancing feature without having changes on client side. This is what I thought of: client requirements: - handling HTTP 302 response status together with HTTP-Location attribute properly erver requirements: - Slave - telling the Master how many clients are connected - Master - using Slave information to fulfill load balancing algortihm And this is how it works: Every Slave sends its load data (how many clients connected and the defined maximum of clients) to the Master (propably included in the master-update-interval procedure). Therefore, the Master knows which Slaves are connected and working, and which has the lowest load. The next client will be forwarded to this Slave using the HTTP 302 status together with a HTTP-Location attribute: --- HTTP/1.0 302 Found Location: http://SLAVEIP:SLAVEPORT/MOUNTPOINT --- Thus, the client is forwarded to a Slave and we got a centrally controlled load balancing. Advantages: - Slaves can be added dynamically without posting them in mirror-lists - Slaves will be used for load balancing instantly <p>What do you think? 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.
> > 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.