Hi Yeah the sync=true|false is an endpoint configuration. It's not per. request based. So you might need to expose two endpoints: - one with sync=true - and one with sync=false if that is what you need.
On Tue, Nov 11, 2008 at 3:23 PM, Jeff V <[EMAIL PROTECTED]> wrote: > > My case is not what you are describing. > > My client will send a message to which there is no response or request. > Messages to the client will no always get a response either. > > Correct me if I'm wrong, please, but from what I have found through the docs > and some experimenting: > > If I set async=true I cannot send messages out, it becomes > exchangePattern=InOnly. Or, at least I am not seeing any messages coming out > of the TCP socket. > > If I set async=false, then it is not asynchronous. My incoming <Event/> > messages would block for a response that will never come. > -- > View this message in context: > http://www.nabble.com/Can-mina%3A%3Atcp-do-asyncronous-bidirectional-messages--tp20431804s22882p20440549.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- /Claus Ibsen Apache Camel Committer Blog: http://davsclaus.blogspot.com/
