Well, this is not session problems I am having but SSL Sessions - you
can't have a secure connection without using one of those.
On a side note, I'd like to argue that if you have users logging in,
you can't help having some kind of object on the server side telling
you which user is actually sending the request.
Yuval Perlov
www.r-u-on.com
On Jan 22, 2008, at 3:42 AM, Jonadan wrote:
IMHO, there isn't much you can do about once you use sessions. The
problem
with session is that there is no natural way telling that session is
ended
and can be discarded! So system may have to keep session objects for
long.
For this reason, I always avoid to use sessions. If this is a major
problem
for you, alternative techniques might be worth trying!
Regards.
--
View this message in context: http://www.nabble.com/ssl.SessionId-
Cache-keeps-growing-tp14999824p15010907.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
