You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BOLT use -Dcom.alipay.remoting.client.log.encode to control bolt framework log encoding, why not use file.encoding directly? Just like sofa-rpc log-conf.xml, so developers can use one configuration to control all logs encoding.
The text was updated successfully, but these errors were encountered:
* (tuning) refactor start logic of remoting server
fix#8 (#21)
* tuning init logic of rpc server (#20)
fix#18
* (tuning) modify buffer allocator type
fix#9 (#23)
* (format) modify header format (#24)
fix#10
* (tuning) log conf modify (#25)
fix#12#13
* (format) modify license format
* fix maven-javadoc-plugin build ERROR with JDK 1.8 (#28)
* fix threadpools shutdown problems (issues 14) (#31)
单测待补充,先合并
* [feature] support the native transport
* merge feature/1.4.2
* [feature] support native transport (epoll)
* add autor
* make the bossGroup not deamon
* (bugfix) modify boss threadpool back to non-daemon
* [feature] support the native transport
* merge feature/1.4.2
* [feature] support native transport (epoll)
* add autor
* make the bossGroup not deamon
* rebase 1.4.2
* (feature) Netty epoll switch
* (version) modify release version
* Tuning/threadpool exit (#36)
* (tuning) change command factory visibility (#37)
* format error
BOLT use
-Dcom.alipay.remoting.client.log.encode
to control bolt framework log encoding, why not usefile.encoding
directly? Just like sofa-rpc log-conf.xml, so developers can use one configuration to control all logs encoding.The text was updated successfully, but these errors were encountered: