This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
Isn't the Web Container that writes this cookie? or it's written by java API?
I mean, if it's container job to write that cookie and it's also his job to read it, then any name could be used like, "tomcatseessionid" or "jettysessionid" or "iissessionid" as long as he understands what he has written, I don't see why the cookie must be named "jsessionid".
I know that this matter isn't so important, I just couldn't not ask it!!
Hi, Mateus. I think it is due to compatablity between the servers, especially in clustering environment, where different server's work together(when session needs to migrate from one server to another server). Thankyou.
Joined: Jul 27, 2006
That makes sense ... when you deploy a web app in a clustered environment, you don't need (or sometimes you can't) to use the same web container in all machines, if you don't use the same cookie name your session info couldn't be transferred from one node to another!