IMO we should create a codec module not depending on core (perhaps only
for tests) with codec API, base codec (cumulative stuff and textLineCodec).
Each big codec like http or ldap should have it's own module.
What do you think ?
On Mon, Jan 14, 2013 at 1:38 PM, Emmanuel Lécharny
I started refactoring MINA 3 HTTP Codec, but I wonder how to share the
codec infertaces (ProtocolDecoder.class and ProtocolEncoder.class) between
MINA 3 and MINA 2 ? a separate module ?
Because if we don't do that we will finish by having the two version
depending of each other like with the
Le 1/14/13 10:55 AM, Julien Vermillard a écrit :
I started refactoring MINA 3 HTTP Codec, but I wonder how to share the
codec infertaces (ProtocolDecoder.class and ProtocolEncoder.class) between
MINA 3 and MINA 2 ? a separate module ?
Because if we don't do that we will finish by having the
I wasn't thinking about making MINA 2 Codfec stuff comatible with MINA 3
ones, just wondering how we share the framework independent API.
If you want to use the codec, with.. let's say plain java.net.Socket
blocking stuff. It would be stupid to depend the whole MINA3 core ?
Julien
On Mon, Jan
Something like org.apache.commons.codec.Decoder
and org.apache.commons.codec.Encoder but modernized with ByteBuffer /
generics. so you can only depend of this third party jar.
Julien
On Mon, Jan 14, 2013 at 1:26 PM, Julien Vermillard jvermill...@gmail.comwrote:
I wasn't thinking about making
Le 1/14/13 1:26 PM, Julien Vermillard a écrit :
I wasn't thinking about making MINA 2 Codfec stuff comatible with MINA 3
ones, just wondering how we share the framework independent API.
If you want to use the codec, with.. let's say plain java.net.Socket
blocking stuff. It would be stupid to
Demuxingiohandler .. what a moronic piece of code, it s sure you
should not depend on that. In place of switch case you should use
polymorphism (visitor pattern fits).
BTW the OutOfOrderExecutor Will process your two messages in two // threads.
--
Julien Vermillard
Le 12 janv. 2013 à 08:09,
Hi !
I did some experiment with the LDAP codec today. It's not exactly easy
to check if it can work safely with MINA 3, as it's almost impossible to
write a standalone LDAP codec in MINA without doing some huge
modifications in the LDAP API code.
I think it should be done the other way out : the
