W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2010

[whatwg] WebSockets: what to do when there are too many open connections

From: Ashley Sheridan <ash@ashleysheridan.co.uk>
Date: Wed, 12 May 2010 19:06:51 +0100
Message-ID: <1273687611.21168.243.camel@localhost>
On Wed, 2010-05-12 at 11:01 -0700, Ojan Vafai wrote:
> On Wed, May 12, 2010 at 4:31 AM, Simon Pieters <simonp at opera.com>
> wrote:
> 
>         establishing a WebSocket connection:
>         
>         [[
>         Note: There is no limit to the number of established WebSocket
>         connections a user agent can have with a single remote host.
>         Servers can refuse to connect users with an excessive number
>         of connections, or disconnect resource-hogging users when
>         suffering high load.
>         ]]
>         
>         Still, it seems likely that user agents will want to have
>         limits on the number of established WebSocket connections,
>         whether to a single remote host or multiple remote hosts, in a
>         single tab or overall. 
>         
> 
> 
> Why? Is the concern that we'd run out of memory? Overload the user's
> network connection?
> 
> 
> Ojan

I would imagine primarily it's out of concern for the remote host.

Thanks,
Ash
http://www.ashleysheridan.co.uk


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100512/27fb5ab5/attachment.htm>
Received on Wednesday, 12 May 2010 11:06:51 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:23 UTC