> > The overhead of serializing is only there when running > clustered? The > > 'page back' functionality also uses it, isn't, so I thought > it wasn't > > only for clustered environments (and then specifically for > clustering > > without sticky sessions, right?) > That's not quite what I meant. First it is strongly > recommended to use sticky sessions when using wicket on > cluster. Without sticky sessions you have to use redirect to > render (instead of redirect to buffer) and that certainly > won't help your performance. > > Also on cluster you probably want to have failover (must have > if you don't use sticky sessions). In that case the changes > needs to be distributed across cluster. Thus the page must be > serialized. Wicket reuses the serialized data from the > serializaton is diskpagestore so on cluster the page is only > serialized once (instead of twice - once in diskpagestore and > for session replication).
Ok, I think I get it :-) One more questionL if I would have sticky sessions, and no page back functionality, would I still need wicket to serialize? Regards Ard and thanks for the explanations > > -Matej > > > > > -Ard > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
