Thanks, Claus. One Camel message mapping to one netty message is quite
fine, but it needs to keep a persistent TCP connection for our purposes.
We have to send something akin to a "hello" packet that lets the server at
the TCP destination know what kind of data it will be receiving, and other
I think you would need to implement some custom codec or something to
deal with this kind of requirements.
The out of the box behavior is to use netty for messaging like where
each Camel message maps to one netty message being sent over the wire.
On Tue, Oct 18, 2016 at 7:29 PM, Steve973
