[Seaside] VisualWorks + WebServers
mkobetic at cincom.com
Wed Jul 25 19:33:21 UTC 2007
I don't mean to be obtuse, but that still sounds as just an optimization, i.e. nothing would break if the chunking happens after the page is fully 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 :-).
Boris Popov wrote:
> 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.
More information about the Seaside