First release: priorities

Abierto
#48 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
c

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C
Estrellas
0
Forks
0
Merge medio
20 h 4 min
PR fusionados (30 d)
25

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de public/cursed-http

Todos los issues de public/cursed-http

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.