Hi guys,
right now, Julien and I have experimented the MINA 3.0 branch writing a
Http codec and a Ldap codec. So far, so good, for basic scenario it
works well.
Now, I'd like to know if it would be a good idea to move the
ProtocolCodecFilter we have in MINA 2 to MINA 3? The rational would be
to just expose two interfaces for implementers :
- ProtocolEncoder
- ProtocolDecoder
otherwise, an implementer has to code the full Filter logic :
- messageReceived
- messageWriting
- sessionClosed
- sessionCreated
- sessionIdle
- sessionOpened
even if most of them are not necessary.
Just wondering...
Also it might be a good idea to define an AbstractFilter class that
implements the Filter methods, to avoid having to implement them
everytime we write a filter (for instance, sessionIdle() method is
unlikely to be handled in all the filters)
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
