Hi Giving this a 2nd thought on the way home. I guess I would like to think about this some more.
Most components either support InOut or InOnly and not both (eg WebServiice = InOut, Http = InOut, JMS = InOnly) So I think it would be confusing if you can alter this behavior at runtime based on the content of the data received or being sent. So I guess it's best practice to expose 2 TCP listeners: - one for InOut - and another for InOnly On Tue, Nov 11, 2008 at 3:55 PM, Claus Ibsen <[EMAIL PROTECTED]> wrote: > Hi > > Yeah and that probably sucks for you. I am wondering if we could do > some content based (at runtime) what the message exchange pattern > should be to support your use-case. > > So being able to override and set the InOnly or InOut. Could you > create a ticket in JIRA for this request and then we could work on a > patch to get this feature in there if you need it badly ;) > > > /Claus > > On Tue, Nov 11, 2008 at 3:44 PM, Jeff V <[EMAIL PROTECTED]> wrote: >> >> Then, my client would need to connect to two different ports? >> >> >> Claus Ibsen-2 wrote: >>> >>> 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/ >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Can-mina%3A%3Atcp-do-asyncronous-bidirectional-messages--tp20431804s22882p20440992.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> >> > > > > -- > > /Claus Ibsen > Apache Camel Committer > Blog: http://davsclaus.blogspot.com/ > -- /Claus Ibsen Apache Camel Committer Blog: http://davsclaus.blogspot.com/
