Closed mscwilson closed 2 years ago
Looking forward to hearing what you come up with @matus-tomlein.
I consider this PR as a temporary fix to make the new retry mechanism slightly more sophisticated. I hope that Java tracker 0.13.0 would implement something better.
There's now no delay/backoff after a fatal response code, as it's not an error. It's not logged either (except at DEBUG level like for a successful send with 200 code). The Emitter just keeps sending requests.
For issue #316.
A simple implementation to allow users to choose not to retry when certain HTTP response codes are received. The events are dropped instead.