With ajax=True, first the parent page is returned to the browser, and then an Ajax call is made to fill in the component. So, the parent page should load a little faster in that case (because the component isn't called until after), but there's an additional network call to get the component, so total time might be a bit longer. With ajax=False, the component is added to the parent page on the server side as part of the original request for the parent page. That means returning the parent page might take slightly longer (because web2py has to generate the component content as part of the original response), but there is no subsequent Ajax call once the parent page is returned. So, this may seem faster because there is no waiting for the component to render once the main page is loaded. With ajax=True, however, there shouldn't necessarily be a "disconcerting pause", unless the component takes a particularly long time for web2py to generate (or unless you've got slow network times). Anthony
On Monday, June 13, 2011 6:24:56 AM UTC-4, apple wrote: > Well it certainly seems faster. With Ajax=True the first part of the > page appears then there is a disconcerting pause before the rest. > > On Jun 13, 9:37 am, pbreit <[email protected]> wrote: > > Not necessarily. Ajax=true loads the page and component in parallel. > Ajax=false waits for the component to load before rendering the page.
