On Wed, 19 Nov 2014 18:21:52 -0200, Paul Stanton <pa...@mapshed.com.au>
wrote:
True, visiting PageA and PageB if they both had their own stacks would
download shared snippets twice. The trade off between more bytes *IF*
the user visits both PageA and PageB or a single resource if they just
visit PageA.
Exactly. The better usage is very context-, scenario-specific.
In my example, the 3 large pages have 3 distinct audiences. Only select
people would visit all 3. Therefore it would be great to be able to
combine all scripts for each of these.
Build one stack for each page. :) The overlapping between them could be
refactored to other stacks, used by the page-specific ones.
I'm not sure which is a better approach generally, but I think the
feature of combining scripts is wasted on the current approach.
It's not, at all, when you plan your stacks.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
