Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP/2 status #38

Open
wilzbach opened this issue Feb 18, 2017 · 2 comments
Open

HTTP/2 status #38

wilzbach opened this issue Feb 18, 2017 · 2 comments

Comments

@wilzbach
Copy link

Just out of interest: do I remember correctly that you plan to implement HTTP/2?

Do you have a public roadmap?

@ikod
Copy link
Owner

ikod commented Feb 20, 2017

Hello,
At the moment I have no answer re plans to implement http/2. And there are several questions:

  1. Not sure that http2 have any advantages over http/1 for non-browser applications, but I may be wrong.
  2. All http/2 implementations, which I can see, require event loop. So looks like I have to select event loop as first step.
  3. Should I reuse some library like nghttp2 or write it from scratch?

Re. public roadmap - there are some things that I would like to fix in current code: buffer management, API cleanup, and I'd like to implement command-line tool like "wget" using dlang-requests - it would be good use case, and good test for feature completeness.

@Domain
Copy link

Domain commented Nov 1, 2017

Apple use http2 to push message, so I want this feature too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants