You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.
Activity
hueniverse commentedon Sep 24, 2017
Probably another week before I can get into it with v17 in full dev right now.
mcollina commentedon Sep 24, 2017
There is no hurry, just let us know here or open issues on nodejs/node.
mnot commentedon Nov 29, 2017
Where's the best place to leave feedback / ask questions?
mcollina commentedon Nov 30, 2017
Here or in nodejs/node.
hueniverse commentedon Nov 30, 2017
@mnot about the node http2 module in general or it's relation with hapi?
mnot commentedon Nov 30, 2017
In general; I'll give it over there. Thanks.
hueniverse commentedon Aug 2, 2018
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...
chrisdavies commentedon Jan 16, 2019
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.
hueniverse commentedon Jan 18, 2019
@chrisdavies feel free to ping me on the hapihour slack channel. I'd need more context to understand how you want to use http/2 with hapi.
lock commentedon Jan 9, 2020
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.