From eeb43d81789fa4f50a9f74545dcd4cdd7ff443ad Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Mon, 31 Jan 2022 15:40:10 -0500 Subject: [PATCH 01/16] doc: add initial version of maintaining-http.md - document strategy based on Next-10 mini-summit - initial top level info on http API implementations Refs: https://github.com/nodejs/next-10/pull/114 Signed-off-by: Michael Dawson --- doc/contributing/maintaining-http.md | 98 ++++++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 doc/contributing/maintaining-http.md diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md new file mode 100644 index 00000000000000..acbda7c441701c --- /dev/null +++ b/doc/contributing/maintaining-http.md @@ -0,0 +1,98 @@ +# Maintaining HTTP + +Support for HTTP is a key priority in terms of ensuring the continued success of +Node.js as captured in the projects +[technical priorities](https://github.com/nodejs/node/blob/master/doc/contributing/technical-priorities.md). + +The current high level stragegy is based on the discussion in the +[Next-10](https://github.com/nodejs/next-10) + [mini-summit](https://github.com/nodejs/next-10/blob/main/meetings/summit-jan-2022.md) +on modern HTTP which was held on Jan 27 2022. + +## High level strategy + +The key elements of our strategy for future HTTP APIs are: + +* APIs should HTTP protocol independant (support HTTP1, HTTP2, etc.) +* APIs should be transport protocol independant (tcp, quick, etc.) +* APIs should provide good defaults the perform well +* Client/server APIs should be consistent and allow easy integration +* Common requirements like piping out from client API to server APIs should be easy +* For both the Client and Sever there is a need for multiple APIs, with each targeting + a different level of abstraction. + +Unfortunately our existing HTTP APIs: + +* [HTTP](https://nodejs.org/docs/latest/api/http.html) +* [HTTPS](https://nodejs.org/docs/latest/api/https.html) +* [HTTP2](https://nodejs.org/docs/latest/api/http2.html) + +do not align with the key elements. For this reason, while these APIs +are widely used and we do not plan to deprecate or remove them, +they are not the focus of active development or performance improvements. +Bug fixing is still important for all of these APIs. + +With respect to the HTTP protocols themselves our current assessment in +terms of priority within existing or new APIs is: +* HTTP 2 in “maintenance mode” both protocol and APIs +* HTTP 1 stable protocol, but innovation in APIs +* HTTP 3 is the future need to plan in support + +The current strategy is to build out 2 new client APIs and 2 new Server APIs +in line with the key elements above. + +While trasport level APIs are important (ex socket level), the HTTP APIs +should not be tied to a specific transport level API. Therefore, +transport level APIs are out of the scope of our HTTP strategy/maintaining +information. + +### Client APIs + +For client APIs we want a high level API and a lower level API when +more control is required. The current plan is for the following APIs: + +* High level api - + [Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) + based API buit on top of [undici](https://www.npmjs.com/package/undici). +* Lower Level API - a subset of the APIs exposed by + [undici](https://www.npmjs.com/package/undici). The exact shape and + set of these APIs is still to be worked out. The current plan is to + pull undici into Node.js core without exposing its APIs in the Node.js + API so that it can initially be used to support the higher level + Fetch based API. As this gets proved out we will discuss which + APIs to expose in the Node.js API surface. + +### Server APIs + +For the server APIs we do not yet have a clear path, other than wanting +to align them with the APIs built for the client. + +## Maintaining the HTTP APIs + +### HTTP, HTTPS + +The lower implementation of the +[HTTPS](https://nodejs.org/docs/latest/api/https.html) +and [HTTP2](https://nodejs.org/docs/latest/api/http2.html) APIs +are maintained in the [llttp](https://github.com/nodejs/llhttp) +repository. Updates are pulled into Node.js under +[deps/llhttp](https://github.com/nodejs/node/tree/master/deps/llhttp) + +The lower level implemention is surfaced in the Node.js API through +JavaScript code in the [lib](https://github.com/nodejs/node/tree/master/lib) +directory and C++ code in the +[src](https://github.com/nodejs/node/tree/master/src) directory. + +### HTTP2 + +The low level implementation of +[HTTP2](https://nodejs.org/docs/latest/api/http2.html) +is based on [nghttp2](https://nghttp2.org/). Updates are pulled into Node.js +under [deps/nghttp2](https://github.com/nodejs/node/tree/master/deps/nghttp2) +as needed. + +The lower level implemention is surfaced in the Node.js API through +JavaScript code in the [lib](https://github.com/nodejs/node/tree/master/lib) +directory and C++ code in the +[src](https://github.com/nodejs/node/tree/master/src) directory. + From 67e0cc507c5410790d837d3570d8f05eb2d502dc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C3=ABl=20Zasso?= Date: Tue, 1 Feb 2022 08:35:18 +0100 Subject: [PATCH 02/16] Apply suggestions from code review Co-authored-by: mscdex Co-authored-by: Mohammed Keyvanzadeh Co-authored-by: Mestery --- doc/contributing/maintaining-http.md | 60 ++++++++++++++-------------- 1 file changed, 30 insertions(+), 30 deletions(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index acbda7c441701c..cbe653d2b10a62 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -1,10 +1,10 @@ # Maintaining HTTP Support for HTTP is a key priority in terms of ensuring the continued success of -Node.js as captured in the projects +Node.js as captured in the project's [technical priorities](https://github.com/nodejs/node/blob/master/doc/contributing/technical-priorities.md). -The current high level stragegy is based on the discussion in the +The current high level strategy is based on the discussion in the [Next-10](https://github.com/nodejs/next-10) [mini-summit](https://github.com/nodejs/next-10/blob/main/meetings/summit-jan-2022.md) on modern HTTP which was held on Jan 27 2022. @@ -13,53 +13,53 @@ on modern HTTP which was held on Jan 27 2022. The key elements of our strategy for future HTTP APIs are: -* APIs should HTTP protocol independant (support HTTP1, HTTP2, etc.) -* APIs should be transport protocol independant (tcp, quick, etc.) -* APIs should provide good defaults the perform well +* APIs should be HTTP protocol independent (support HTTP1, HTTP2, etc.) +* APIs should be transport protocol independent (TCP, QUIC, etc.) +* APIs should provide good defaults that perform well * Client/server APIs should be consistent and allow easy integration * Common requirements like piping out from client API to server APIs should be easy -* For both the Client and Sever there is a need for multiple APIs, with each targeting +* For both the Client and Server there is a need for multiple APIs, with each targeting a different level of abstraction. Unfortunately our existing HTTP APIs: * [HTTP](https://nodejs.org/docs/latest/api/http.html) * [HTTPS](https://nodejs.org/docs/latest/api/https.html) -* [HTTP2](https://nodejs.org/docs/latest/api/http2.html) +* [HTTP2](https://nodejs.org/docs/latest/api/http2.html) -do not align with the key elements. For this reason, while these APIs +do not align with our high level strategy. While these APIs are widely used and we do not plan to deprecate or remove them, they are not the focus of active development or performance improvements. -Bug fixing is still important for all of these APIs. +Bug fixes however are still important for all of these APIs. -With respect to the HTTP protocols themselves our current assessment in +With respect to the HTTP protocols themselves, our current assessment in terms of priority within existing or new APIs is: -* HTTP 2 in “maintenance mode” both protocol and APIs -* HTTP 1 stable protocol, but innovation in APIs +* HTTP 2 is in “maintenance mode” for both protocol and APIs +* HTTP 1 is a stable protocol, but innovation is still possible with the APIs * HTTP 3 is the future need to plan in support The current strategy is to build out 2 new client APIs and 2 new Server APIs in line with the key elements above. -While trasport level APIs are important (ex socket level), the HTTP APIs -should not be tied to a specific transport level API. Therefore, -transport level APIs are out of the scope of our HTTP strategy/maintaining +While transport-level APIs are important (e.g. socket level), the HTTP APIs +should not be tied to a specific transport-level API. Therefore, +transport-level APIs are out of the scope of our HTTP strategy/maintenance information. ### Client APIs -For client APIs we want a high level API and a lower level API when +For client APIs we want a high-level API and a low-level API when more control is required. The current plan is for the following APIs: -* High level api - +* High-level API - [Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) - based API buit on top of [undici](https://www.npmjs.com/package/undici). -* Lower Level API - a subset of the APIs exposed by + based API built on top of [undici](https://www.npmjs.com/package/undici). +* Low-level API - a subset of the APIs exposed by [undici](https://www.npmjs.com/package/undici). The exact shape and - set of these APIs is still to be worked out. The current plan is to + set of these APIs is still to be worked out. The current plan is to pull undici into Node.js core without exposing its APIs in the Node.js API so that it can initially be used to support the higher level - Fetch based API. As this gets proved out we will discuss which + Fetch-based API. As this gets worked out we will discuss which APIs to expose in the Node.js API surface. ### Server APIs @@ -71,27 +71,27 @@ to align them with the APIs built for the client. ### HTTP, HTTPS -The lower implementation of the -[HTTPS](https://nodejs.org/docs/latest/api/https.html) -and [HTTP2](https://nodejs.org/docs/latest/api/http2.html) APIs -are maintained in the [llttp](https://github.com/nodejs/llhttp) -repository. Updates are pulled into Node.js under +The low-level implementation of the +[HTTP](https://nodejs.org/docs/latest/api/http.html) +and [HTTPS](https://nodejs.org/docs/latest/api/https.html) APIs +are maintained in the [llttp](https://github.com/nodejs/llhttp) +repository. Updates are pulled into Node.js under [deps/llhttp](https://github.com/nodejs/node/tree/master/deps/llhttp) -The lower level implemention is surfaced in the Node.js API through +The low-level implementation is made available in the Node.js API through JavaScript code in the [lib](https://github.com/nodejs/node/tree/master/lib) directory and C++ code in the [src](https://github.com/nodejs/node/tree/master/src) directory. ### HTTP2 -The low level implementation of -[HTTP2](https://nodejs.org/docs/latest/api/http2.html) +The low-level implementation of +[HTTP2](https://nodejs.org/docs/latest/api/http2.html) is based on [nghttp2](https://nghttp2.org/). Updates are pulled into Node.js under [deps/nghttp2](https://github.com/nodejs/node/tree/master/deps/nghttp2) as needed. -The lower level implemention is surfaced in the Node.js API through +The low-level implementation is made available in the Node.js API through JavaScript code in the [lib](https://github.com/nodejs/node/tree/master/lib) directory and C++ code in the [src](https://github.com/nodejs/node/tree/master/src) directory. From 62af82af444efdcfddeea69170caffbe684dfe31 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 1 Feb 2022 18:23:38 -0500 Subject: [PATCH 03/16] Update doc/contributing/maintaining-http.md Co-authored-by: Antoine du Hamel --- doc/contributing/maintaining-http.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index cbe653d2b10a62..5f33fe61062898 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -13,13 +13,14 @@ on modern HTTP which was held on Jan 27 2022. The key elements of our strategy for future HTTP APIs are: -* APIs should be HTTP protocol independent (support HTTP1, HTTP2, etc.) -* APIs should be transport protocol independent (TCP, QUIC, etc.) -* APIs should provide good defaults that perform well -* Client/server APIs should be consistent and allow easy integration -* Common requirements like piping out from client API to server APIs should be easy -* For both the Client and Server there is a need for multiple APIs, with each targeting - a different level of abstraction. +* APIs should be HTTP protocol independent (support HTTP1, HTTP2, etc.). +* APIs should be transport protocol independent (TCP, QUIC, etc.). +* APIs should provide good defaults that perform well. +* Client/server APIs should be consistent and allow easy integration. +* Common requirements like piping out from client API to server APIs should be + easy. +* For both the Client and Server there is a need for multiple APIs, with each + targeting a different level of abstraction. Unfortunately our existing HTTP APIs: From 5681930ae52311174846daa0c1db2bee2a4e9147 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 1 Feb 2022 18:23:48 -0500 Subject: [PATCH 04/16] Update doc/contributing/maintaining-http.md Co-authored-by: Antoine du Hamel --- doc/contributing/maintaining-http.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index 5f33fe61062898..a8d596b9b9db0e 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -22,12 +22,10 @@ The key elements of our strategy for future HTTP APIs are: * For both the Client and Server there is a need for multiple APIs, with each targeting a different level of abstraction. -Unfortunately our existing HTTP APIs: - -* [HTTP](https://nodejs.org/docs/latest/api/http.html) -* [HTTPS](https://nodejs.org/docs/latest/api/https.html) -* [HTTP2](https://nodejs.org/docs/latest/api/http2.html) - +Unfortunately our existing HTTP APIs ( +[HTTP](https://nodejs.org/docs/latest/api/http.html), +[HTTPS](https://nodejs.org/docs/latest/api/https.html), and +[HTTP2](https://nodejs.org/docs/latest/api/http2.html)) do not align with our high level strategy. While these APIs are widely used and we do not plan to deprecate or remove them, they are not the focus of active development or performance improvements. From 9b057a4e142972a84eca24dd40d9fe7a92a5be91 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 1 Feb 2022 18:23:59 -0500 Subject: [PATCH 05/16] Update doc/contributing/maintaining-http.md Co-authored-by: Antoine du Hamel --- doc/contributing/maintaining-http.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index a8d596b9b9db0e..898e4327110df0 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -33,9 +33,10 @@ Bug fixes however are still important for all of these APIs. With respect to the HTTP protocols themselves, our current assessment in terms of priority within existing or new APIs is: -* HTTP 2 is in “maintenance mode” for both protocol and APIs -* HTTP 1 is a stable protocol, but innovation is still possible with the APIs -* HTTP 3 is the future need to plan in support + +* HTTP 2 is in “maintenance mode” for both protocol and APIs. +* HTTP 1 is a stable protocol, but innovation is still possible with the APIs. +* HTTP 3 is the future need to plan in support. The current strategy is to build out 2 new client APIs and 2 new Server APIs in line with the key elements above. From 723da3af0b49409babc59f784a827630c7bf0b79 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 1 Feb 2022 18:24:05 -0500 Subject: [PATCH 06/16] Update doc/contributing/maintaining-http.md Co-authored-by: Darshan Sen --- doc/contributing/maintaining-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index 898e4327110df0..a0331fec9d1291 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -2,7 +2,7 @@ Support for HTTP is a key priority in terms of ensuring the continued success of Node.js as captured in the project's -[technical priorities](https://github.com/nodejs/node/blob/master/doc/contributing/technical-priorities.md). +[technical priorities](https://github.com/nodejs/node/blob/HEAD/doc/contributing/technical-priorities.md). The current high level strategy is based on the discussion in the [Next-10](https://github.com/nodejs/next-10) From a93d4a2770ba6b6431267ed426dd129a59eb0986 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 1 Feb 2022 18:24:11 -0500 Subject: [PATCH 07/16] Update doc/contributing/maintaining-http.md Co-authored-by: Darshan Sen --- doc/contributing/maintaining-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index a0331fec9d1291..5f610213083bfa 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -79,7 +79,7 @@ repository. Updates are pulled into Node.js under [deps/llhttp](https://github.com/nodejs/node/tree/master/deps/llhttp) The low-level implementation is made available in the Node.js API through -JavaScript code in the [lib](https://github.com/nodejs/node/tree/master/lib) +JavaScript code in the [lib](https://github.com/nodejs/node/tree/HEAD/lib) directory and C++ code in the [src](https://github.com/nodejs/node/tree/master/src) directory. From 95b6dc26c0e91062432b1cc2ff9cc305647afa5b Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 1 Feb 2022 18:24:16 -0500 Subject: [PATCH 08/16] Update doc/contributing/maintaining-http.md Co-authored-by: Darshan Sen --- doc/contributing/maintaining-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index 5f610213083bfa..1df01757341191 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -88,7 +88,7 @@ directory and C++ code in the The low-level implementation of [HTTP2](https://nodejs.org/docs/latest/api/http2.html) is based on [nghttp2](https://nghttp2.org/). Updates are pulled into Node.js -under [deps/nghttp2](https://github.com/nodejs/node/tree/master/deps/nghttp2) +under [deps/nghttp2](https://github.com/nodejs/node/tree/HEAD/deps/nghttp2) as needed. The low-level implementation is made available in the Node.js API through From 933af049b5b9d4b46dea4d48b5cb9f517e2f5fc5 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 1 Feb 2022 18:24:22 -0500 Subject: [PATCH 09/16] Update doc/contributing/maintaining-http.md Co-authored-by: Darshan Sen --- doc/contributing/maintaining-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index 1df01757341191..b3499c4db65965 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -94,5 +94,5 @@ as needed. The low-level implementation is made available in the Node.js API through JavaScript code in the [lib](https://github.com/nodejs/node/tree/master/lib) directory and C++ code in the -[src](https://github.com/nodejs/node/tree/master/src) directory. +[src](https://github.com/nodejs/node/tree/HEAD/src) directory. From 3974bdeab40d1be9c18012a1997cad9d80b019ef Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 1 Feb 2022 18:24:29 -0500 Subject: [PATCH 10/16] Update doc/contributing/maintaining-http.md Co-authored-by: Darshan Sen --- doc/contributing/maintaining-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index b3499c4db65965..2a3b27f64a1a56 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -92,7 +92,7 @@ under [deps/nghttp2](https://github.com/nodejs/node/tree/HEAD/deps/nghttp2) as needed. The low-level implementation is made available in the Node.js API through -JavaScript code in the [lib](https://github.com/nodejs/node/tree/master/lib) +JavaScript code in the [lib](https://github.com/nodejs/node/tree/HEAD/lib) directory and C++ code in the [src](https://github.com/nodejs/node/tree/HEAD/src) directory. From 90137ff6d5715895e0e1836907a9f600517908ef Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 1 Feb 2022 18:24:34 -0500 Subject: [PATCH 11/16] Update doc/contributing/maintaining-http.md Co-authored-by: Darshan Sen --- doc/contributing/maintaining-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index 2a3b27f64a1a56..53dcd6640117b2 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -81,7 +81,7 @@ repository. Updates are pulled into Node.js under The low-level implementation is made available in the Node.js API through JavaScript code in the [lib](https://github.com/nodejs/node/tree/HEAD/lib) directory and C++ code in the -[src](https://github.com/nodejs/node/tree/master/src) directory. +[src](https://github.com/nodejs/node/tree/HEAD/src) directory. ### HTTP2 From 50235c873e64b278eebd20c94a5de3a9c1354513 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 1 Feb 2022 18:24:42 -0500 Subject: [PATCH 12/16] Update doc/contributing/maintaining-http.md Co-authored-by: Darshan Sen --- doc/contributing/maintaining-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index 53dcd6640117b2..0182e8e5a764dd 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -76,7 +76,7 @@ The low-level implementation of the and [HTTPS](https://nodejs.org/docs/latest/api/https.html) APIs are maintained in the [llttp](https://github.com/nodejs/llhttp) repository. Updates are pulled into Node.js under -[deps/llhttp](https://github.com/nodejs/node/tree/master/deps/llhttp) +[deps/llhttp](https://github.com/nodejs/node/tree/HEAD/deps/llhttp) The low-level implementation is made available in the Node.js API through JavaScript code in the [lib](https://github.com/nodejs/node/tree/HEAD/lib) From 3fd1dbcbc9c2bee40e2e330ec7fd4c972d18bd0b Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Wed, 2 Feb 2022 12:53:02 -0500 Subject: [PATCH 13/16] Update doc/contributing/maintaining-http.md --- doc/contributing/maintaining-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index 0182e8e5a764dd..4ffb1c6f0ad50c 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -39,7 +39,7 @@ terms of priority within existing or new APIs is: * HTTP 3 is the future need to plan in support. The current strategy is to build out 2 new client APIs and 2 new Server APIs -in line with the key elements above. +in line with the high level strategy above. While transport-level APIs are important (e.g. socket level), the HTTP APIs should not be tied to a specific transport-level API. Therefore, From 5a1cbcff00d11ef3dd6ba4d6b30ae0016d1d87d2 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Wed, 2 Feb 2022 12:53:36 -0500 Subject: [PATCH 14/16] Update doc/contributing/maintaining-http.md --- doc/contributing/maintaining-http.md | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index 4ffb1c6f0ad50c..843e2b8799100b 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -95,4 +95,3 @@ The low-level implementation is made available in the Node.js API through JavaScript code in the [lib](https://github.com/nodejs/node/tree/HEAD/lib) directory and C++ code in the [src](https://github.com/nodejs/node/tree/HEAD/src) directory. - From 277995b6710aa78d4430a4106ad74946e3134bca Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Wed, 2 Feb 2022 16:11:08 -0500 Subject: [PATCH 15/16] squash: address linter complaint Signed-off-by: Michael Dawson --- doc/contributing/maintaining-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index 843e2b8799100b..045783557b82e6 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -6,7 +6,7 @@ Node.js as captured in the project's The current high level strategy is based on the discussion in the [Next-10](https://github.com/nodejs/next-10) - [mini-summit](https://github.com/nodejs/next-10/blob/main/meetings/summit-jan-2022.md) +[mini-summit](https://github.com/nodejs/next-10/blob/main/meetings/summit-jan-2022.md) on modern HTTP which was held on Jan 27 2022. ## High level strategy From 42823a14316d450c3dc67e400c8fda20b47385a2 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Wed, 2 Feb 2022 16:15:21 -0500 Subject: [PATCH 16/16] Update doc/contributing/maintaining-http.md --- doc/contributing/maintaining-http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing/maintaining-http.md b/doc/contributing/maintaining-http.md index 045783557b82e6..0737b2f9880d66 100644 --- a/doc/contributing/maintaining-http.md +++ b/doc/contributing/maintaining-http.md @@ -36,7 +36,7 @@ terms of priority within existing or new APIs is: * HTTP 2 is in “maintenance mode” for both protocol and APIs. * HTTP 1 is a stable protocol, but innovation is still possible with the APIs. -* HTTP 3 is the future need to plan in support. +* HTTP 3 is an important protocol and we need to add support for it. The current strategy is to build out 2 new client APIs and 2 new Server APIs in line with the high level strategy above.