You run the risk of getting duplicate session id's. However, across contexts you'll have
separate Managers, and therefore different sets of sessions. So, you don't run the risk
of one context gaining access to another context's sessions.

The risk is the one discussed in the other session id thread where if you get duplicate
session id's in the same context. Then you've got serious problems.

shawn wrote:

If I use RequestDispatcher.forward(request, response) to another context
am I running the risk of session id conflicts?

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to