On Tue, May 13, 2025 at 5:22 PM Mark Thomas <ma...@apache.org> wrote: > > 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?
It was Oracle's decision basically: - The necessary fixes and refactorings were finally made in NIO, long after I expected them to happen. - Features were added that were not added to NIO2 (inherited channel and domain sockets). As a result, I would recommend removing NIO2 from Tomcat 12 since there's no point keeping it. I volunteer to do it. Since the connector stays in Tomcat 11 and will be kept in sync, it can be resurrected easily. This should address Michael's concern. Also APR is very different since it needs a very costly to maintain native library to work. Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
