"Basuki, Rendra" <[EMAIL PROTECTED]> wrote:
__________
>So, you are saying I should use Servlet Mapping at the server level?? and
>then check the URI upon session timed out?
Yes.
>This might works, but the problem is there might be different group of users
>that will come from different login page and thus must come back to the
>login page that they came from.
Yes, I realize that.
Looking at it from the browser
perspective I propose you create
subdirectory for each class of
user so you'd have
http://me.com/app/aIpha/login
http://me.com/app/aIpha/main
http://me.com/app/aIpha/etc
and
http://me.com/app/numeric/login
http://me.com/app/numeric/main
http://me.com/app/numeric/etc
And
http://me.com/app/roman/login
http://me.com/app/roman/main
http://me.com/app/roman/etc
all the urls in the pages should
be relative- so each user stays
in their own subapp.
the trick is to use the same java
in the 3 subapps (skins).
Each of the 3 servlets (login. Main,etc) would be mapped
3 times, once into each of
the subapps.
That said, I think that in reality
you should be creating 3 separate
webapps that contain the same
servlets, but different html (if
that's what you need)
I have a nasty hack too, If you
know the name of the cookie that
the container uses to keep the
session, you could get that at
session timeout (it will probably still
be valid) and look it up in a hash
table created in the login servlet.
UUGH! (blush, I wish I hadn't thought
of that).
http://www.westpoint.ltd.uk/
Internet reconnaissance services.
___________________________________________________________________________
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
