Implementing NIO for a client sockets which are always alive

I am newbie to MINA. I initially had implemented StreamIOHandler. It seems that it is still SYNCHRONOUS and not NIO based. Is my understanding correct ? Does this mean that I lose all the benefits of MINA because of this approach. -- View this message in context: http://www.nabble.com/Implement

Re: Implementing NIO for a client sockets which are always alive

quicksilverm28 wrote: I am newbie to MINA. I initially had implemented StreamIOHandler. It seems that it is still SYNCHRONOUS and not NIO based. Is my understanding correct ? Does this mean that I lose all the benefits of MINA because of this approach. Well, you are using Java NIO under the h

Re: Implementing NIO for a client sockets which are always alive

I also see that if I just overload messageReceived and remove StreamIOHaandler then I am getting partial bytes. Is there a workaround to this issue ? If there is no workaround, would it mean that streaming is impossible using NIO ? -- View this message in context: http://www.nabble.com/Implem

Re: AbstractIoSession and final qualifiers

Emmanuel Lecharny-3 wrote: > > While looking at the abstract class, I found some methods with this kind > of code : > > public final WriteFuture write(Object message, SocketAddress > remoteAddress) { > if (message == null) { > throw new NullPointerException("message");