fd
commented
8 years ago Just some thoughts:
- HTTP2 detection should be transparent
- most browsers/http implementations already do this via ALPN
- servers can trivially implement this (again via ALPN)
- see https://godoc.org/golang.org/x/net/http2
- Server->Client data should be delivered via https://en.wikipedia.org/wiki/Server-sent_events
- (Clients that don't support SSE should start long-polling)
- Client->Server data should be delivered via POST requests (with the packets embeded in the form data as a base32 string).
- When http2 is supported these requests will be multiplexed over one http2 connection (along with the SSE stream)
- WebSockets are not very well supported and add allot of complexity. IMHO WebSockets should not be used.
Right now the HTTP transport is HTTP/1.x and socket.io based, update the spec to include detecting/using HTTP/2.
Also research detecting/using CoAP as a fallback?