On Jul 23, 2010, at 3:31 AM, Jason Brower wrote: > Is this because you have large amounts of data? > When I has some work, we used TCL for the pages. TCL loads as you go. > This is because back in the day webbrowsers we nasty slow and it sent > the data as it came. Now-a-day we create the page remotely and then > send the entire thing. > If your working with large amounts of data then concider loading the > page with ajax or with good ol pagination. At least that's how I feel > about it.
In the long run, I'll invoke Ajax, for a variety of reasons. But what I'm trying to do is to load a page with two tables, the first being short & sweet, the second taking several seconds (perhaps as much as 30) to compute, server-side. I want the browser to render the page header and the first table and then wait for the second table to arrive, rather than waiting for the whole page. The reason I asked about chunking the page is that it's the way that Google does it. I recommend this talk to everyone on this list; it's quite interesting: Velocity 09: Google's Marissa Mayer, "In Search of... A better, faster, stronger Web http://www.youtube.com/watch?v=WFsQvcdmLxc > Best Regards, > Jason Brower > > On Thu, 2010-07-22 at 21:35 -0700, Jonathan Lundell wrote: >> On Jul 22, 2010, at 9:32 PM, Phyo Arkar wrote: >> >>> You mean ajax? >>> You can do this using Ajax. >>> In Jquery: >>> $(#div_id).load(Path_To_Your_Page) >> >> No, I meant just serving a regular (dynamic) page. I'm not using Ajax. >> >>> >>> On 7/23/10, Jonathan Lundell <[email protected]> wrote: >>>> It'd be nice to be able to return a dynamic page in (controlled) chunks. I >>>> have no idea how the interface to something like that might work.... >> >> > >
