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

Redis Adapter #396

Open
Totodore opened this issue Nov 5, 2024 · 2 comments
Open

Redis Adapter #396

Totodore opened this issue Nov 5, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@Totodore
Copy link
Owner

Totodore commented Nov 5, 2024

This is a tracking issue for a redis adapter. Once the async adapter PR is merged (see #395) it will be possible to start working on a redis adapter. First thought are:
We must let the end user choose its Redis client implementation. There are currently multiple potential candidates:

The best way to implement that would be to make a simple compat trait for every redis feature the adapter use (mostly PUB/SUB AFAIK). We could then put each redis implementation behind a feature flag for the most used implementation and otherwise propose the user to implement manually the compat trait if he wants another Redis flavour.

@Totodore Totodore added the enhancement New feature or request label Nov 5, 2024
@Totodore Totodore self-assigned this Nov 5, 2024
@bossman1999
Copy link

When will it be updated? Waiting for this feature.

@Totodore
Copy link
Owner Author

I'm working on it on my spare time. I can't promise anything but it will be surely in 2025. (~3 to 10 months).

When will it be updated? Waiting for this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants