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