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

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

From: Mike Shaver <mike.shaver@gmail.com>
Date: Thu, 13 May 2010 13:40:09 -0400
Message-ID: <AANLkTingO-fxFHQAqFX-Bdx3xZQplmKyTKoFU3YlWGJ4@mail.gmail.com>
On Thu, May 13, 2010 at 1:19 PM, Perry Smith <pedzsan at gmail.com> wrote:
> Hosts have limits on open file descriptors but they are usually in the ten's of thousands (per process) on today's OSs.

I have to admit, I'd be a little surprised (I think pleasantly, but
maybe not) if I could open ten thousand file descriptors on the latest
shipping Windows CE, or for that matter on an iPhone.

The question is whether you queue or give an error.  When hitting the
RFC-ish per-host connection limits, browsers queue additional requests
from <img> or such, rather than erroring them out.  Not sure that's
the right model here, but I worry about how much boilerplate code
there will need to be to retry the connection (asynchronously) to
handle failures, and whether people will end up writing it or just
hoping for the best.

Received on Thursday, 13 May 2010 10:40:09 UTC

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