On Thu, May 27, 2010 at 11:45 AM, John Tamplin wrote:
> On Thu, May 27, 2010 at 10:28 AM, Simon Pieters wrote:
>>
>> 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 Linux, that is just the default
On Thu, May 27, 2010 at 10:28 AM, Simon Pieters wrote:
> 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 Linux, that is just the default (which may vary between distros) and can
be configured by the
On Thu, 13 May 2010 16:47:34 +0200, Simon Pieters wrote:
On Wed, 12 May 2010 20:01:11 +0200, Ojan Vafai wrote:
On Wed, May 12, 2010 at 4:31 AM, Simon Pieters wrote:
establishing a WebSocket connection:
[[
Note: There is no limit to the number of established WebSocket
connections
a use
On May 13, 2010, at 9:00 PM, Boris Zbarsky wrote:
> On 5/13/10 7:55 PM, Perry Smith wrote:
>> Its not that hard and it won't happen that often. And it gives
>> the javascript authors more control and choices.
>
> If a situation doesn't happen often, then historically speaking most authors
> wi
On 5/13/10 7:55 PM, Perry Smith wrote:
Its not that hard and it won't happen that often. And it gives
the javascript authors more control and choices.
If a situation doesn't happen often, then historically speaking most
authors will have no provisions to handle it. Try browsing the web with
I think that queuing in chrome bends the intent of the createWorker api just
a little too far and will be happy to see it go away. I'd rather it failed
outright then pretend to succeed when it really hasn't.
(Actually that queuing code complicates the impl somewhat too... can you
tell its been ann
As an example from a bit different area, in Chrome the Web Workers today
require a separate process per worker. It's not good to create too many
processes so there is a relatively low limit per origin and higher total
limit. Two limits help avoid situation when 1 bad page affects others. Once
limit
On May 13, 2010, at 12:40 PM, Mike Shaver wrote:
> The question is whether you queue or give an error. When hitting the
> RFC-ish per-host connection limits, browsers queue additional requests
> from or such, rather than erroring them out. Not sure that's
> the right model here, but I worry ab
On Thu, May 13, 2010 at 1:40 PM, Mike Shaver wrote:
> 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.
ulimit -n tells me I can only open 1024 per pr
On Thu, May 13, 2010 at 1:19 PM, Perry Smith 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 descrip
On Thu, May 13, 2010 at 1:19 PM, Perry Smith wrote:
> >>> [[
> >>> 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
>
On May 13, 2010, at 10:05 AM, Simon Pieters wrote:
> On Wed, 12 May 2010 20:51:59 +0200, Michael Nordman
> wrote:
>
>> On Wed, May 12, 2010 at 4:31 AM, Simon Pieters wrote:
>>
>>> establishing a WebSocket connection:
>>>
>>> [[
>>> Note: There is no limit to the number of established WebSock
On Wed, 12 May 2010 20:51:59 +0200, Michael Nordman
wrote:
On Wed, May 12, 2010 at 4:31 AM, Simon Pieters 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 c
On Wed, 12 May 2010 20:01:11 +0200, Ojan Vafai wrote:
On Wed, May 12, 2010 at 4:31 AM, Simon Pieters 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 refu
On Wed, May 12, 2010 at 4:31 AM, Simon Pieters 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 con
On Wed, 2010-05-12 at 11:01 -0700, Ojan Vafai wrote:
> On Wed, May 12, 2010 at 4:31 AM, Simon Pieters
> wrote:
>
> establishing a WebSocket connection:
>
> [[
> Note: There is no limit to the number of established WebSocket
> connections a user agent can h
On Wed, May 12, 2010 at 4:31 AM, Simon Pieters 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 con
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 sufferin
18 matches
Mail list logo
