-
-
Notifications
You must be signed in to change notification settings - Fork 278
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
Need a way to rewind responses for idempotent requests. #657
Comments
@maf23 I think this is what we want, but would love it if you could review and confirm, thanks! |
It looks good to me. |
Great, thanks!
…On Fri, Dec 15, 2017 at 12:38 AM, Martin Forssen ***@***.***> wrote:
It looks good to me.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#657 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAQKptlbl1UaZsZj1V8NVT3LRpOB2Zfks5tAhPVgaJpZM4Q87xa>
.
|
maf23
added a commit
to maf23/fog-xml
that referenced
this issue
Mar 6, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There needs to be a way to know when an idempotent request is restarted. Excon may already have returned some blocks of data before it encountered an error so the caller must be able to get notified that the request is restarted. Analogous to the rewind in the request block.
This is needed by fog: fog/fog-xml#13
The text was updated successfully, but these errors were encountered: