-
Notifications
You must be signed in to change notification settings - Fork 535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add cancelation tokens to read/write blob APIs #5192
Comments
Related items (or sub-items to consider): |
This issue has been automatically marked as stale because it has had no activity for 180 days. It will be closed if no further activity occurs within 8 days of this comment. Thank you for your contributions to Fluid Framework! |
Closing old issues - we will eventually get to it! |
DeltaManager raises "throttled" warnings today when we hit 429 errors from server.
The way it's designed today is that all errors from all reads and writes (i.e. blobs, but also delta connection) are aggregated into single "warning" system. The problem is - this does not allow building proper user experiences.
For example, image upload/read want to display progress / errors in place, including 429 errors.
The way to address it is for all our read/write APIs to allow passing cancelation token and use it to both listen for cancelations from caller, but also report back progress to caller, including 429 status
Later on, this same technique has to be applied to all APIs that use blob APIs, i.e. including handle resolution and request handling.
The text was updated successfully, but these errors were encountered: