We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is a warning to all users that we intend to revert back to Cohttp to Httpaf. The only reason for switching away from cohttp were:
Since both of these issues are being resolved (mirage/ocaml-cohttp#819, mirage/ocaml-cohttp#821) there's no longer any incentive to use httpaf.
The text was updated successfully, but these errors were encountered:
Pin opium at 0.18.0
af8a249
Pinning to the last CoHttp-based version 0.18.0, because 0.19.0 was a major rewrite to switch away from CoHttp[1], but there seem to be intentions to switch back to CoHttp[2]. We do not need to make this detour. [1]: https://github.com/rgrinberg/opium/blob/0.20.0/CHANGES.md#0190 [2]: rgrinberg/opium#279
No branches or pull requests
This is a warning to all users that we intend to revert back to Cohttp to Httpaf. The only reason for switching away from cohttp were:
Since both of these issues are being resolved (mirage/ocaml-cohttp#819, mirage/ocaml-cohttp#821) there's no longer any incentive to use httpaf.
The text was updated successfully, but these errors were encountered: