Netty 5.0 以前是發(fā)布alpha版。聽說 Netty 5.0不繼續(xù)開發(fā)了。
為啥呢?看看GitHub上怎么作者怎么回復的吧?
The major change of using a ForkJoinPool increases complexity and has not demonstrated a clear performance benefit. Also keeping all the branches in sync is quite some work without a real need for it as there is nothin in current master which I think justifies a new major release.
Things that we should investigate to prepare for this change:
Deprecate exceptionCaught in ChannelHandler, only expose it in ChannelInboundHandler Expose EventExecutorChooser from MultithreadEventExecutorGroup to allow the user more flexibility to choose next EventLoop Add another method to be able to send user events both ways in the pipeline. (#4378)
主要意思:
使用ForkJoinPool增加了復雜性,并且沒有顯示出明顯的性能優(yōu)勢。同時保持所有的分支同步是相當多的工作,沒有必要。
詳情請看github地址:
https://github.com/netty/netty/issues/4466
更多建議: