Skip to content

Feedbacks on core 'http2' module #3584

Closed

Description

@mcollina

Can one of you check out the experimental 'http2' module from core?
The docs are here: https://nodejs.org/api/http2.html.

If would be good to know if we have to change anything to better support the integration with Hapi.

We plan to make require('http2') available without a flag in Node 9, and move it out of experimental before Node 10.

cc @jasnell

Activity

  1. hueniverse commented on Sep 24, 2017

    @hueniverse
    Contributor

    Probably another week before I can get into it with v17 in full dev right now.

  2. self-assigned this
    on Sep 24, 2017
  3. mcollina commented on Sep 24, 2017

    @mcollina
    Author

    There is no hurry, just let us know here or open issues on nodejs/node.

  4. added
    supportQuestions, discussions, and general support
    and removed on Nov 14, 2017
  5. mnot commented on Nov 29, 2017

    @mnot

    Where's the best place to leave feedback / ask questions?

  6. mcollina commented on Nov 30, 2017

    @mcollina
    Author

    Here or in nodejs/node.

  7. hueniverse commented on Nov 30, 2017

    @hueniverse
    Contributor

    @mnot about the node http2 module in general or it's relation with hapi?

  8. mnot commented on Nov 30, 2017

    @mnot

    In general; I'll give it over there. Thanks.

  9. hueniverse commented on Aug 2, 2018

    @hueniverse
    Contributor

    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...

  10. chrisdavies commented on Jan 16, 2019

    @chrisdavies

    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.

  11. hueniverse commented on Jan 18, 2019

    @hueniverse
    Contributor

    @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.

  12. lock commented on Jan 9, 2020

    @lock

    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.

  13. locked as resolved and limited conversation to collaborators on Jan 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

supportQuestions, discussions, and general support

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions