This repository was archived by the owner on Feb 25, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 84
Labels
Comments
I think prior to this we should run through connect and rip out any redis-specific code and work it into modinha-redis. |
@vsimonian yes, we'd have to. Although in doing that, we'd make modinha-redis specific to this application. I think that's probably an acceptable tradeoff since it's very unlikely that that particular lib is in use anywhere else. |
|
Re: my last comment, it looks like the name doesn't refer to io.js in particular, and ioredis supports node.js as well. Sounds like a go to me. |
I think this might be a good weekend hack. |
👍 |
This was referenced Aug 23, 2015
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Even as we're looking to roll our own embedded distributed backend and move away from Redis, users are asking for high-availability Redis support.
Recently someone reached out by email to ask about porting to ioredis, in order to support sentinel. Looks like it could be fairly straightforward to switch redis clients. Anyone interested to work on this?
The text was updated successfully, but these errors were encountered: