Hi And check the source code of camel-netty. Maybe you can spot an improvement to fit your need. But I think the answer is in the Netty community/documentation.
On Mon, Jun 6, 2011 at 8:09 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Mon, Jun 6, 2011 at 8:03 AM, Sachin <sachin2...@gmail.com> wrote: >> Thanks for your response,it's great to hear from Ibsen directly :) . >> I am already doing it as below. >> >> SocketAddress remoteAddress >> =exchange.getIn().getHeader(NettyConstants.NETTY_REMOTE_ADDRESS, >> SocketAddress.class); >> ChannelHandlerContext  channelHandlerContext =(ChannelHandlerContext) >> exchange.getIn().getHeader(NettyConstants.NETTY_CHANNEL_HANDLER_CONTEXT); >> SocketAddress localAddress = >> (SocketAddress)channelHandlerContext.getChannel().getLocalAddress(); >> >> But by this , i am only getting local and remote address, and to get socket >> object , i need to create a new socket object , which doesnt fulfill my >> scenario. >> >> I have to get same socket object, so that i can write my response back. >> Please guide me. >> > > Thats the stuff that Netty exposes to Camel. I suggest you ask/check > the Netty community/documentation for any pointers. > > >> Regards >> Sachin >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/Camel-with-Netty-strange-requirement-tp4450979p4457745.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: cib...@fusesource.com > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/ > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
