Re: [hybi] Multiplexing extension spec draft 03

[Takeshi Yoshino <[e-mail]>]

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".