Skip to content
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

Implement RSC15f (successful fallback host) #1115

Closed
ricardopereira opened this issue Apr 30, 2021 · 2 comments · Fixed by #1150
Closed

Implement RSC15f (successful fallback host) #1115

ricardopereira opened this issue Apr 30, 2021 · 2 comments · Fixed by #1150
Assignees

Comments

@ricardopereira
Copy link
Contributor

ricardopereira commented Apr 30, 2021

(RSC15f) Once/if a given fallback host succeeds, the client should store that successful fallback host for ClientOptions.fallbackRetryTimeout. Future HTTP requests during that period should use that host. If during this period a qualifying errors occurs on that host, or after fallbackRetryTimeout has expired, it should be un-stored, and the fallback sequence begun again from scratch, starting with the default primary host (rest.ably.io or ClientOptions#restHost) or, in the case of an existing fallback realtime connection as per (RTN17e), with the current fallback realtime host.

┆Issue is synchronized with this Jira Story by Unito

@maratal
Copy link
Collaborator

maratal commented Nov 26, 2021

@lukasz-szyszkowski Isn't the issue #815 is a duplicate of this one?

@lukasz-szyszkowski
Copy link
Contributor

Hmmm, it looks like a duplicate. #815 is three years old.

maratal pushed a commit that referenced this issue Jul 19, 2023
RTN7b: msgSerial only increases with messages expecting ACK/NACK
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants