Hi,
Am 05.03.2012 11:41, schrieb Lance Java:
The javascript stack concept exists so that the stack remains constant and
can be cached by the client's browser.
You are now asking to break this contract and have stacks be dynamic based
on what components are on a page which would eliminate the ability to cache
them in the client's browser.
Right, I missed that ignoring duplicates would break the stack
assembling feature. But I still see problems with the current behavior.
I think we should find a way to prevent someone from creating stack
setups like mine (a single asset being used in multiple stacks). Maybe
JavaScriptStackSource(Impl) could log a warning or even throw an
exception if that is done. What do you think?
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
