I don't see an HTTP2 native support happening in the near future as there are no clear use cases driving this. I know some people are using hapi with the new HTTP2 server but I don't really have enough experience to provide feedback. I hope this will change but I don't really want to build HTTP2 features without some kind of business driver...
Hi @hueniverse I work on the Elastic Kibana team (but I don't claim to speak for them).
We've currently got a feature that uses websockets mostly because Hapi doesn't have http2 support. Basically, we've got a feature (Canvas) that allows our end-users to build fancy, custom scripted UIs. The scripting language generally needs to communicate with the server. So, if they build a UI with loads of little components, each with a custom script, it gets really chatty. This isn't ideal over HTTP/1, but HTTP/2 or websockets mitigates the problem.
I'd personally prefer to use HTTP/2 for this, as I think it would mean simpler code for us. Happy to discuss in more detail, if you're interested.