camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-2624) support for async responses on single tcp connection
Date Tue, 19 Feb 2013 13:19:13 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581255#comment-13581255
] 

Claus Ibsen commented on CAMEL-2624:
------------------------------------

If you want fine grained events for session open / partly packages received / and whatnot
then you should use a custom mina codec (or what they call it).

Its not a good model to fire empty Camel Exchange in routes for these kind of events. The
normal use-case is 1 Exchange per complete message received. If people want something different,
then use a custom codec to hook into these events. And/or use the Mina API directly.
                
> support for async responses on single tcp connection
> ----------------------------------------------------
>
>                 Key: CAMEL-2624
>                 URL: https://issues.apache.org/jira/browse/CAMEL-2624
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-mina2
>    Affects Versions: 2.2.0
>         Environment: any
>            Reporter: Anand
>            Assignee: Chad Beaulac
>             Fix For: Future
>
>         Attachments: Mina2ClientServerTest.java, Mina2TcpAsyncOutOnly.java
>
>
> Mina Component does not support async InOut connections.
> Many applications require two way or out only async tcp connections this is not supported.
> Single TCP connection to external server. Ability to send multiple requests one after
the other without waiting for a response. responses need to be processed asynchronously.
> h5. Use Cases to Support
> # UC-1 - Consumer sends messages after connect
> ## TCP producer (P1) connects to TCP consumer/server (C1), session is created
> ## C1 sends many messages to P1
> ## P1 receives messages and processes them
> ## C1 or P1 close the connection
> # UC-2 - Full async session
> ## P1 connects to C1
> ## P1 and C1 send and receive messages ansynchronously. There is no blocking write-read
loop.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message