-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Filip,
Filip Hanik - Dev Lists wrote: | the solution is to not store stuff in the session modified by other | threads, if that's the case, then its not really something you wanna | store in a session What's wrong with modifying something in a session? It's not being modified by "other threads"... it's being modified by request-handling threads. The only synchronization issue is that the replication code basically needs to take a snapshot of the session, but that's not possible because there is no standard way to do it. I suppose if you have to modify something in the session, you can copy-and-modify and then put it back... but that's not very efficient. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkeUs58ACgkQ9CaO5/Lv0PC0+gCgkJ4m+eEoozj6fFth0KIE+tC+ mYEAn0oYsxUCiFoGxA7U2Ub+aWE/NcBX =YrnX -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
