-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Arnab,
On 1/9/2010 1:14 AM, Arnab Ghosh wrote: > How it will be I create a new manager which will extend standardmanager and > then if overload the generateSessionId() method. I will mot change the > session Id generation code. Instead of that I will add a new static set and > will store all generated sessionId there. I will continue the loop of > generating a unique session Id until it get added in that static set (By > default it will check a instance map where it used to store all session and > sessionId as a key). Technically speaking, that's changing the session id generation code. :) I think if you do this, you're going to just create more trouble for yourself. What's the problem with different sessions in different webapps having the same session id? The sessions don't interfere with each other. The only "problem" is that they have the same session id. I can't understand why this is a problem. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktI5+YACgkQ9CaO5/Lv0PBkVgCgpq3fy2qGEaEm20IqSsEgrIQ2 C0QAnRlz+hGllZ7xRdFCvW1Cgb5byWIs =Ka8V -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
