-
Notifications
You must be signed in to change notification settings - Fork 959
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
Listen directly to Broker for messages #2500
Conversation
} | ||
else | ||
{ | ||
// more aggressive backoff [30, 60] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically we'll retry forever in case of retriable exceptions?
Nit: Regarding comment, It's less aggressive right? since we're increasing the retry intervals.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep I think so. This is copied behavior from the existing Message listener
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it could be read as "more aggressively backing off by increasing the time" 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could have some maximum of continuousError
where I abort if it reaches that
This PR adds 3 things:
/message
endpoint)We will set the
ServerUrlV2
in a followup PR.