What HTTP/2 features make it desirable for general RPC (no browser involved)?
In the past I've found HTTP (1.1) to be okay, but not great for server->server RPC. The semantics are fine (but overkill) and the overhead sort of sucks. With HTTP/2 I guess the performance should be a lot better (with a binary protocol); I'm still unsure about the HTTP semantics in a general RPC context. Anyone with deeper knowledge of HTTP/2 care to enlighten me?
(Following up on a twitter conversation I had with @bradfitz: https://twitter.com/calebspare/status/571049339541270529)