Re: [hybi] WebSocket connection throttling clarification requested

[Simone Bordet <[e-mail]>]

Hi,

On Wed, Jan 23, 2013 at 10:30 AM, Adam Rice <[e-mail]> wrote:
> Hi,
>
> I would like to ask for clarification on section 4.1 item 2 of WebSocket RFC
> 6455. It reads (emphasis mine):
>
> 2. If the client already has a WebSocket connection to the remote host (IP
> address) identified by /host/ and port /port/ pair, even if the remote host
> is known by another name, the client MUST wait until that connection has
> been established or for that connection to have failed. There MUST be no
> more than one connection in a CONNECTING state. If multiple connections to
> the same IP address are attempted simultaneously, the client MUST serialize
> them so that there is no more than one connection at a time running through
> the following steps.

May I ask the reason for this requirement ?

It seems to me that a protocol should not limit in this way concurrent
connects to a host.
This look more like a recommendation for implementers, but not
something that should be mandated in a protocol.

For example, this would be sub-optimal for client WebSocket libraries
that can be used to perform load testing, or server-to-server
communication, etc.
Not all clients or use cases are browsers.

I'd like to propose to remove this requirement and changing it a
non-normative section as a suggestion for browser implementations.

Thanks !

--
Simone Bordet
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz