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
Netty's native transport is available on linux, is more performant and has optimized memory footprint.
Since, it is a choice based on the OS, it will force people to write conditional code in the client and servers to flip the transport when available. On top of it, there would not be any standardization for an application owner to switch to native transports (when available and applicable for a client/server) if required.
RxNetty should provide a way to globally use native transport for an application via static method calls in RxNetty factory class. This setting should follow the following rules:
It should be considered when a server or client has not explicitly chosen a transport (via the channel and eventloop implementation).
If the transport implementation is applicable for that server/client. UDP is not supported by the native transport.
The text was updated successfully, but these errors were encountered:
If it is required to globally turn on/off the use of native transport, RxNetty provides two methods:
Enable
RxNetty.useNativeTransportIfApplicable() Enables use of native transport wherever applicable (TCP/HTTP/Websockets client and servers)
Disable
RxNetty.disableNativeTransport() Disables the use of native transport. If any client/server explicitly uses the native transport, that is not effected.
Additional dependency
Since, this is using the native transport of netty it requires the binary for the OS, the application is intended to be used.
In order to get the OS specific binary for linux, one can use the following gradle dependency:
Netty's native transport is available on linux, is more performant and has optimized memory footprint.
Since, it is a choice based on the OS, it will force people to write conditional code in the client and servers to flip the transport when available. On top of it, there would not be any standardization for an application owner to switch to native transports (when available and applicable for a client/server) if required.
RxNetty should provide a way to globally use native transport for an application via static method calls in
RxNetty
factory class. This setting should follow the following rules:The text was updated successfully, but these errors were encountered: