Ahh, so the information is serialized in the same thread, but the actual saving to disk goes on in another thread. Is that right?
On Wed, Aug 20, 2008 at 12:38 PM, Johan Compagner <[EMAIL PROTECTED]> wrote: > no we need always the latest version on disk before the next request comes > in > This is because if your next request comes in it can change the page then if > you go to another page > and back again we loose a version if it isnt saved yet. > > i guess matej can also come up with some other reason for it > > > On Wed, Aug 20, 2008 at 6:30 PM, John Patterson <[EMAIL PROTECTED]> wrote: > >> >> Is that the only reason? I imagine most sites will be running on one >> server >> with no failover. Is there a way to switch the serialisation of the >> current >> page off if failover support is not required? >> >> >> Martijn Dashorst wrote: >> > >> > Failover support needs the updates done by the ajax request. >> > >> > Martijn >> > >> > On Wed, Aug 20, 2008 at 6:13 PM, John Patterson <[EMAIL PROTECTED]> >> wrote: >> >> >> >> Hi, this might be a really obvious question but... why are pages >> >> serialised >> >> for every ajax request? I thought the latest page was always stored in >> >> the >> >> PageMap? >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Page-serialisation-tp19072319p19073257.html >> Sent from the Wicket - User mailing list archive at 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]
