On Jun 7, 2007, at 8:37 AM, Chris Audley wrote:
Why does MINA limit one ProtocolCodecFilter in an IoFilterChain?
you can only go from ByteBuffer -> non-ByteBuffer once :)
This seems to be an unnecessary limitation. What if I want to use a series of codecs in order to build more complicated behaviours. I could have aline oriented filter that converts between ByteBuffers and lines, another that converts between lines and paragraphs and another that converts between paragraphs and chapters.
absolutely.. But the ProtocolCodecFilter is Byte-Buffer centric, so you can't use it as a building-block as-is. If you want to refactor it to make it non-BB centric and contribute it back, that'd rock!
Or, as in my case, I may just want to add multiple unrelated codecs. In my web proxy filter, I wan't to use an HTTP codec to handle the CONNECTrequest and response. After the web proxy filter is done connecting through the proxy, it will remove the HTTP codec and another protocolcodec installed behind the web proxy filter can handle remainder of thesession.
You can absolutely do this.. Remove the first PCF instance and add a new one.. The limitation is just one at a time, not one for all time :)
-pete -- [EMAIL PROTECTED] - http://fotap.org/~osi
smime.p7s
Description: S/MIME cryptographic signature
