[Seaside] Seaside vs Streaming

Boris Popov boris at deepcovelabs.com
Mon Aug 20 21:24:54 UTC 2007

Okay, let's simplify this a bit. If streaming were an option on a
session and defaulted to false to keep all the "cool" things like auth
working, that's fine with me, I would turn it on for our application
anyway since we don't use it. Also, I believe there was some talk about
making one extra pass over a component tree to try and determine if any
components would "vote" to suppress streaming for that specific request,
say if WATask is involved, can we still do that? This way those of us
who want to start delivering content to the user agent as soon as it
becomes available can do that, merely as user experience optimization if
nothing else.



DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com


This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Lukas Renggli
> Sent: Monday, August 20, 2007 2:20 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Seaside vs Streaming
> > So it's not about handling large files. It's about being able to
> > do new kinds of web programming.
> What kind of new web programming?
> Seaside supports Comet style HTTP streaming since 11 April 2006,
> am.
> Lukas
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list