Hello all, I was wondering what everyone's preferred approach to using multiple zones in a hierarchy of components was. I'm not pleased with the current pattern we use and figured someone might have come up with a better approach.
We run a complex page; having a single zone proved very slow. We increased the number of zones to encompass specific components so as to speed up the page; this worked but as a side effect we have large numbers of component parameters dedicated to zones and thus long chains of parameters carried through a number of components. We need to update (multiple) zones in multiple places throughout our component hierarchy. One good example is a text alert that needs to be updated by pretty much every component in the hierarchy and so we end up passing the 'alert zone' as a parameter to every component that needs it. I was imagining something similar to an object of session state that can be initialized to hold on to the zone references and thus be injected where required. Or perhaps as is the case with the zoned alert component, to have it extend Zone and pass that around as a parameter (I already pass the injected Alert component as well as the related Zone all over the place; this allows me to centralize reusable alert messages for the component hierarchy, makes breakages more manageable). It's quite an open question - I do hope to hear some of your approaches! Thanks again! -- View this message in context: http://tapestry.1045711.n5.nabble.com/Elegant-Handling-of-Multiple-Zones-in-Deep-Hierarchies-of-Components-tp5717698.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
