This is for both came and mina reasons.
The scenario is to support request-reponse and "fire-and-forget"
exchanges (InOut and InOnly)
Camel as TCP Server (MinaProducer)
InOut is used if you as a TCP server want to be able to send a
response back to the client
InOnly is used if you as a TCP server does not send a response back.
This can be used for eg. a TCP logging server or the likes.
Camel as a TCP client (MinaConsumer)
InOut is for sending to a remote TCP server and wait for a response
InOnly is for sending to a remote TCP server and *not* wait for a response
So the sync=true|false and thus the ExchangePattern InOut or InOnly
instructs Camel and Mina how to operate.
On Tue, Nov 11, 2008 at 4:09 PM, Jeff V <[EMAIL PROTECTED]> wrote:
>
> Do you know if the limitation is in Mina or the Camel-Mina component?
>
> It in the mina component sync determines the exchange pattern:
>
> // set sync or async mode after endpoint is created
> if (sync) {
> endpoint.setExchangePattern(ExchangePattern.InOut);
> } else {
> endpoint.setExchangePattern(ExchangePattern.InOnly);
> }
>
> From:
> http://svn.apache.org/viewvc/activemq/camel/tags/camel-1.5.0/components/camel-mina/src/main/java/org/apache/camel/component/mina/MinaComponent.java?view=markup
> http://svn.apache.org/viewvc/activemq/camel/tags/camel-1.5.0/components/camel-mina/src/main/java/org/apache/camel/component/mina/MinaComponent.java?view=markup
>
> Is this because it has to for proper mina operatio or camel component
> reasons?
> --
> View this message in context:
> http://www.nabble.com/Can-mina%3A%3Atcp-do-asyncronous-bidirectional-messages--tp20431804s22882p20441499.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
