[xiph-cvs] cvs commit: libshout/src shout.c util.c util.h
Brendan Cully
brendan at xiph.org
Sat Feb 22 14:50:24 PST 2003
On Saturday, 22 February 2003 at 15:38, Jack Moffitt wrote:
> > Send ice-audio-info header in HTTP protocol, instead of ice-bitrate.
> > This header is encoded like the query part of a GET request, eg
> > ice-audio-info: bitrate=128&samplerate=44100&channels=2
> >
> > Oddsock, knock yourself out. :)
>
> Why encode it like an HTTP request? That seems a bit silly to me.
> Normally RFC822 (i think that's the correct one) type fields are
> delimited by semicolons or commas. I'd suggest looking at RTSP and/or
> RTP docs and see how they do this. My recollection is that it's
> something like:
>
> ice-audio-info: bitrate=128; samplerate=44100; channels=2
>
> which is a lot more human friendly, and only slightly more difficult to
> parse.
I have no opinion either way. I just reused the code I was using for metadata,
and there didn't seem to be a compelling reason to make the delimiter vary. Since
this is HTTP I figured anyone handling these headers would already have the
library code to parse them. I do think it's a good idea to URL-encode at least
the values, in case someone wants to send something more complicated than numbers
later on.
RFC2616 (HTTP/1.1) is probably a better model than 822.
Any other opinions?
-b
PS Hi jack :)
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'cvs-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.
More information about the commits
mailing list