> > The only problem there is the added delay. A client can't open a > websocket in the first flight. So I plan to allow the client to start an opening handshake without knowing that the HTTP/2 connection is capable of WS. If it is not capable of WS, the client may retry connecting with the native WS. To do so, the server must know the capability when the handshake request arrives. On Fri, Jul 18, 2014 at 1:29 AM, Martin Thomson <martin.thomson@gmail.com> wrote: > On 16 July 2014 23:24, Yutaka Hirano <yhirano@google.com> wrote: > > Then we need only client => server SETTINGS frame with WS_CPABABLE. > > Other way around: > > The client knows the server is WS capable when it receives a > WS_CAPABLE setting from the server. > The server knows the client is WS capable when it receives a WS request. > > The only problem there is the added delay. A client can't open a > websocket in the first flight. >
Received on Thursday, 17 July 2014 17:06:45 UTC