"Oscar =?iso-8859-1?Q?Pérez?=" wrote:
> Do you still have access to the session data after redirecting, or the
> session isn't valid no more?
> [...]
Hi :-) I am not sure, the following is just my understanding:
* with jakarta-tomcat-4.0-b1, I think session(HttpSession)
is belong to:
several instances of a browser <--> a specail webapp
- in one wabapp, the session is same for:
% different servlet definition of the same one MyServlet
% different servlet definition of the different MyServlet
% after reloading, the session will be invalidated
- between two wabapps, the session is different
* so just from my understanding, perhaps the answer of
the question->"if we can access session or not after
HttpServletResponse.sendRedirect(...)" depends on:
- "where we go"
- "type" of the session:
% within one webapp
% across multi webapps
% across multi server
% ...
in other word, I guess that question Doesn't has relation with
HttpServletResponse.sendRedirect(...) Itself(please see several
emails about sendRedirect(...) uses 302 to tell browser go to
another URL...)
* with jakarta-tomcat-4.0-b1, I think "we Can access session" after
RequestDispatcher.forward(...), because they are All within one
web app.
* about across multi server(loading balence), please see:
http://groups.yahoo.com/group/advanced-servlets
there are some good emails there :-)
Bo
Feb.28, 2001
___________________________________________________________________________
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
