[Seaside] VisualWorks + WebServers

[Martin Kobetic]

OK, so the key here is that it's not a single fully rendered page per HTTP response, but rather a sequence of several "UI artifacts" (for lack of better expression) packaged in a single response where you need to previous one to be rendered before the next one arrives. Is that getting close ?

Thanks,

Martin

Ramon Leon wrote:
> Because it gives the impression that the site is much faster, the page
> starts rendering to the client right away.  
> 
> It also allows the server to send down initial content like maybe a splash
> page or progress bar, and stream down updates to the UI and then when
> finished, hide that and show the result.
> 
> Ramon Leon
> http://onsmalltalk.com
> 
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>