zeya team mailing list archive

[Phil Sung <philbert@xxxxxxxxx>]

On Sat, Dec 19, 2009 at 14:54, Romain Francoise <rfrancoise@xxxxxxxxxx> wrote:
> 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.

Interesting. Do you still have that branch around? I'd like to better
understand the extent of the changes needed.

>> 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. :)

Right.

Cheers,
Phil