From 88ecb965112a295a4c5e4af9bb8c0beb6f858e78 Mon Sep 17 00:00:00 2001 From: HoneyryderChuck Date: Sat, 9 Jan 2021 00:25:25 +0000 Subject: [PATCH] added note to last post --- www/_posts/2020-12-21-a-year-in-review.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/www/_posts/2020-12-21-a-year-in-review.md b/www/_posts/2020-12-21-a-year-in-review.md index afeee3d9..55b38aa8 100644 --- a/www/_posts/2020-12-21-a-year-in-review.md +++ b/www/_posts/2020-12-21-a-year-in-review.md @@ -73,6 +73,8 @@ Overall, I'd like to achieve two ambitious goals: reduce all dependencies not ma After a few initial bumps (including an issue that involved a report to the AWS Cloudfront team), H2spec compliance was achieved, so I can actually tell for a fact that `http-2-next` is the only complete implementation of the HTTP/2 protocol. These specs are run as part of the CI, so future changes don't break the status quo. +**EDIT**: It was brought to my attention that [protocol-http2](https://github.com/socketry/protocol-http2) also ships with an h2spec-compliant HTTP/2 parser. + ### Features Support for the `ORIGIN` frame was added. It was a bittersweet endeavour though, as, such as the `ALTSVC` frame before it, no known public server seems to use it yet, so it can't even be tested. Bummer.