[
https://issues.apache.org/activemq/browse/CAMEL-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48084#action_48084
]
James Strachan commented on CAMEL-1077:
---------------------------------------
Yeah - I think the client and server endpoints would act similar; you could
route from them or to them. Whether there are 4 (including async + sync) or
whether sync/async mode is an extension or configuration of the endpoint is
maybe separate.
The main difference is the server endpoint would use the different connection
establishment.
Having
{code}
from("mina-server:localhost").bean(Somethings.class);
{code}
could then create a custom mina server with routing logic inside it. If folks
send to "mina:server:localhost" then it could use the connection details of the
server endpoint to know how to basically create a normal mina client producer
to talk to the server's socket etc
> tcp client mode / server mode determined by "to" or "from" elements limits
> usability.
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-1077
> URL: https://issues.apache.org/activemq/browse/CAMEL-1077
> 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
> Reporter: Jeff Vienneau
>
> Internally,
> MinaProducer is coded to create a Mina connector (client mode socket).
> MinaConsumer is coded to create a Mina acceptor (server mode socket).
> Additionally, it appears a producer (client mode socket) is created for a
> "to" route mapping and a consumer (server mode socket) is created for a
> "from" route mapping.
> This means an endpoint cannot be created in which the session is initiated by
> a client and messages are routed "to" the client.
> The opposite is also true, an endpoint with a "from" route mapping cannot
> establish a connection to a tcp server.
> This is a major limitation, as we do not often have control over the systems
> with which we are interfacing.
> Perhaps, the mina::tcp URI could have a parameter the sets the socket mode:
> tcp.mode=server or tcp.mode=client.
> Hope this make sense, thanks!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
