You could make such a thing as an extentions project as a special session store or ipagestore. But i dont see the big gain because its not the reading (that doesnt happen a lot, or the writing (done in separate thread)) the time is spend in serialization. But the overhead we encountered was 20% or something like that. But the gain we have is way less memory usage so in the end we can handle more clients with 1.3
On 1/6/08, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > on the subject of 2nd level cache stores, how feasible would it be to use > ehcache as a backing store? ehcache can store things in memory, and overflow > to disk making it a hybrid to our disk based storage. > Is it reasonable to consider a caching solution such as ehcache to provide > the backend storage? > > Did we ever consider ehcache as an alternative? If so, why did we not pick > it? > > Martijn > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.0 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0 >
