zeya team mailing list archive

[Romain Francoise <rfrancoise@xxxxxxxxxx>]

Samson Yeung <fragmede@xxxxxxxxxxxxxxxx> writes:

> Google Chrome's implementation of ogg decoding needs to see a
> Content-Length header. [...]

Yeah, but the problem is really in Zeya: it's unusual to stream
audio content using plain old HTTP/1.0; streaming servers usually
use a combination of chunked encoding and partial content serving.

I had a branch which implemented support for chunked encoding over
Python's BaseHTTPServer but it got broken by Phil's shaping changes
in the backend (my branch added another level of buffering in the
server itself).

In the long term, I think that using an existing HTTP/1.1 stack like
Twisted's web2 would be the best solution.

> Actually, all files are decoded and pushed to the ogg encoder,
> even ogg files. Not the most efficient, but patches welcome!

I suspect that most people have their Ogg files encoded at a higher
bitrate than what they use for streaming, though. :)