> But even if I would accept the usability penalty of the expiring pages, I'm > surrounded by usability experts who will never do that. Moreover a very long > session timeout won't be accepted by others.
But if you require your users to be logged in, what alternatives are left then? Even if you would use another framework, you would have to deal with session time-outs, right? I'm sure there are still possibilities to improve though. One of the things that we've been talking about is to have a more recoverable model. Like in, when a page for an internal page is not found, we would try to construct it's bookmarkable counterpart etc. I think we've discussing this as 'hybrib urls' and Matej has been doing some experimentation with this. We also just need a couple of really good ideas and use cases if we want to improve on this. Cheers, Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user