https://bz.apache.org/bugzilla/show_bug.cgi?id=69631
--- Comment #19 from Remy Maucherat <r...@apache.org> --- NIO2 is very clean, so initially when it was released it was better than NIO, which felt abandoned. Since then, roughly staring with Java 11, the following happened: - NIO got fixes and significant refactorings. - NIO got new features. - NIO2 did not get the new features. I don't see the trend reversing, so as a result, it might not be useful anymore to keep NIO2 in Tomcat 12. I'm not 100% sure yet though. Note: even if removed, it is important to keep things abstracted as if NIO is not the only endpoint implementation. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
