camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chad Beaulac (Updated) (JIRA)" <>
Subject [jira] [Updated] (CAMEL-2624) support for async responses on single tcp connection
Date Sun, 11 Mar 2012 15:33:58 GMT


Chad Beaulac updated CAMEL-2624:


Attached Mina2ClientServerTest and Mina2TcpSyncOutOnly.
The full-asych changes done so far affect how the template producer is used when the client
wants a response. The client uses the template.sendBody method and processes the response
asynchronously in the URI supplied ioHandler. The Mina2TcpSyncOutOnly tests that the processor
on the mina2 consumer side can recognize session creation and can asynchronously send messages
to a producer client. Please have a look at these tests and provide any comments you might
> support for async responses on single tcp connection
> ----------------------------------------------------
>                 Key: CAMEL-2624
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-mina2
>    Affects Versions: 2.2.0
>         Environment: any
>            Reporter: Anand
>            Assignee: Chad Beaulac
>             Fix For: 2.10.0
>         Attachments:,
> 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message