[whatwg] WebSockets: what to do when there are too many open connections
ash at ashleysheridan.co.uk
Wed May 12 11:06:51 PDT 2010
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>
> 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?
I would imagine primarily it's out of concern for the remote host.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg