Re: [libmicrohttpd] shoutcast streaming using libmicrohttpd

[Christian Grothoff]

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*"?

Let me know...

Happy hacking

Christian


On Friday 17 September 2010 16:52:57 Erik Slagter wrote:
> > Would a server-level option (for all connections) do, or does this need
> > to be done on a per-response basis?  I'm just thinking of what would be
> > the right API to give you access to change this...
> 
> It needs to be on a per-response basis, the server streams both http and
> shoutcast connections... From the application's perspective it would be
> ideal if the MHD_queue_response function would accept both an integer
> and a string value for status_code, although I can imagine that is not
> that simple to implement in the library. Or a pure integer value (for
> mhd's internal use) combined with an additional custom string value.