fix(api): streaming chunk upload for long running connections #3047
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
notanatol
approved these changes
Jun 27, 2022
aloknerurkar
force-pushed
the
streamupload.0
branch
from
342b24a
to
23f356d
Compare
mrekucci
approved these changes
Jun 28, 2022
There was a problem hiding this comment.
Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @acud)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the
/chunks/streamendpoint uses the HTTP request context which expires once the API returns. However, the websocket connection is expected to be alive for a longer time. This change allows clients to maintain long-running connections to upload a stream of chunks. The websocket connection is tracked using thewsWgin the api handler, so by passing a background context we allow the server read loop to be alive till the client closes the connection.This change is