[
https://issues.apache.org/activemq/browse/CAMEL-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47388#action_47388
]
Jeff Vienneau commented on CAMEL-1075:
--------------------------------------
Re: #4, We're talking: "connect to a server and receive massages", not connect
to a server and send "Hello World" and wait for a response, that's
*syncronous*.
I'm talking *asyncronous*. Connect to a server, leave the connection open and
if it sends a message, route the message, otherwise keep the socket alive and
keep waiting.
We know the system can do InOut syncronous. but what I am talking about is:
*Two way* message routing of *asyncronous* messages irrespective of the means
to establish the connection.
With all due respect, I have been prototyping and reading the code. You are
misinterpreting me.
I am trying to point out a need that I have with the system that is lacking for
the greater good of Camel Mina. I will be solving my problem with a hand
cobbled component, but I just wanted to point out the issue. If I end up with
something of quality I will post it in the forum.
> mina tcp: support for asyncronous InOut endpoint.
> -------------------------------------------------
>
> Key: CAMEL-1075
> URL: https://issues.apache.org/activemq/browse/CAMEL-1075
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-mina
> Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
> Environment: All.
> Reporter: Jeff Vienneau
>
> Mina Component does not support async InOut connections.
> Many applications require two way or out only async tcp connections this is
> not supported.
> See a more full discussion on this here:
> http://www.nabble.com/Can-mina::tcp-do-asyncronous-bidirectional-messages--tc20431804s22882.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
