Lines Matching +full:all +full:- +full:apis

5 [technical priorities](https://github.com/nodejs/node/blob/HEAD/doc/contributing/technical-prioriti…
8 [Next-10](https://github.com/nodejs/next-10)
9 [mini-summit](https://github.com/nodejs/next-10/blob/main/meetings/summit-jan-2022.md)
14 The key elements of our strategy for future HTTP APIs are:
16 * APIs should be HTTP protocol independent (support HTTP1, HTTP2, etc.).
17 * APIs should be transport protocol independent (TCP, QUIC, etc.).
18 * APIs should provide good defaults that perform well.
19 * Client/server APIs should be consistent and allow easy integration.
20 * Common requirements like piping out from client API to server APIs should be
22 * For both the Client and Server there is a need for multiple APIs, with each
25 Unfortunately our existing HTTP APIs (
29 do not align with our high level strategy. While these APIs
32 Bug fixes however are still important for all of these APIs.
35 terms of priority within existing or new APIs is:
37 * HTTP 2 is in “maintenance mode” for both protocol and APIs.
38 * HTTP 1 is a stable protocol, but innovation is still possible with the APIs.
41 The current strategy is to build out 2 new client APIs and 2 new Server APIs
44 While transport-level APIs are important (e.g. socket level), the HTTP APIs
45 should not be tied to a specific transport-level API. Therefore,
46 transport-level APIs are out of the scope of our HTTP strategy/maintenance
49 ### Client APIs
51 For client APIs we want a high-level API and a low-level API when
52 more control is required. The current plan is for the following APIs:
54 * High-level API -
55   [Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API)
57 * Low-level API - a subset of the APIs exposed by
59   set of these APIs is still to be worked out. The current plan is to
60   pull undici into Node.js core without exposing its APIs in the Node.js
62   Fetch-based API. As this gets worked out we will discuss which
63   APIs to expose in the Node.js API surface.
65 ### Server APIs
67 For the server APIs we do not yet have a clear path, other than wanting
68 to align them with the APIs built for the client.
72 The low-level implementation of the
74 and [HTTPS](https://nodejs.org/docs/latest/api/https.html) APIs
81 The low-level implementation of
87 The low-level implementation is made available in the Node.js API through