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

feat: Use HTTP statuses to backoff when needed #77

Open
chriswk opened this issue Jan 10, 2024 · 0 comments
Open

feat: Use HTTP statuses to backoff when needed #77

chriswk opened this issue Jan 10, 2024 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@chriswk
Copy link
Member

chriswk commented Jan 10, 2024

Describe the feature request

In order to reduce load on servers, as well as save our users some bandwidth, I'd like for this SDK to react to http status codes, and not just keep requesting at the same frequency if the server is telling it to chill out.

Background

Part of a cross-SDK initiative to make all our SDKs respect http statuses in order to save ourselves and our users for bandwidth/cpu usage that adds no value to either the server or the client.

Solution suggestions

Unleash/unleash-client-node#537 follows the correct pattern. Use 404, 429 or 50x statuses to reduce polling frequency. On 401 or 403 log and don't keep polling - your user probably needs to update their key before there's any point in continuing to hit the server.

@chriswk chriswk added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Jan 10, 2024
@sjaanus sjaanus moved this from New to Todo in Issues and PRs Jan 10, 2024
@ivarconr ivarconr moved this from Todo to For later in Issues and PRs May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
Status: For later
Development

No branches or pull requests

1 participant