Re: [hybi] Addressing Minimal Events

There are different reasons for imposing a limit on the number of HTTP
connections. A page with 100 images might innocently cause 100 HTTP
connections to open simultaneously. A malicious page might
intentionally do the same with embedded content.

In the case of malicious cross-origin connections, a WebSocket server
should have all the information it needs to close them quickly.

As far as client-side congestion goes, we leave it up to authors to
police themselves regarding their CPU usage and memory consumption.
Badly behaved sites get complaints and drive away their users. I see
this the same way.

-Frank

On Thu, Apr 16, 2009 at 12:19 AM, Greg Wilkins <gregw@webtide.com> wrote:
> Frank Salim wrote:
>>>
>>> Connections are a real problem and I believe that the Websocket
>>> API will encourage the usage of more sockets.
>>
>> WebSockets are not subject to the browsers' restrictions on the number
>> of HTTP connections. I don't think this is a problem.
>
> Frank,
>
> Avoiding the limit doesn't avoid the good reasons the limit was put there
> in the first place.
>
> regards
>
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>