You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 13, 2023. It is now read-only.
Implement an adapter wrapper that, given a collection of AdapterSpec objects will route each API request in a round-robin fashion.
If a connection failure occurs (e.g., timeout or connection refused) or if the client receives a 5xx response (e.g., 500 or 503), then the wrapper should automatically try to switch to the next one. If every connection fails, then raise an exception. Note that this does not apply when the client receives a 4xx response (this indicates a problem with the request, not the node).
Bonus points if you can make it thread-safe, but it's not a requirement. To be honest, I'm not even sure if "thread-safe round-robin" even makes sense 😸
The text was updated successfully, but these errors were encountered:
Implement an adapter wrapper that, given a collection of
AdapterSpec
objects will route each API request in a round-robin fashion.If a connection failure occurs (e.g., timeout or connection refused) or if the client receives a 5xx response (e.g., 500 or 503), then the wrapper should automatically try to switch to the next one. If every connection fails, then raise an exception. Note that this does not apply when the client receives a 4xx response (this indicates a problem with the request, not the node).
Bonus points if you can make it thread-safe, but it's not a requirement. To be honest, I'm not even sure if "thread-safe round-robin" even makes sense 😸
The text was updated successfully, but these errors were encountered: