>>> "Basuki, Rendra" <[EMAIL PROTECTED]> 25-Apr-01 6:49:38 PM >>>
>The only way I can achieve this is "probably" in
>JSDK 2.3 Filter function.... I hope...
Doubt it. What you're talking about doing is carrying state between
the lifetimes of 2 different connections. Filters don't give you
anything that you haven't already got.
What you need is someway of storing the state, which might be ticket,
it might be a replacement for session.
There are defined ways of carrying state:
- session (actually a form of the next 2 methods)
- cookie
- url re-writing or form parameter
- lookups based on authentication or IP address
It's all you can do and the last one isn't even very reliable.
Your problem is that when the request comes in and the session has
timed out you still want to know who the user is.
My order of preference for dealing with this would be:
- extend the lifetime of the session so that it never dies
this might be impractical if sessions get heavy in your app
- rewrite URLs so that they all have the user's name in them
- rewrite URLs so that you assign a "ticket" to them, the ticket
should link into a hash to tell you who the user is
Nic
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
