Hi, Could anyone tell me about the different login schemes sources can use to connect to IceCast, ShoutCast, etc? From what I can tell: ShoutCast uses something called icy login? IceCast uses something called x-audiocast, but can also use icy? IceCast2 uses what? Also, where can I find details about these login schemes? I sort of figured out a basic use of x-audiocast by looking at the JScream source, but I don't know anything about icy. Can anyone send me pointers on these issues? Thanks, Akos --- >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 at xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Due to my inability to find such a utility I'm going to hack something toghether (in Java most likely) to parse the icecast log files and insert the entries into an SQL database. Although I've managed to piece together most of the format for the access log the nature of a couple still elude me, as well as the organization of the icecast log. I've gone through the icecast source what I can but C is by far not my native tongue. Anyone care to help me out so I don't have to bug the developers? Any input is appreciated. Jason Mansfield __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com --- >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 at xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> ShoutCast uses something called icy login? > IceCast uses something called x-audiocast, but can also use icy? > IceCast2 uses what?icecast2 uses one called ice. It's not complete yet, as we want to add some security features that will make it a bit different. All of the code for these (and it's _very_ simple) is in the libshout module in the BitKeeper repository. icy and x-audiocast are also well defined by the code in libshout in cvs. 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.
> Although I've managed to piece > together most of the format for the access log the > nature of a couple still elude me, as well as the > organization of the icecast log.access.log is in Combined Log Format, which is quite well documented around the web is the same as what Apache produces. The only thing differnet is the last parameter, which is a number. It's hte number of seconds that the connection lasted. using this you can turn the bytes into bitrates, and figure out average listener time, etc. You can parse the logs with any normal log parser, they will all ignore the last value. icecast.log is only meant to be readable by humans. It's not in any format.> I've gone through the > icecast source what I can but C is by far not my > native tongue. Anyone care to help me out so I don't > have to bug the developers? Any input is appreciated.Look at apache.org for Combined (and Common) log format docs. From memory it's something like: ip/host, identd, authname, date, request string, status, bytes, referer, agent, seconds connected Hope this helps. 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.