Hi, Since few year, I stopped to use the MINA ProtocolCodecFilter and associated stuff (CumulativeCodec..). for implementing my own codec independent of MINA.
it's just a service consuming ByteBuffer and pushing decoded POJO in a callback. The point is to be independent of MINA for example, parse & save files using the codec, or simply implement an HTTP version of the transport using old style servlet. Basically a decoder looks like : https://gist.github.com/4417934 One is instantiated by session. I'm quite happy with that and I think we should not port the old ProtocolCodeFilter to MINA 3.0 and replace it with a independent MINA async decoder framework (consuming BB, accumulating if needed and producing pojo). Julien
