Thanks Ioannis however the 'responses' are never ending. Which is why I mentioned its like pub/sub.
The two applications I have use an 'always open' TCP connection where the in and out messages streams are effectively 'sessionless'. E.g. TCP Client opens connection with TCP Sever Listener . Client sends a message to Srv. Srv continually sends messages to cli over the same connection. (Plus there may be the possiblity that the client sends further messages in the future). So a gathering strategy will not work here! What I require is the request and response channels to work independently. DO you think camel can support this? -- View this message in context: http://camel.465427.n5.nabble.com/Single-request-with-multiple-replies-over-TCP-tp5022206p5022909.html Sent from the Camel - Users mailing list archive at Nabble.com.
