[Seaside] VisualWorks + WebServers

Boris Popov boris at deepcovelabs.com
Wed Jul 25 19:36:20 UTC 2007

Yes, that's right, the end result of delivering content in full to the
browser is the same, but don't underestimate the important of such
optimization, because every little bit of perceived performance helps
keep users happy :)



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:33 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] VisualWorks + WebServers
> I don't mean to be obtuse, but that still sounds as just an
> i.e. nothing would break if the chunking happens after the page is
> rendered. Things just show up a bit later. Or am I missing something ?
> It's not that I think this feature is unnecessary, I just like to
> understand the problem when I try to fix something :-).
> Thanks,
> Martin
> Boris Popov wrote:
> > Because most browsers will start processing chunks as they come in.
> > you get the first chunk that refers to a bunch of .js and .css
> > browser can then start working on getting those in parallel while
> > rest of your page is being rendered/sent over to you. Depending on
> > page layout, some will even attempt to do incremental rendering,
> > tables and such.
> >
> > Cheers!
> >
> > -Boris
> >
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the Seaside mailing list