Re: [hybi] Ticket#1 Http Compliance

[Greg Wilkins <[e-mail]>]

Roberto Peon wrote:

> On the handshake? Which features, specifically? 

The requirements can't really talk about handshakes or specific
features - because those are attributes of a particular solution.


> I'm asking because the
> two sentences here come in fundamental conflict.. It is HTTP/1.1, but
> not really.
> I'd expect something like:
> 
> On a connection established with the expectation that the primary or
> first protocol spoken is not WebSocket, the connection shall be
> considered that protocol and not WebSocket until a successful UPGRADE or
> similar change-of-protocol request is acknowledged. In the case of HTTP,
> WebSocket-only server implementations are required to implement the
> following subset of rfc2616, but are not required to implement any more
> than that.


The context for this requirement is set by a prior requirement:

  REQ. 6:  The WebSocket protocol MUST allow HTTP and WebSocket
           connections to be served from the same port.

the context is also further specified by the opening phrase
of the requirement:  "When sharing host and "well known" port with HTTP, .."

So this requirement only applies to websocket connections that
are established via shared HTTP port.   It does not prevent
there being other mechanisms for opening websocket connections
that do not use a shared HTTP port.

The requirement is trying to remove the doubt about when is
it HTTP and when it is not.    It says that when you are
working on a shared HTTP port, then the connection *is a*
HTTP connection up until both ends have agreed that it
has been upgraded.


regards