Hi, The question I have is regarding separated ports for client and source connections. Let me explain. Since a short while I have been successfully testing icecast and ogg for live broadcasts. Now I am building a website around it, which of course I want to be dynamically generated on the fact whether there is a live broadcast or not. The easy way I want to do that is to check for connections on the given port in the icecast configuration file. Basically this works fine. If there is at least one connection on that port, there must be a source connected, hence a broadcast. The problem occures when a client wants to connect without a source being available, then my webscript detects a connection, but that of the client trying to connect and not of the source. Is it possible to build in an option in the configure stage of icecast which let's you choose between just one port or separate ports for client and source connections? Or does anyone know I can alter the source code to accomplish this myself? I have tried to add an alternative 'sourceport' in the main.c and config.h files. It compiled successfully but after startup it did not work (surprise surpise!). Since I am no C programmer, can anyone help me out? I know there are several reasons for going for just one port, I understand completely, but it's such an easy to realtime detect broadcasts. Thanks for reading and any answers that follow. Regards, Frank Keijzers <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-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.
Quoting Michael Smith <msmith@labyrinth.net.au>:> Why don't you just ask icecast whether it has any source connections? > You can do this by requesting /stats.xml from the server, and parsing > that.Yes, but that only showed ClientConnections and Connections. That is, until I did a cvs update after two months:) Is there any way, or will there be a way in the future, to disable the reading of the stats.xml by unauthorized people from outside of the server? Frank --- >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.
At 01:52 PM 8/13/02 +0200, you wrote:> >Hi, > >The question I have is regarding separated ports for client and source connections. Let me explain. > >Since a short while I have been successfully testing icecast and ogg for live broadcasts. Now I am building a website around it, which of course I want to be dynamically generated on the fact whether there is a live broadcast or not. > >The easy way I want to do that is to check for connections on the given port in the icecast configuration file. Basically this works fine. If there is at least one connection on that port, there must be a source connected, hence a broadcast.Why don't you just ask icecast whether it has any source connections? You can do this by requesting /stats.xml from the server, and parsing that. MUCH easier than adding multiple port support. 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.