I wrote a memcached session manager store for jetty, that our wicket
app utilizes. Works well, except I can't open source it,
since it was created on the company's dime ;-(
Here is my opinion on memcached as a session store.
Memcached will not work well as a wicket session store, due to 1mb
size limits. You honestly don't want to serialize anything past 100kb
in size due to performance reasons. That said, It works best if you
use memcached as a container httpsessionstore with the wicket
secondlevelcache diskpagestore. The only thing you need to serialize
is the last pagemap which should only be 50kb in size max. You still
get fail over since the last page map is distributed.
One thing you need to be careful with is not referencing anything that
got stored on disk from your active pagemap, it will spiral into a
stack overflow.
https://issues.apache.org/jira/browse/WICKET-2138
-Victor
On Mar 8, 2009, at 3:25 PM, Martijn Dashorst wrote:
You can check the TIM integration work from the Terracotta guys. That
should make things easier, and you could even try it out, perhaps
saving a memcached implementation completely :)
Martijn
On Sun, Mar 8, 2009 at 11:01 PM, Martin Grotzke
<[email protected]> wrote:
Hi,
we're just thinking about a session store using memcached. I just
want
to ask if somebody already implemented this (and wants to share)
before
we implement this.
Btw, is there some documentation about ISessionStore semantics, in
addition to javadocs? I would be interested in the order in which the
different methods would be invoked.
Thanx && cheers,
Martin
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
