James Im <[EMAIL PROTECTED]> writes: > Which architecture do you prefer/use? why?
Though I'm working on a client, I'll still chime in. The ProtocolCodecFilter just formalizes a particular intention of a filter -- reshaping the type of the message, with symmetric translation "in" or "out". The ProtocolCodecFilter is an implementation of an IoFilter that delegates more specific and relevant calls to your encoder and decoder. Using it makes the protocol-specific code's purpose more obvious. Also, at least on the decoding side, the ProtocolCodecFilter can be plugged together with some helpful implementations like CumulativeProtocolDecoder and TextLineDecoder. -- Steven E. Harris
