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

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

From: Simon Pieters <simonp@opera.com>
Date: Thu, 27 May 2010 16:28:16 +0200
Message-ID: <op.vddbteksidj3kv@simon-pieterss-macbook.local>
On Thu, 13 May 2010 16:47:34 +0200, Simon Pieters <simonp at opera.com> wrote:

> On Wed, 12 May 2010 20:01:11 +0200, Ojan Vafai <ojan at chromium.org> 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?
>
> If nothing else, the underlying OS might have a limit on the number of  
> open connections.

 From our testing it seems that Vista has a limit of 1398 open sockets.  
Apparently Ubuntu has a limit of 1024 file descriptors per process.

On low-end devices and low-end networks, it seems likely that there's a  
relatively low limit on the number of connections.

-- 
Simon Pieters
Opera Software
Received on Thursday, 27 May 2010 07:28:16 UTC

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