Skip to content
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update doc/contributing/maintaining-http.md
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
  • Loading branch information
mhdawson and aduh95 authored Feb 1, 2022
commit 62af82af444efdcfddeea69170caffbe684dfe31
15 changes: 8 additions & 7 deletions doc/contributing/maintaining-http.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down