SP over HTTP/2 transport

[gdamore]

as an alternative to websocket, we could transport over HTTP/2. Its unclear if this will actually provide a benefit over websocket, but here's some example:

golang/go#13444

Note that this would only work with Go 1.6 or newer, where HTTP/2 is available.

[gdamore]

Reading this, I see only small benefits for HTTP/2, since we would almost immediately switch to WebSocket. We cannot use HTTP/2 server push for generic protocol uses, and server send events (SSE) look complex with little benefit.

More promising in the long term is QUIC. Sadly there doesn't seem to be usable QUIC code for Go yet. At least not code I'd feel good about integrating directly into mangos.

I'm going to close this issue for now; the question of HTTP/2 is orthogonal to websocket, and we'll use HTTP/2 to establish the websocket connection automatically when the go 1.6 HTTP framework discovers it makes sense to do so.