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
Le 12/30/12 6:16 PM, Julien Vermillard a écrit :
> Yes the timeout doesn't works correctly, I commited the test for Emmanuel.
> Looks like NIO async connect doesnt handle timeout like I thought.
Yep. As NIO is non-blocking, there is no need for a timeout. That means
you can't use the SO_TIMEOUT to
Yes the timeout doesn't works correctly, I commited the test for Emmanuel.
Looks like NIO async connect doesnt handle timeout like I thought.
Julien
Le 30 déc. 2012 17:51, "Alan Cabrera" a écrit :
>
> On Dec 29, 2012, at 1:14 AM, Julien Vermillard wrote:
>
> > Hi,
> > Just pushed the NioTcpClient
On Dec 26, 2012, at 4:52 AM, Emmanuel Lécharny wrote:
> Hi guys,
>
> as I discovered today (the information was buried in a mail about the
> site migration...), the release should *also* be pushed to svnpubsub. In
> other words, we should not move anything in
> /www/www.apache.org/dist/mina, but
On Dec 29, 2012, at 1:14 AM, Julien Vermillard wrote:
> Hi,
> Just pushed the NioTcpClient (new name for NioTcpConnector).
> It's basically working, I need to finish some stuff like connection timeout.
> But if you checkout the code it's very simpler than MINA 2 to dig in.
>
> I think the next s
