camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-1075) mina tcp: support for asyncronous InOut endpoint.
Date Tue, 19 Jan 2010 17:17:43 GMT


Claus Ibsen commented on CAMEL-1075:

[18:14]  <jgenender> cibsen: Hehe... you need to get creative on that ;-)
[18:15]  <jgenender> cibsen: I used Hashmaps with message ID s
[18:15]  <jgenender> cibsen: Many ways to do it
[18:15]  <cibsen> and the message ids then have to part of the data send over the wire?
[18:15]  <jgenender> cibsen: You can do it via session id
[18:15]  <cibsen> what if I use some old custom text based protocol which does not offer
a field for that
[18:16]  <jgenender> The socket session is unique
[18:16]  <cibsen> ah cool that is what I liked to hear
[18:16]  <cibsen> yeah then a map is sufficient
[18:16]  <jgenender> So create a Hashmap that correlates teh session id (the socket)
to information on the client and you have what you need
[18:16]  <jgenender> You can even create state and store it in the hashmap
[18:16]  <cibsen> :) like it already

> mina tcp: support for asyncronous InOut endpoint.
> -------------------------------------------------
>                 Key: CAMEL-1075
>                 URL:
>             Project: Apache Camel
>          Issue Type: New Feature
>          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
>             Fix For: Future
> 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:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message