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

There's no cap on the number of HTTP fetches being run at a time #6

Open
ChillyCider opened this issue Oct 22, 2022 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@ChillyCider
Copy link
Owner

We need a way to coordinate between gunicorn/uWSGI/etc. workers to make sure only 1 fetch operation is ever being performed at a time.

Maybe we can leverage our SQLite cache?

Otherwise, we might have to resort to an external solution. (I'd prefer not to do this, because I like how this repo is a self-contained and complete WSGI app)

@ChillyCider ChillyCider added the bug Something isn't working label Oct 22, 2022
@ChillyCider ChillyCider self-assigned this Oct 22, 2022
@ChillyCider ChillyCider changed the title There's no cap on the number of HTTP fetches being run There's no cap on the number of HTTP fetches being run at a time Oct 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant