You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Stijn Haezebrouck <st...@gmail.com> on 2014/02/18 07:23:42 UTC
Netty listening producer
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.
Re: Netty listening producer
Posted by fraleocamel <fr...@gmail.com>.
I have the same issue.....
it sound very strange this is not supported , after all lot of legacy TCP/IP
interfaces support this exchange
did u progress on this topic ?
Franco
--
View this message in context: http://camel.465427.n5.nabble.com/Netty-listening-producer-tp5747456p5749896.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Netty listening producer
Posted by Cristiano Costantini <cr...@gmail.com>.
Ok! Good!
My username on github is "cristcost", when you have something shared, I'll
check it out!
Send me a message in case I miss the mail on this mailing list ;-)
Take your time,
Cristiano
2014-02-19 20:40 GMT+01:00 Thomas Termin <th...@gmail.com>:
> Hi Cristiano,
>
> the code is currently on my laptop only. But we could share it on github of
> course. Give me a few days so that we have at least a running version. I
> keep you informed.
>
> Currently the consumer side is working with connection type client and
> server. Client has automatic reconnecting handling.
>
> Thomas
>
>
> On Wed, Feb 19, 2014 at 12:44 AM, Cristiano Costantini <
> cristiano.costantini@gmail.com> wrote:
>
> > Hi Thomas,
> > where can I checkout the code you are working on?
> > Maybe I can write some test to help you in your work...
> >
> > Cristiano
> >
> >
> > 2014-02-18 20:21 GMT+01:00 Thomas Termin <th...@gmail.com>:
> >
> > > Hi,
> > >
> > > I'm currently working on porting the netty component to netty 4. I also
> > > implement that we can use client or server in consumer and producer.
> But
> > as
> > > I do this in my spare time it takes a little bit.
> > >
> > > Thomas
> > >
> > >
> > > On Tue, Feb 18, 2014 at 6:52 PM, Cristiano Costantini <
> > > cristiano.costantini@gmail.com> wrote:
> > >
> > > > 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 <cl...@gmail.com>:
> > > >
> > > > > Hi
> > > > >
> > > > > No this is currently not supported out of the box.
> > > > >
> > > > > On Tue, Feb 18, 2014 at 7:23 AM, Stijn Haezebrouck
> > > > > <st...@gmail.com> 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: cibsen@redhat.com
> > > > > 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
> > > > >
> > > >
> > >
> >
>
Re: Netty listening producer
Posted by Thomas Termin <th...@gmail.com>.
Hi Cristiano,
the code is currently on my laptop only. But we could share it on github of
course. Give me a few days so that we have at least a running version. I
keep you informed.
Currently the consumer side is working with connection type client and
server. Client has automatic reconnecting handling.
Thomas
On Wed, Feb 19, 2014 at 12:44 AM, Cristiano Costantini <
cristiano.costantini@gmail.com> wrote:
> Hi Thomas,
> where can I checkout the code you are working on?
> Maybe I can write some test to help you in your work...
>
> Cristiano
>
>
> 2014-02-18 20:21 GMT+01:00 Thomas Termin <th...@gmail.com>:
>
> > Hi,
> >
> > I'm currently working on porting the netty component to netty 4. I also
> > implement that we can use client or server in consumer and producer. But
> as
> > I do this in my spare time it takes a little bit.
> >
> > Thomas
> >
> >
> > On Tue, Feb 18, 2014 at 6:52 PM, Cristiano Costantini <
> > cristiano.costantini@gmail.com> wrote:
> >
> > > 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 <cl...@gmail.com>:
> > >
> > > > Hi
> > > >
> > > > No this is currently not supported out of the box.
> > > >
> > > > On Tue, Feb 18, 2014 at 7:23 AM, Stijn Haezebrouck
> > > > <st...@gmail.com> 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: cibsen@redhat.com
> > > > 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
> > > >
> > >
> >
>
Re: Netty listening producer
Posted by Cristiano Costantini <cr...@gmail.com>.
Hi Thomas,
where can I checkout the code you are working on?
Maybe I can write some test to help you in your work...
Cristiano
2014-02-18 20:21 GMT+01:00 Thomas Termin <th...@gmail.com>:
> Hi,
>
> I'm currently working on porting the netty component to netty 4. I also
> implement that we can use client or server in consumer and producer. But as
> I do this in my spare time it takes a little bit.
>
> Thomas
>
>
> On Tue, Feb 18, 2014 at 6:52 PM, Cristiano Costantini <
> cristiano.costantini@gmail.com> wrote:
>
> > 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 <cl...@gmail.com>:
> >
> > > Hi
> > >
> > > No this is currently not supported out of the box.
> > >
> > > On Tue, Feb 18, 2014 at 7:23 AM, Stijn Haezebrouck
> > > <st...@gmail.com> 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: cibsen@redhat.com
> > > 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
> > >
> >
>
Re: Netty listening producer
Posted by Thomas Termin <th...@gmail.com>.
Hi,
I'm currently working on porting the netty component to netty 4. I also
implement that we can use client or server in consumer and producer. But as
I do this in my spare time it takes a little bit.
Thomas
On Tue, Feb 18, 2014 at 6:52 PM, Cristiano Costantini <
cristiano.costantini@gmail.com> wrote:
> 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 <cl...@gmail.com>:
>
> > Hi
> >
> > No this is currently not supported out of the box.
> >
> > On Tue, Feb 18, 2014 at 7:23 AM, Stijn Haezebrouck
> > <st...@gmail.com> 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: cibsen@redhat.com
> > 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
> >
>
Re: Netty listening producer
Posted by Cristiano Costantini <cr...@gmail.com>.
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 <cl...@gmail.com>:
> Hi
>
> No this is currently not supported out of the box.
>
> On Tue, Feb 18, 2014 at 7:23 AM, Stijn Haezebrouck
> <st...@gmail.com> 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: cibsen@redhat.com
> 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
>
Re: Netty listening producer
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
No this is currently not supported out of the box.
On Tue, Feb 18, 2014 at 7:23 AM, Stijn Haezebrouck
<st...@gmail.com> 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: cibsen@redhat.com
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