I have a Linux Java7 stand-alone application using Camel 2.14 and the *camel-netty* component. I have several routes that each receive a UDP feed via netty:udp.
I've already implemented a few routes that do this, but have used either a *DelimiterBasedFrameDecoder* or a *LengthFieldBasedFrameDecoder*, depending on whether the packets/messages in the UDP feed have a delimiter and/or a way for me to know the total length of the payload. Now I have another UDP feed that I need to create a route for, but this one has payload messages each containing a fixed 16-byte header and the rest of the message is encrypted. Therefore, I have no message delimiter or message length field to exploit. Here lies my confusion: shouldn't camel-netty be able to just produce a separate Exchange for each received UDP packet, regardless of its size or contents? Camel-netty interfaces to the UDP protocol and knows the size of each received packet. I'm starting to feel like maybe I've over-complicated things by using a *DelimiterBasedFrameDecoder * and/or *LengthFieldBasedFrameDecoder* in my ServerPipeline. Any help is greatly appreciated! Thanks, Steve -- View this message in context: http://camel.465427.n5.nabble.com/Camel-2-14-Netty-Separate-Exchange-for-each-UDP-packet-tp5769372.html Sent from the Camel - Users mailing list archive at Nabble.com.
