On 18 Aug 2014, at 9:47 pm, Thiago H de Paula Figueiredo <thiag...@gmail.com> wrote:
> I think there's a confusion here about what Sumanth means by "server > requests". Agreed. > The term is ambiguous in the context of his/her e-mail and I answered > considering them as database and web services requests. > > On Sun, 17 Aug 2014 00:48:56 -0300, Geoff Callender > <geoff.callender.jumpst...@gmail.com> wrote: > >> Sumanth, >> >> I think there will be much fewer requests than you imagine. Have a look at >> the network traffic (use your browser's web inspector or FireBug) to see for >> yourself. >> >> * If you click a link generated by PageLink, then you should see exactly >> *one* request and an HTTP 200 (OK) response which contains the whole page >> including the layout. >> >> * If you click a link generated by EventLink, then you should see exactly >> *two* requests: the first one will respond with an HTTP 302 (REDIRECT) >> response and the second will respond with an HTTP 200 (OK) response which >> contains the whole page including the layout. >> >> Of course there may be other requests for assets (css, js, images, etc), but >> the ones in your layout will be cached automatically (when in production >> mode). >> >> An alternative technique is to use a single page, with layout, for the whole >> app and use Ajax/Zone updates to replace everything except the layout >> portion. >> >> HTH, >> >> Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
