First release: priorities

Aperta
#48 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
c

Direzione di ricerca

This is a roadmap, not a single task, so there is no file or test named here. Read the P0 items first (#32 QUIC Retry, #33 Version Negotiation, #36 pacing), each as its own linked issue, to see what each one needs. Work on this issue is done when the first release is cut with the P0 and P1 items complete; the P2 items are out of scope for a first newcomer contribution.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

The order to work through for a first release of the HTTP/1.1, HTTP/2 and HTTP/3 clients and servers. Correctness against real servers and networks comes first, then latency and efficiency, then new protocol features.

P0: release blockers

  1. #32 QUIC client handling of Retry. Without it, servers that validate addresses (common under load and behind CDNs) can't be reached at all.
  2. #33 Version Negotiation on the client. Today the handshake times out instead of failing at once.
  3. #36 Pacing. Sending a whole congestion window in one burst causes avoidable loss on real paths. A library others ship should behave well on the network by default.

P1: in the first release

  1. #35 TLS + ALPN for the HTTP/2 client example, tested against real servers. Real-world HTTP/2 is all TLS.
  2. #44 Stateless reset detection. It's small, and makes server restarts fail fast.
  3. #43 Connection ID rotation. At minimum, honouring the peer's NEW_CONNECTION_ID / retire_prior_to (the spec requires it). Full migration can come later.
  4. #34 0-RTT and session resumption. The largest latency win.
  5. #39 Blocked streams in our QPACK decoder. Browsers' first request bursts to our server get compressed.
  6. #37 Path MTU discovery. About 15% fewer packets on bulk transfers.
  7. #40 Extensible priorities. Lets pages load in a sensible order.

P2: later
#38 ECN, #41 extended CONNECT (WebSockets), #42 DATAGRAM and HTTP datagrams, #47 BBR, #45 h2c Upgrade, #46 accepting server push.

Lingua principale
C
Stelle
0
Fork
0
Merge medio
20h 4m
PR unite (30g)
25

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di public/cursed-http

Tutte le issue di public/cursed-http

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.