Skip to content

Question about http-next version strategy #113

Open
@fed135

Description

@fed135

I've been working on ideas for the lib API design of http-next and getting inspiration from the strategy document and this old gist.

One question that popped was: does http-next need to handle all versions of http as part of the same core api module, or should it expose versions independently and let the community build modules custom tailored for specific handling/downgrading of http sessions?

Ex:

const {http, http2, http3} = require('node:http-next');

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussTopics for open discussion

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions