Retrofit: How to setup a retrofit call to do automatic retries on a GET
For a GET operation, I want to be able to specify that retry it 3 times with a 500ms wait in between.
Is this already possible? If so, documentation will be quite helpful. Thanks.
inder123
All 7 comments
You'd probably do this through setting the HTTP client, I think OkHttp supports this. Also, ask things like this on StackOverflow, not as a bug on the project.
DSteve595
on 1 May 2015
Sure. I created the issue to add the documentation to the retrofit page at http://square.github.io/retrofit/, or to implement the feature if it is worth doing. Go ahead and close the issue if neither is a possibility.
inder123
on 1 May 2015
What you describe is an application-level policy that must be implemented by the application. Retrofit exists solely as a mechanism for creating requests from high-level Java objects, executing them on the underlying HTTP client, and marshaling the response back to high-level Java objects.
Policy like what you describe is vast and subjective. Thus, it's very hard to implement in any useful way with a reasonable API so we simply choose not to. This policy is much easier to implement at the application level because it doesn't need to be generalized and it can use additional information from the response to affect policy.
JakeWharton
on 3 May 2015
Or, as suggested, you could have an HTTP client transparently implement this. OkHttp's interceptors come to mind, but then such policy applies globally to every request made.
JakeWharton
on 3 May 2015
Ok, that makes sense. Thanks Jake and DSteve
inder123
on 3 May 2015
@JakeWharton is it possible to re-execute a pre-defined Observable?
https://stackoverflow.com/questions/47619115/how-to-retry-a-consumed-observable?
SamiKh94
on 3 Dec 2017
Subscribe to it again.
On Sun, Dec 3, 2017, 10:06 AM Sami Khleaf notifications@github.com wrote:
@JakeWharton https://github.com/jakewharton is it possible to
re-execute a pre-defined Observable?https://stackoverflow.com/questions/47619115/how-to-retry-a-consumed-observable
?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/square/retrofit/issues/828#issuecomment-348780550,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEEEduZDovU5csK22eIfbIeuj84OVUBks5s8rkDgaJpZM4EMvq8
.
JakeWharton
on 3 Dec 2017
Related issues
bhagyasri
·
3Comments
bolds07
·
3Comments
starktonys
·
3Comments
attaullahpro
·
3Comments
zheangrybear
·
3Comments
Most helpful comment
What you describe is an application-level policy that must be implemented by the application. Retrofit exists solely as a mechanism for creating requests from high-level Java objects, executing them on the underlying HTTP client, and marshaling the response back to high-level Java objects.
Policy like what you describe is vast and subjective. Thus, it's very hard to implement in any useful way with a reasonable API so we simply choose not to. This policy is much easier to implement at the application level because it doesn't need to be generalized and it can use additional information from the response to affect policy.