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

Compatibility with http2 >= 3 #79

Open
akshaymankar opened this issue Jun 19, 2021 · 1 comment
Open

Compatibility with http2 >= 3 #79

akshaymankar opened this issue Jun 19, 2021 · 1 comment

Comments

@akshaymankar
Copy link

http2-3.0.0 introduced a module named Network.HTT2.Client, which implements some of the same features as this library. Given http2 is a dependency of this library, I think it makes sense to re-orient some of the features provided here to align with the way the http2 library has implemented them and get rid of the module name collision. Maybe it might also make sense to find the differences and upstream them into http2 and mark this library as deprecated.

@ProofOfKeags
Copy link
Collaborator

While this is ideal. The client code in http2 has a very different API than in this library as best I can tell. I would love to get there, but the documentation around the http2 client code is fairly thin, and the types are something I haven't wrapped my head around yet. It looks like the "client" in http2 is CPS encoded to accept various transport functions.

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

2 participants