-
Notifications
You must be signed in to change notification settings - Fork 3
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
HttpWebRequest retry strategy #5
Comments
@moberacker You mean based on the 429 HTTP Status Code? It can be done, I'll have to see if I can do it in the coming weeks. |
@ealsur no I mean if the internet connection dies for a couple of seconds, and then comes back...the code will throw an exception, with a status like ReceiveFailure, ConnectFailure, KeepAliveFailure etc. it's quite important that if the internet connection comes back, the HttpDataCollectorAPI should be able to continue communicating with the server... |
@moberacker Sounds good, I'll research the possible codes to catch just those and see if I can apply an exponential back off. |
ok thanks |
Hi, is it possible to implement some HttpWebRequest retry strategy in your Collector?
The text was updated successfully, but these errors were encountered: