In order to have HA support past last visited page (which is what we have now), you would have to use eh cache in distributed mode. I've tried this, it's dog-slow. ehcache uses RMI for remote calls and it really really is slow. Sorry.
Also, EHCache is a cache. It's not storage. That's a fundamental difference. Cache is for objects can be recreated. That's not true for serialized wicket pages. -Matej On Jan 7, 2008 12:47 AM, C. Bergström <[EMAIL PROTECTED]> wrote: > > On Mon, 2008-01-07 at 00:43 +0100, Matej Knopp wrote: > > On Jan 7, 2008 12:04 AM, C. Bergström <[EMAIL PROTECTED]> wrote: > > > > > > Matej.. I haven't looked at how difficult it would be to implement, but > > > would someone post some ehcache 2nd level cache store code so I could > > > run some real numbers with it? > > > > The implementation is no longer available, because the interfaces have > > changed. And I really don't get the benefits of ehcache pagestore > > implementation. > > > > I think the goal in this case was so that the session/back button support > could be replicated to provide some HA features or failover capability. > > With the current pagestore how do you scale back button support past a single > node? > > ./C > >
