Re: ProtocolCodecFilter change of behavior in 2.0.0-RC1

2010-03-13 Thread Ashish
On Sun, Mar 14, 2010 at 9:38 AM, John Fallows wrote: > Thanks Emmanuel. > > Good to see you were already on top of this six months ago!  Sorry that I > didn't consider checking the trunk. > > Is there any word on when we might expect a post 2.0.0-RC1 release, either > 2.0.0-RC2 or 2.0.0 final? We

Re: ProtocolCodecFilter change of behavior in 2.0.0-RC1

2010-03-13 Thread John Fallows
Thanks Emmanuel. Good to see you were already on top of this six months ago! Sorry that I didn't consider checking the trunk. Is there any word on when we might expect a post 2.0.0-RC1 release, either 2.0.0-RC2 or 2.0.0 final? Kind Regards John Fallows On Mar 13, 2010, at 5:58 PM, Emma

Re: ProtocolCodecFilter change of behavior in 2.0.0-RC1

2010-03-13 Thread Emmanuel Lecharny
On 3/14/10 1:03 AM, John Fallows wrote: Folks, There appears to be a change of behavior in ProtocolCodeFilter due to the previously non-static and now-static nature of the attribute keys used to cache the encoder, encoder output, decoder and decoder output. Is there any objection to rever

ProtocolCodecFilter change of behavior in 2.0.0-RC1

2010-03-13 Thread John Fallows
Folks, There appears to be a change of behavior in ProtocolCodeFilter due to the previously non-static and now-static nature of the attribute keys used to cache the encoder, encoder output, decoder and decoder output. Specifically, the pre-2.0.0-RC1 code private final AttributeKey ENCODER =