mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julien Vermillard <jvermill...@gmail.com>
Subject MINA 3.0 status
Date Mon, 06 Jun 2011 09:46:18 GMT
Hi !
Just a few heads up on current work on MINA 3.

As stated before, we are re-writing from scratch (but using MINA well
know interface/concepts) a simple NIO TCP server for experimenting
different strategy around NIO selector.

The work is done on this branch :

Here the current Javadoc :

Actually the NioTcpServer accept connections, write some basic bytes
and read incoming data in a SelectorProcessor. A SelectorProcessor is
a thread selecting/polling a bunch of sockets.

The main design change is the SelectorStrategy idea :
When you create a Service (server or client) you provide a
SelectorStrategy which will be in charge of providing the
SelectorProcessor for the different operations (accept, read, write).
So we can implements (and seriously benchmark) different SelectorStrategy like :
 - OneThreadSelectorStrategy (currently implemented) which will spawn
only one SelectorProcessor for handling all the operations
 - a processor thread for read, another for write, another for accept
 - a processor thread for each CPU
 - ...

The idea is to stress test few ideas and  find the winning scenario
for common use cases (connection less like HTTP, long living sessions,
write intensive protocols, latency, etc..)

I now need to plug a serious API for writing real tests : IoHandler
and perhaps a filter chain and a test environment.

For the IoHandler/ chain I'll dig in the ML archive, a lot of idea was
proposed, but for the test env, I'm a bit puzzled, does I'm supposed
to ask resources to infra ?

Any help/patch/review comment on the code is welcomed even if I
haven't much hope :)

View raw message