thats not entirely correct. while the event cannot be pushed to you, you can
pull for it. you can set a cookie with expiration null - such a cookie is
destroyed when the window is closed. so you can poll for it ad if its gone
you know its a new window being opened. in the same manner you can use
window.name variable, which is what we do.
so when a request comes in and the user has a last_login cookie (set
expiratio to 30 mins), but no login_session cookie (which is the one with
expiration null) you know they closed the window and are coming back
-igor
On 6/17/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> well, I have a project where the requirement is to do some things when
user
> logs out, otherwise the same user can't use the application for the next
30
> minutes. It works fine when user uses the logout link, but I want the
same
> behavior when the user closes the window. Any hints how to do this?
That's just not possible to my best knowledge. It has nothing to do
with Wicket, but just with the fact that such an event (closing a
browser window using the functionality the OS provides for that) can't
be trapped.
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
-------------------------------------------------------------------------
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
