All,
This was mentioned briefly before (I think on a BZ issue) but needs a
wider discussion before taking action - if we do anything.
It has been suggested that there isn't much benefit to maintaining the
NIO2 connector and that we could simplify maintenance by removing it
(deprecating in 11.0.x, removing in 12.0.x). The current code structure
would be retained should there ever be an NIO3 or similar that we wanted
to add.
NIO and NIO2 performance is very similar.
The NIO2 code is arguably more complicated. I've always found it harder
to get me head around but that could just be me.
There is the odd bug with NIO2 we haven't been able to track down.
A similar case might be made for dropping NIO and only maintaining NIO2
although, as stated above, I have a preference for NIO over NIO2.
What do folks think?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
