>but what is a previous page? you said you only have a single page? Yes, we have one 'physical' Wicket page. But of course, our application contains various 'conceptual' pages (physically panels), i.e. components that make up the body of that single page, and that we go replacing as the user navigates. With previous, I mean the same Wicket page, but a previous panel.
>wicket's ajax requests should never generate a new version, because ajax requests do >not change the page url and thus there is no back-button history - and so a >version is not needed. That's why I started this thread in the first place: we are using ajax requests to replace these 'conceptual pages' (panels), and would have liked a history of that. But for what I read around here, this would be a hell of a job. I suppose we should re-render the whole page each time. Jan. B.t.w.: thanks for the great support, the quick response from the core developers, the open mind to new ideas, etc. We made the right choice in going to Wicket ! -- View this message in context: http://www.nabble.com/Single-page-applications%3A-bad-idea-in-Wicket---tf3182341.html#a8873296 Sent from the Wicket - Dev mailing list archive at Nabble.com.
