I agree that the Shoutcast protocol concocted by Nullsoft and by several media players is more of an ugly trick from a protocol perspective. If anyone has a better suggestion for a streaming protocol (RTSP or RTP?) which is supported by the mentioned mediaplayers I am open for the suggestion. Probably could make a Coyote connector for that if need be.
Arend Filip Hanik - Dev Lists wrote: > an HTTP request, requires an HTTP response, regardless of what the > headers are set to. > proxies and other things that come in the middle would be confused, or > even reject the response if something else came in between. > I'd be surprised if anyone here would be interested in making that > modification, it would break the protocol. > why would applications like XMMS or WinAmp not handle a HTTP response, > but would need the response to be of a different kind? > > Filip > > Arend van Spriel wrote: >> Hi, >> >> I have created a stand-alone socket application serving HTTP request >> from XMMS, WinAmp, etc. which use the header field 'icy-metadata' on >> which the server application returns with ICY response. >> >> Now I would like to do the same from within a Tomcat servlet. As I am >> not aware what the correct channel was I already created an enhancement >> bug in bugzilla: http://issues.apache.org/bugzilla/show_bug.cgi?id=44399 >> >> I also attached a solution there, but more experienced tomcat developers >> may have a better one. Maybe the community can comment on this request. >> >> Gr. AvS >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
