Most database expensive operations come from the result of stored procedures(my current experience at least). A cache solution can be implemented by caching the method results with spring(in case of using spring) but is a heavy(difficult) thing to maintain that "cache" per user - http session is a nice and easy storage for that-.
Eelco Hillenius wrote: > >> You should use a second level cache to cache objects and queries from >> your database; and that's not Wicket's job, Wicket is a Web framework. >> >> For example, use Hibernate + ehcache. > > Yep. That way you'll avoid redundancy in caching, and have caching > regardless of whatever UI framework you're using. and using e.g. > ehcache can do things for you like limit the RAM cache and overflow to > disk. Etc. > > Eelco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Disabling-serialization-storage-of-pages-in-session--tf4768006.html#a13663495 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
