>A completely different approach is to use container-managed security, as
described in the Servlet API Specification >>
><<http://java.sun.com/products/servlet/download.html>>. Here, you are
relying on the servlet container to manage user logon, so that you do not
have to check
>anything on a per-request basis. > > Thanks, > Shiraz
> Craig McClanahan
When you use the servlet container basic authentication - the session is
automatically refreshed (because the user info is sent directly from the
browser) but you still may need to refresh the data/warn the user that the
data has been refreshed since the user may think he is continuing from the
the place he left off but ends up operating on a form-bean in the initial
state.
Could someone correct me if my assumption is wrong?
pratima
____________________________________
Pratima Gogineni
Core Technology
Selectica, Inc.
3 West Plumeria Drive
San Jose CA 95134.2111
www.selectica.com
Direct: 408.545.2615
Main: 408.570.9700
Mobile: 408.315.6380
Fax: 408.570.2167
See our Internet Selling Systems in action:
http://www.selectica.com/iss_in_action/
