Of course they do need to be saved. What if after the ajax request there is regular request that shows new page. User goes back and expects to see the previous page as it was after the *last* ajax request, so we need to save and serialize it.
-Matej On Wed, Aug 20, 2008 at 7:29 PM, John Patterson <[EMAIL PROTECTED]> wrote: > > > > Johan Compagner wrote: >> >>> >>> Ajax request for page A: alter the page in memory (still only in memory, >>> no >>> new version) >> >> yes page is altered so new version (ajax version) >> >>> >>> Normal request for page B: serialise A to disc and place B in memory >> >> >> No now you first do a request to A that can change something on it >> And then you redirect to B (you clicked on a Link object or submit a form >> on >> page A) >> >> if previous step didnt serialized then that version is lost >> > > I understand that every page-version needs to be saved for back button > support. But I thought that AJAX requests did not make new versions and > therefore did not need to be saved. > > > -- > View this message in context: > http://www.nabble.com/Page-serialisation-tp19072319p19074361.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]
