Re: [libmicrohttpd] shoutcast streaming using libmicrohttpd

[Erik Slagter]

> What about using a high bit in the status code (something like 1 << 31, which 
> won't conflict with HTTP status codes which are all small) to indicate 
> "SHOUTCAST"?  That'd result in a compatible API and we'd not need to define 
> new external functions.  Are there (many/any) other protocols that are this 
> close to HTTP but then also epsilon-off that would justify why we'd have to 
> enable passing a full "const char*"?

AFAIK only shoutcast abuses http this way. Also shoutcast only needs the
200 code. A workaround to cater for abuse of a protocol, ugly ;-)

I think it would work yes.