WebSocket with scalability

[mheath]

The problem is not a 64k ports per host, it's 64k ports per IP address. So,
you can always bind multiple IP addresses to a single interface and use that
to overcome this scalability problem. The software proxy, of course, has to
be aware of the availability of multiple IP addresses and be able to
leverage them.

-Mike

On Tue, Aug 9, 2011 at 4:17 AM, ljohnston [via Netty Forums and Mailing
Lists] <ml-node+6667589-961205527-177308 at n2.nabble.com> wrote:

>  Benoit Perroud wrote:
> In the scenario of scaling websocket, using any software proxy won't
> scale to more than 64'000 connections, which is the number of port
> (ipv4) the proxy can open to forward incoming connection to processing
> nodes.
>
> Slight correction (hope you don't mind), the limitation on the number of
> ports is a feature of TCP (and UDP) which defines unsigned 16 bit fields for
> the source and destination port numbers.
>
> IP (either V4 or V6) only knows about IP addresses.
>
> Just in case anyone was thinking IPv6 might change things - it won't
> although it may eventually result in even more clients wanting to connect to
> your limited number of ports simultaneously :)
>
> Cheers
> Lee
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://netty-forums-and-mailing-lists.685743.n2.nabble.com/WebSocket-with-scalability-tp6665887p6667589.html
>  To unsubscribe from Netty Forums and Mailing Lists, click here<http://netty-forums-and-mailing-lists.685743.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=685743&code=bWhlYXRoQGFwYWNoZS5vcmd8Njg1NzQzfC0xMDg2MTY2MDU=>.
>
>


--
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/WebSocket-with-scalability-tp6665887p6668914.html
Sent from the Netty User Group mailing list archive at Nabble.com.