It's nice to hear you are working on improvements.

Thanks,

Pieter

ps

just wanted to mention a scenario I ran in to:

You log in and open a second window or tab of the same application. A page
can expire in one window, while you are stilled logged because you are
working in the other window.



2007/6/21, Igor Vaynberg <[EMAIL PROTECTED]>:

you can only do it if you are writing a purely stateless application -
zero session use. and if this is a hard requirement then wicket is probably
not for you. of course it is pretty difficult and annoying to write any soft
of a complex web ui without using session at all, thus wicket. so just
depends on what tradeoffs match your specs.

-igor


On 6/20/07, Pieter Cogghe <[EMAIL PROTECTED]> wrote:
>
> That's partially true, but after the session expired and the user has
> logged in again, you can redirect him immediately to the place where he was
> when the session expired (if that's a stateless page). It's true that this
> is more an issue with sites that don't require the user to log in and that's
> the case that concerns me the most.
>
>
>
> 2007/6/20, Eelco Hillenius <[EMAIL PROTECTED] >:
> >
> > > 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
> >
>
>
>
> --
> Pieter Cogghe
> Ganzendries 186
> 9000 Gent
> 0487 10 14 21
>
>
> -------------------------------------------------------------------------
> 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
>
>

-------------------------------------------------------------------------
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




--
Pieter Cogghe
Ganzendries 186
9000 Gent
0487 10 14 21
-------------------------------------------------------------------------
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

Reply via email to