Fine. Leave the WeakHashmap the way it is. But synchronizing on the
servlet session is a -1 for me. That could have unknown consequences
since the object is owned by the container, not Cocoon. See my other
post. Sorry - my ISP has had severe email problems the last few days
and so I have been lagging behind the discussion.
Ralph
Nathaniel Alfred wrote:
You are proposing to pollute the container session with a parasitic
attribute. Even if the Serialable issue of that wrapper object was
solved, that is still a -1 for me. Let's keep the session clean!
Cheers, Alfred.