Steven, Have a look at the diff that Trustin posted: http://tinyurl.com/2ar8ky
ProtocolCodecFilter stores a lock object in the session and locks on it before calling decoder.decode() As I see it, this means that no two threads can call decoder.decode for the same session simultaneously. Maarten On 3/28/07, Steven E. Harris <[EMAIL PROTECTED]> wrote:
Trustin Lee <[EMAIL PROTECTED]> writes: > By doing this, all decoders will be free from the visibility > problem. I missed the earlier part of this discussion. Does this mean that ProtocolDecoder.decode() calls will be synchronized to a particular decoder? That is, a given decoder instance will only be called on by one thread at a time? I thought we had discussed this earlier and confirmed that it was intentional that a decoder could be called on from multiple threads simultaneously. -- Steven E. Harris
