Le 11/17/12 7:42 AM, Julien Vermillard a écrit :
well I strongly disagreeing here :)
The selector listener and the selector loop should be seen as a wrapper on
top of nio to make things easier.
I don't disagree here.
The event can happen at the same moment so we need to provide them as is
Hi guys,
I looked at the SelectorListner interface and its implementation.
Here is the hierarchy of classes implementing this interface :
(SelectorListener)
o
|
+-- [NioTcpServer]
|
+-- [NioUdpServer]
|
+-- [NioTcpSesession]
The interface
well I strongly disagreeing here :)
The selector listener and the selector loop should be seen as a wrapper on
top of nio to make things easier.
The event can happen at the same moment so we need to provide them as is
and not to choose the order to propagate them.
It's up to the listener to
