I happen to be a fan of tapestry's multi-page approach and serverside markup generation. On 4 Feb 2014 18:35, "Christian Köberl" < tapestry.christian.koeb...@gmail.com> wrote:
> 2014-02-04 Lance Java <lance.j...@googlemail.com>: > > It's tricky because there would be 2 requests (1 for markup and 1 for > > javascript). > > No, there's no need for a 2nd request - JS should be static - it's > code! The data should be in the DOM (or probably fetched by a REST > request per JSON). Think outside of the Tapestry box - if you look at > recent examples in other frameworks you won't find any inline JS > anymore. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
