Um, What do you mean it is up to the client? who's the client in this case?
I don't know if Wicket uses sychronized objects or methods for accessing the httpsession. On Mon, Apr 20, 2009 at 10:37 PM, francisco treacy < [email protected]> wrote: > 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 <[email protected]>: > > 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 > generate more interested replies. ;-) David. > > > > > > > > > > Carlo Camerino wrote .. > >> 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 question is how does wicket handle this? Do we need to add any > special > >> handling or does wicket take care of it automatically? > >> > >> Thanks > >> Carlo > > > > > > > > --------------------------------------------------------------------- > > 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] > >
