hmm that is pretty much killed with the basic 1.3 setting now because we have a file on disk thats pretty much a database file with multiiply pages now but the index of that file, where the page starts is in mem..
so for clustering and a shared disk the only solution we currently have (besides the HttpSessionStore) is the SimpleSynchronousFilePageStore I guess we need a SimpleAsync one to have a performant one? Or look if matej finishes the other. Also is it you should ask yourself is it really importand if you have failover but with sticky sessions that when a failover happens. That only at that small window the back button will trigger a page expired? If they are already 1 or 2 clicks further nothing is wrong. Its just a matter of how high you build the banks. johan On Nov 16, 2007 7:33 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > you can still cluster 1.3.1 easily. either use httpsessionstore or > tell wicket to save pages to a shared drive > > -igor > > > On Nov 16, 2007 10:20 AM, saenz <[EMAIL PROTECTED]> wrote: > > > > > > igor.vaynberg wrote: > > > > > > you will get an error, i have explained this in a parallel thread > > > yesterday... that is why we are working on a special page store that > > > will also write out the current page onto the disk when the session is > > > replicated - that means all nodes will have all the pages spooled to > > > disk so clustering will be transparent... > > > > > > > Thank you Igor. > > > > So for now, is the recommendation to disable disk-based page > serialization > > if a Wicket app is deployed to a cluster? > > > > Do you plan on including the new and improved replicated page store in > > Wicket 1.3 RC or will that be a 2.0 feature? > > > > Also -- if page serialization is disabled, what happens when the user > hits > > the back button? > > -- > > View this message in context: > http://www.nabble.com/Disabling-serialization-storage-of-pages-in-session--tf4768006.html#a13797991 > > > > Sent from the Wicket - User mailing list archive at > > Nabble.com<http://nabble.com/> > . > > > > > > --------------------------------------------------------------------- > > 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] > >
