Client libraries to generate fallback hosts from custom environment #818
Assignees
Labels
content-request
A request for new content, as opposed to changing/fixing existing content
Comments
QuintinWillison
added
content-request
mattheworiordan
added a commit
to ably/ably-ruby
that referenced
this issue
Feb 21, 2020
When environment is set in the client SDKs, we can now rely on default fallback hosts as follows. Fallbacks are ENV-[a-e]-fallback.ably-realtime.com. For example: ENV-a-fallback.ably-realtime.com ENV-b-fallback.ably-realtime.com ENV-c-fallback.ably-realtime.com ENV-d-fallback.ably-realtime.com ENV-e-fallback.ably-realtime.com Note that this change: - It breaks a lot of tests against sandbox that assumed no fallback hosts would be used - We need to ensure that custom hosts or custom ports result do not use default environment fallback hosts. We should only use when only the custom environment is set - Some spec updates are needed in the spec relating to the use of fallback hosts See related issue ably/docs#818 (no spec yet exists)
mattheworiordan
changed the title
TheSmartnik
pushed a commit
to ably/ably-ruby
that referenced
this issue
Nov 30, 2020
When environment is set in the client SDKs, we can now rely on default fallback hosts as follows. Fallbacks are ENV-[a-e]-fallback.ably-realtime.com. For example: ENV-a-fallback.ably-realtime.com ENV-b-fallback.ably-realtime.com ENV-c-fallback.ably-realtime.com ENV-d-fallback.ably-realtime.com ENV-e-fallback.ably-realtime.com Note that this change: - It breaks a lot of tests against sandbox that assumed no fallback hosts would be used - We need to ensure that custom hosts or custom ports result do not use default environment fallback hosts. We should only use when only the custom environment is set - Some spec updates are needed in the spec relating to the use of fallback hosts See related issue ably/docs#818 (no spec yet exists)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This enhancement will automatically use fallback hosts, deterministically derived from the supplied
environment, when they've not been specified explicitly.It will solve the problem whereby customers ship their app built against our client library, seeing that it works with basic testing, but don't realise that it will quickly stop working when things go wrong with the primary host.
See the internal issue which proposes this enhancement.
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: