How to prevent multiple simultaneous connections from the same client?

[Ersin ER]

Well that's unacceptable as you said as it's also block people behind NAT
gateways.

Perhaps we may do something with incorporating client IP address (the
original one behind the NAT as well as the public NAT one) within the
packages. But I am not sure yet..

On Tue, Nov 23, 2010 at 19:34, tsuna <tsunanet at gmail.com> wrote:

> On Tue, Nov 23, 2010 at 6:45 AM, Ersin ER <ersin.er at gmail.com> wrote:
> > That's why I am asking what I can do with Netty at the connection level.
>
> But then the only thing you can do is to allow each IP address to
> connect only once to your server.  This will prevent all the users
> behind firewalls or modem routers from playing if there's already
> another user playing from the same network, which is going to be a
> very frequent problem for your users.
>
> I don't recommend doing that, but if you really do, it's pretty
> simple, you can create a ConcurrentHashSet and whenever a client
> connects, you check if its IP is already in the set.  If it is, you
> deny the connection, otherwise you store the IP in the set and let it
> proceed.
>
> --
> Benoit "tsuna" Sigoure
> Software Engineer @ www.StumbleUpon.com
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>



-- 
Ersin Er
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20101123/46d6b2f1/attachment.html