Replies: 2 comments
-
|
Digging into this a bit more, I'll likely need to do some refactoring on Clock as well since the monotomic clock usage will present issues with a distributed approach. I'm still amenable to this if there's interest, though. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I think there are other packages out there that support using redis as a backend. This gem is intentionally simpler than those, so I dont' foresee us merging something like that into it. Please feel free to fork a new gem inspired by / based on this one though. Cheers |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Thanks for creating this project! The interface is intuitive, but I had a use case for it in mind that is better served with a Redis backend so RateQueue can share state across multiple processes or services.
I've hacked together an implementation based on the
redisgem. If there's interest, I can refactor it so RateQueue supports various backends for state management and open a PR.Beta Was this translation helpful? Give feedback.
All reactions