Hi Folks, I am currently pondering a problem on how scalable is scalable in terms of servlet sessions. For a person calling my servlet I want to assign a session ID, the session in the servlet will not have any data assigned to it other that that assigned by the servlet engine to maintain session. I know it will probably be dependant on the servlet engine and if sessions are written to disk. I can load balance the servlet engines behind the HTTP server (Apache & Tomcat) but at what point do we start to thrash. There must be some work involved in matching the session to the session cookie, if the session is stored on disk the this needs to be located, loaded and compared. Will I have to look at the Tomcat source to work out how efficient it all is ? What is the minimum number of bytes used to track a session ?
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Smallest Session Size, Scalable until when ?