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

Replace red-socket by RedisStore #3

Open
JeromeParadis opened this issue Jun 21, 2012 · 2 comments
Open

Replace red-socket by RedisStore #3

JeromeParadis opened this issue Jun 21, 2012 · 2 comments

Comments

@JeromeParadis
Copy link
Owner

If we use the socket.io RedisStore instead of red-socket module, we can have multiple threads using node.js cluster functionality and/or multiple node servers.

@roblinton
Copy link
Collaborator

Hey Jerome,

One thing to keep in mind here is that the name-spacing is handled by
red-socket right now so we'd have to either let go of namespacing or
re-implement it around the socket.io interface.

Cheers,

Rob

On 21 June 2012 18:24, Jerome Paradis
reply@reply.github.com
wrote:

If we use the socket.io RedisStore instead of red-socket module, we can have multiple threads using node.js cluster functionality and/or multiple node servers.


Reply to this email directly or view it on GitHub:
#3

@JeromeParadis
Copy link
Owner Author

Thanks for the reminder Rob.

I think the best approach to handle Redis prefixes would be to create a separate project for the NamespaceRedisClient code and then have live-notify monkey-path the redis client with this module if a prefix is supplied as an option. This way, it could be used for any project and would be optional to use in live-notify.

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

No branches or pull requests

2 participants