-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
Request Retry #99
Comments
Please take a look at #98. It may be what you’re looking for. That pull request is open for user experimentation and feedback, so let me know what you think! |
Initial view of #98 having integrated it into our project looks spot on - will report back with any feedback. Additionally, this approach appears to have resolved a gap we were also facing with the token renewal / request retry cycle which you example clearly proposes a resolution for given the new changes. |
Merged #98. Closing this, but it’s new functionality in need of more eyes — so please send questions, bugs, and enhancement ideas early and often! |
Currently Siesta does not allow your to retry a request (created via load*() functions). You can only "retry" a standard Resource by calling load() or loadIfNeeded() which does not support RequestMethods other than GET, and loses all previously appended onSuccess / onFailure / onCompletion callbacks. If the developer wishes to retry a more complex request then they have to reconstruct from scratch.
A function to allow a previously failed request to be recreated (maintaining RequestMethod & callbacks) or to be retried entirely would be useful to avoid duplication of request generation code in POST / PUT / etc. scenarios. Without this it makes it difficult to create robust utility classes to handle negative conditions.
The text was updated successfully, but these errors were encountered: