On Mon, Jan 09, 2006 at 09:45:32AM -0300, Edgard Lima wrote: > Im a gstreamer developer and we have just developed a neon-http-src > plugin to allow us get http data. libneon has been choose because it > fits all requirements we need, but one, we cant get icecast/shoutcast > (http://207.200.96.232:8006) data. > > And today it is very important to us because most of servers out there > streaming Ogg and MP3 is icecast/shoutcast. > > Is it possible to change(/add a functionatily to) libneon (I mean, a > small change like a flag o anything else you consider a better design) > in order to allow responses with no http header like in > http://207.200.96.232:8006?
It depends; what other differences are there between the IceCast (ShoutCast?) protocol and HTTP? Is it just the status-line? (if so, one might ask why the heck they made the protocol arbitrarily incompatible with HTTP). Is there a spec for this protocol somewhere which I can read? If IceCast is HTTP-compatible other than the status-line, I'd accept a patch to add a flag to the session to allow parsing IceCast responses, something generic like this is needed anyway: /* if enabled, treat IceCast responses as HTTP responses */ #define NE_FLAG_ICECAST (0x1) int ne_set_flags(ne_session *sess, int flags); and then a API change is really needed for ne_parse_statusline to be able to handle ICY/ as the prefix, conditionally. joe _______________________________________________ neon mailing list [email protected] http://mailman.webdav.org/mailman/listinfo/neon
