On Fri, Dec 14, 2012 at 2:37 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > Have you checked the Netty documentation / forum? >
Norman from the Netty team said the ipfilter should be the way to do this http://static.netty.io/3.5/api/org/jboss/netty/handler/ipfilter/package-summary.html > And what do you mean by not allowed? Should the client be denied a > connection to the netty server, > or should the netty server, just "delay" until the 1st is done, and > then continue processing that? > > You can possible set the worker pool to have only 1 thread. > > On Wed, Dec 12, 2012 at 1:54 PM, kiranreddykasa <kirankuma...@fss.co.in> > wrote: >> Hi >> >> Is there any way we can restrict the number of clients that can connect the >> netty server ? >> For eg >> >> client 1 --->netty server >> >> client 2 ---->netty server >> >> the second connection should not be allowed while the first connection is >> active. >> >> Once the first connection is closed then second client can connect. >> >> >> >> ----- >> Regards >> >> kiran Reddy >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/camel-netty-restrict-connections-tp5723951.html >> Sent from the Camel - Users mailing list archive at Nabble.com. > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > FuseSource is now part of Red Hat > Email: cib...@redhat.com > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
