Re: [hybi] Multiplexing extension spec draft 03

[John Tamplin <[e-mail]>]

On Tue, Mar 27, 2012 at 12:16 PM, Takeshi Yoshino <[e-mail]>wrote:

> BTW, it looks like we need to clarify what to set to _Extensions In Use_.
>
> I can come up with two options
> - cut off mux token and everything after mux token that are applied to the
> physical channel
> - as-is
>
> IIRC, the motivation to expose the list of extensions in use to
> JavaScripts is to allow them to switch their behavior based on availability
> of optimization (compress, mux), e.g. fallback to HTTP when compression is
> not available. This can be done by server side too (We can reject the
> connection if mandatory extensions are not available to ask the client side
> to do something else. We also have close status 1010 to do this now), so
> not critical, but respecting the motivation, we should expose extensions in
> use "as-is".
>

hybi has no control over the JS API -- if you want to change the API
exposed to JS, that has to go through WHATWG.  This also doesn't seem
specific to any of the extensions we are discussing here, but rather a
general facility for exposing which extensions are in use.  AFAIK, there is
no standard API for the server side, so this would have to be done by each
implementation.

-- 
John A. Tamplin
Software Engineer (GWT), Google