Somebody asked me about this so I'm sharing my response with the list. The question was, how do I do this now if the functionality doesn't exist in camel-mina2 yet.
Response: I've been working, off and on, to get this functionality into camel-mina2. Unfortunately, my schedule with customers keeps putting this on the back burner. My projects have asynchronous and synchronous TCP/UDP I/O between Java and C++ components. I wrote a Google Protocol Buffers for mina2. I ported that codec to C++ also. Synchronous Comms Approach 1) Messages are defined in Google Protocol Buffers (GBP) using extensions 2) camel-mina2 endpoints are used for Java subsystems. 3) If we don't expect a reply for a given message, we set route to asynch. If reply can vary, we always send a reply and just send an empty GPB message for handshaking sometimes Asynchronous Comms Approach 1) Messages are defined in Google Protocol Buffers (GBP) using extensions 2) mina2 socket servers and clients are implemented directly using Mina version 2. 3) C++ side is same in both approaches Chad Beaulac Objective Solutions, Inc. www.objectivesolutions.com c...@objectivesolutions.com On Aug 18, 2012, at 9:21 AM, Chad Beaulac wrote: > I'm working on this now. I have some unit tests written and working. I hope > to post a patch for review soon. > The current approach allows you to attach a Mina IoHandler to a Mina2 > endpoint. The IoHandler receives "n" messages from the consumer and can send > "m" responses. > > -Chad > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Asynchronous-socket-read-write-via-camel-tp5503650p5717650.html > Sent from the Camel - Users mailing list archive at Nabble.com.
