You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 16, 2020. It is now read-only.
When a tower-h2 server receives a request that is canceled, the server needs to be able to stop doing work on behalf of the request. I believe that this has two implications:
When the response future has not yet been satisfied, the server should drop the response future.
When the response has been satisfied and its body is streaming, the server should drop both the response parts and body.
With this change middlewares like tower-buffer can ensure proper cancellation semantics without having to be protocol-aware.
The text was updated successfully, but these errors were encountered:
When a tower-h2 server receives a request that is canceled, the server needs to be able to stop doing work on behalf of the request. I believe that this has two implications:
With this change middlewares like tower-buffer can ensure proper cancellation semantics without having to be protocol-aware.
The text was updated successfully, but these errors were encountered: