-
Notifications
You must be signed in to change notification settings - Fork 49
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 support #55
Comments
I do want to look into Alamofire Request adapters and retriers, but did not have time to do that unfortunately. You may actually be able to use them right now in current TRON release by specifying them directly on Alamofire SessionManager, that you pass into TRON. Take a look at Alamofire readme on how to do that - specifically retriers and adapters section: https://github.com/Alamofire/Alamofire#requestadapter I will leave this issue open for now, since we might be adopting those API's in TRON, deprecating HeaderBuildable protocols for example, since they are achieving the same thing. |
For now i have used below approach:
So basically i wanted to recreate request object and retry again. At the same time i wanted to put all these logic encapsulated. So i implemented few changes as below:
This implementation gives me few controls:
|
Hi! I've implemented support for per-request interceptors on master branch 0043c4e and will be releasing it in next 5.0 beta and of course in final release. |
Any roadmap to support request retry scenarios. e.g. retry the request with correct auth header.
The text was updated successfully, but these errors were encountered: