Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Filip,
Filip Hanik - Dev Lists wrote:
| no, its just common sense, given that the session should represent a
| client state,
| and by the time the cluster tries to serialize it, the request is over.
There's no guarantee that the request is complete before session changes
are replicated, is there? In that case, you can never manipulate any
collection you put into the session. If you want to change something,
you have to first remove it from the session, then change it, then put
it back.
In fact, you still are not covered, because removing the object from the
session merely removes the reference. If the session replicator is
running and copying, say, a Map to another machine in the cluster, you
can't even remove it from the session in order to modify it: you /must/
make a copy of it and work on the copy.
That's ridiculous IMHO.
read the source code and enlighten yourself instead of making
assumptions and making comments like that.
| developers misuse sessions all the time, I would add this into that
| category.
Of course they do, but modifying a collection that's in the session
while the replicator just happens to be trying to serialize the session
is simply unreasonable to prevent.
| one can use a technology like terracotta that handles replication
| completely separate from the request flow, and at the field level.
| that technology doesn't suffer from the problem described above
I'm not sure it would... iterating over a collection (which I assume is
what the session replicator is doing) while another thread (a request)
is making legitimate changes to it would lead to a CME no matter what
replication technology is being used.
even terracotta is open source, read the source code there, and correct
yourself
Filip
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkeXsiMACgkQ9CaO5/Lv0PBfmgCcCFnKujLG269RQ+y/vqyPTBMB
sVQAn1z1mIrDf92g0UsFKeKgH/etyY3F
=MCCh
-----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]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
