Re: [hybi] Extensibility mechanisms?

[Greg Wilkins <[e-mail]>]

Ian Hickson wrote:

> Why would a large scale deployments with complex infrastructure that can't 
> handle BEEP framing opt-in to an experimental non-standard feature that 
> uses BEEP framing?

because experiments are a precursor to real deployments.

> 
>> If you want to send BEEP over a HTTP connection, then you should upgrade 
>> to BEEP, not websocket.
> 
> If the handshake involves an optional opt-in to a non-standard 
> experimental feature, and you accept it, then you're not upgrading to Web 
> Socket, you're upgrading to a non-standard protocol influenced by Web 
> Sockets, as defined by the convention you and the client are using.

My point is that an intermediary can't possible know about
all subprotocols (experimental or otherwise), nor be expected
to upgrade everytime a new subprotocol is invented.

Intermediaries can know about websocket framing and so long as
all sub protocols and extensions are restricted to adhere to
websocket framing, then intermediaries can continue to work
regardless of sub protocols.

regards