[Seaside] VisualWorks + WebServers

Boris Popov boris at deepcovelabs.com
Wed Jul 25 19:29:33 UTC 2007


Because most browsers will start processing chunks as they come in. Say
you get the first chunk that refers to a bunch of .js and .css files;
browser can then start working on getting those in parallel while the
rest of your page is being rendered/sent over to you. Depending on your
page layout, some will even attempt to do incremental rendering, large
tables and such.



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 Martin Kobetic
> Sent: Wednesday, July 25, 2007 12:26 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] VisualWorks + WebServers
> Avi Bryant wrote:
> > On 7/25/07, Martin Kobetic <mkobetic at cincom.com> wrote:
> >> Avi Bryant wrote:
> >> > I think what people usually mean is "Transfer-Encoding: Chunked".
> >>
> >> OK, that would be great, because that means we're done with that
> >> :-). The HTTP layer chunks automatically when the body reaches some
> >> pre-configured size.
> >
> > Well, let me be more specific: what people want is to have the
> > start to get sent out as the page renders, rather than have the
> > body get chunked up at the end.
> OK, and why is that important (other than for obvious
> reasons) ?
> Thanks,
> Martin
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the Seaside mailing list