[Seaside] HTTP server streaming (was My progress with Seaside...)
avi.bryant at gmail.com
Thu Jan 5 19:38:38 CET 2006
On Jan 5, 2006, at 2:10 AM, Janko Mivšek wrote:
> Dear all,
> Streaming on a HTTP 1.1 servers is a bit more difficult than on old
> 1.0 ones because a TCP connection stays open during many HTTP
> requests. To know when each request ends, it must therefore report
> an exact length and this is the reason why we need the entire
> response in advance before sending to a client.
> But there is also a solution around: see HTTP 1.1 standard http://
> www.ietf.org/rfc/rfc2616.txt, section 3.6 Transfer Codings. It
> seems that "chunked" transfer coding enables streaming!
Yes, and in fact if you look at the version of Swazoo-HTTP on
SqueakMap you'll see that I started some work to support chunked
encoding, but I've never really put all the pieces together...
More information about the Seaside