Hi Claus, I have the same need of Stijn. Would you mind giving us an analysis for the feasibility of this feature, together with some hint on where to work into the code and list the task you expect need to be done to achieve this?
If it is feasible I would like to try to contribute, or at least help defining more clearly how to implement this functionality. Thank you very much, Cristiano 2014-02-18 18:19 GMT+01:00 Claus Ibsen <[email protected]>: > Hi > > No this is currently not supported out of the box. > > On Tue, Feb 18, 2014 at 7:23 AM, Stijn Haezebrouck > <[email protected]> wrote: > > Hello, we need to implement following setup: > > We have a system to which we need to send data (one way only), but where > the > > other system acts as a TCP/IP client. Hence, we should wait for an > incomming > > TCP/IP connection. Once established, we must send the data over this > > connection. > > So with netty, this would mean that we are the producer, however, netty > > should be listening on a socket rather then creating a connection. In > other > > words, we are the producer, but not the initiater of the connection. > > > > Can this be done using apache camel Netty? > > > > > > > > > > > > -- > > View this message in context: > http://camel.465427.n5.nabble.com/Netty-listening-producer-tp5747456.html > > Sent from the Camel - Users mailing list archive at Nabble.com. > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: [email protected] > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > Make your Camel applications look hawt, try: http://hawt.io >
