Much more performant is very relative. Not to mention that it's much more memory heavy, and when GC starts to kick in, the performance is decreased significantly.
Apart from that, HTTP session store has significant undo/redo problems, and accessstackpagemap leads to unexpected page expiration problem. So should we support httpsessionstore in future, we need to either fix the undo/redo problem (thus increasing complexity for a very rare used feature), or make all pages non-versioned when using httpsessionstore (this would work for me). -Matej On 9/29/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > But the second level cache session store is not the only viable > option: we still have the HTTP session store, which clearly is much > more performant than any other store, especially if you don't have to > cluster. > > Martijn > > On 9/29/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > > On 9/27/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > > > the problem is that that still not really does auto dirty.. > > > Because where does it end? just add/remove/visitble/enable? > > > The nice thing is we have already something like that: thats page > > > versioning > > > with the undo/change map. > > Don't get too attached to it :) We should remove it in the next > > version, doesn't make much sense for 2nd level cache session store :) > > > > -Matej > > > > > If we extend that a little bit then we could have something like > > > componentChanged(component) on a page (or somekind of listener) > > > and that component did trigger it self what ever did happen on it > > > (getting a > > > child, settting the visibility, or setting an internal none wicket core > > > property) > > > > > > johan > > > > > > > > > > > > On 9/26/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > > > > > On 9/26/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > > > > > but this discussion is not just about getter/setters (i don't care > > > > > about > > > > > those) > > > > > but also for add and remove.. then we are getting into some other > > > > > stuff > > > > > > > > Yes. Getters/ setters are less tricky. Though I'm still not breaking > > > > in sweat when I imagine removing final on add and remove. > > > > > > > > Eelco > > > > > > > > --------------------------------------------------------------------- > > > > 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] > > > > > > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.0-beta3 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/ > > --------------------------------------------------------------------- > 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]
