Eelco, you're right! The latest profiling shows where the bottleneck is... it is indeed not where I was looking for. I thought it was because of serialization because when using 1.2.x branch i found out that setSerializeSessionAttributes(false) improved a lot application responsiveness.
Thank you a lot! Alex Eelco Hillenius wrote: > >> Eelco, the ISessionStore interface has a lot of methods.. can you give me >> an >> example of how to get rid of the serialization? It really slows down the >> application. > > I can imagine those checks did cost something in 1.2, though with Wicket > 1.3 > and the way we use it with the session stores should be pretty well > optimized. I think the last time I looked, serializating and saving a > (pretty big) page took 1 or 2 miliseconds on my notebook. Are you sure > this is such a bottle neck? Maybe there is something else you weren't > aware of? Can you give us some numbers maybe? > > Anyway, if you want to build a session store from scratch, you could > look at HttpSessionStore, copy most of it, but instead of storing in > the session, you you store it in a hashmap. > > Eelco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/setSerializeSessionAttributes-in-wicket-1.3.0-beta2-tf4267003.html#a12176426 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
