Hi; For distributed caching i can advice hazelcast.com, take a look.
Cheers Altug. 2010/5/7 nino martinez wael <nino.martinez.w...@gmail.com> > Id go for at "pojo" dao provider which then can cache the menu, and > just use that from your wicket menu components.. You could then use > something like ehcache, for caching.. > > 2010/5/5 Wolfgang <wolfgang.bue...@exedio.com>: > > > > I'm working on a web site that has a menu bar with sub-items, and > > sub-sub-items. The configuration of this menu is computed from > hilariously > > complex SQL queries and needs quite some time to be established. The menu > > looks different for each user (session) but stays the same for the > lifetime > > of the session. So it's time for caching as this menu shows up on most of > > the pages. > > > > From other posts on this site I've taken that it's not a good idea to > share > > the components that represent the menu among different pages. Now I > wonder > > on which level I can cache and re-use objects. > > > > Is it advisable to share models (in the Wicket sense), i.e. store the > menu > > models on the session and construct the menu components according to > their > > information for every page? > > > > Or do I have to create separate, Wicket-independent data structures that > > hold the menu structure information and store it on the session or in the > > database? > > > > Or am I on a complete wrong track and should look for caching of the > > rendered HTML code on a component basis? > > > > Thanks in advance for sharing your knowledge/experience. > > > > -- > > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Caching-menu-tp2130813p2130813.html > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
