Well that's unacceptable as you said as it's also block people behind NAT gateways.<br><br>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..<br>
<br><div class="gmail_quote">On Tue, Nov 23, 2010 at 19:34, tsuna <span dir="ltr"><<a href="mailto:tsunanet@gmail.com">tsunanet@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Tue, Nov 23, 2010 at 6:45 AM, Ersin ER <<a href="http://ersin.er" target="_blank">ersin.er</a>@<a href="http://gmail.com" target="_blank">gmail.com</a>> wrote:<br>
> That's why I am asking what I can do with Netty at the connection level.<br>
<br>
</div>But then the only thing you can do is to allow each IP address to<br>
connect only once to your server. This will prevent all the users<br>
behind firewalls or modem routers from playing if there's already<br>
another user playing from the same network, which is going to be a<br>
very frequent problem for your users.<br>
<br>
I don't recommend doing that, but if you really do, it's pretty<br>
simple, you can create a ConcurrentHashSet and whenever a client<br>
connects, you check if its IP is already in the set. If it is, you<br>
deny the connection, otherwise you store the IP in the set and let it<br>
proceed.<br>
<font color="#888888"><br>
--<br>
Benoit "tsuna" Sigoure<br>
Software Engineer @ <a href="http://www.StumbleUpon.com" target="_blank">www.StumbleUpon.com</a><br>
</font><div><div></div><div class="h5">_______________________________________________<br>
netty-users mailing list<br>
<a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/netty-users" target="_blank">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ersin Er<br>