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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: