hakan eryargi a écrit :
hi,
how can i guarantee messages are processed in arrival order and
sequantially (one is processed after previous is completed) for
NioSocketAcceptor ?
This is guaranteed, as soon as you don't inject an ExecutorFilter in
your chain (see [1] for more info about this
hakan eryargi a écrit :
thanks, that's quite descriptive :)
speaking of blocking, how is IoSession.write(message) is handled ? all
sessions share same thread pool ? is there a chance writing messages
is blocked because one end point is not reading ? as possibly you
know, that can be the case if
cool. my server is using blocking io at the moment, with two threads
(read/write) for each connection. once a message is read, it's
processed in reading thread, with no explicit queing and hence message
order in session is preserved but message order among sessions are
subject to race condition.
