Re: [hybi] #1: HTTP Compliance

[Scott Ferguson <[e-mail]>]

Ian Hickson wrote:
>
> On Tue, 18 May 2010, Greg Wilkins wrote:
>   
>> If the handshake is HTTP compliant, then the connection for a websocket 
>> handshake could be taken from the existing pool of idle connections to a 
>> host.  That would save the time needed to establish the connection.
>>     
>
> The resemblence to HTTP is nothing more than a hack to alolow us to share 
> ports in certain advanced scenarios. Most Web Socket servers will know 
> nothing about HTTP. Reusing connections is a level of complexity that is 
> completely unwarranted and that would only be useful in the rarest of 
> cases. It's a proposal that lies on completely the wrong side of the 80/20 
> line and would introduce _massive_ complexity for authors, who would have 
> no idea why their WebSocket servers were suddenly receiving random HTTP 
> requests and vice versa.

Huh? HTTP connection pooling isn't hard at all, certainly not 
"massively" complex, and would be invisible to the JavaScript 
programmers and WebSocket service writers. And pooling wouldn't dispatch 
random HTTP requests to the WebSocket resources.

TBH, this paragraph reads as if it was written by someone who doesn't 
understand how a HTTP client or server is written.

-- Scott