Support Client initiated Cancellation Propagation
- Langage dominant
- Rust
- Étoiles
- 24.8k
- Forks
- 1.9k
- Merge moyen
- 23 h 10 min
- PR mergées (30 j)
- 26
Description
Linking to the discussion, which contains the meat of the issue.
https://github.com/actix/actix-web/discussions/3011
Likewise, I'm aware of the difficult nature of this ask given the statelessness of the http protocol...
I believe Go handles this by polling the connection status internally and watching for CLOSE so that these events are propagated up.
Given actix-web positions itself as a higher level abstraction, we should also be able to have these events propagated up or that the very least the green-thread/connection needs to be exposed such that user can poll themselves.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Read the linked discussion #3011 first, since the issue says it contains the substantive requirements. Identify the relevant Actix Web request or connection entry points from that discussion and define done as client disconnect or cancellation being propagated upward, or the connection being exposed for polling; the payload names no files or tests.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- rust
- Domaine
- api, backend, networking
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100