On 19 Aug 2014, at 3:56 am, Sumanth <roasteddra...@gmail.com> wrote:
> Hi all,
>
> * 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
>
> I will have to try with this solution "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."
That can be a big change, unless the pages are already divided into small,
use-case-based components. To see what I mean, have a look at the following two
examples. It was quite easy to convert the first, non-AJAX example into the
second, fully-AJAX example (except for the Grid stuff, but that had to be
solved only once and it produced a useful component).
http://jumpstart.doublenegative.com.au/jumpstart7/together/smallercomponentscrud/persons
http://jumpstart.doublenegative.com.au/jumpstart7/together/ajaxcomponentscrud/persons
> Let me try this and come back in case of doubt.
>
> Thanks,
> S S
>
> PS: sorry for confusion :)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
