Hi,
I would just like to post an inquiry on how wicket handles httpsession
concurrency.
When the application usage volume goes way up, it seems that httpsession is
problematic.
In struts for example,
if you use request.getSession() without synchronized access you might
encounter problems
My
Hello Carlo, very good question. I don't have an answer but I am just
confirming equal interest in the outcome of your question. I am about to embark
on a company project web app makeover/rewrite and I am throwing all my eggs
into the Wicket basket (no pun intended). Hopefully, this will help
I don't think you will encounter problems just by calling
Session.get(). But it is up to the client to synchronize session
state.
Francisco
2009/4/20 da...@davidwbrown.name:
Hello Carlo, very good question. I don't have an answer but I am just
confirming equal interest in the outcome of your
Here are some threads that cover this topic, with lots of info from the core
developers.
http://www.nabble.com/Thread-safety-for-components-tt17265324.html#a17265324
http://www.nabble.com/Wicket-Session-and-threading-tt14595666.html#a14599963
