We have few node.js processes that should be able to pass messages,  What's the most efficient way doing that? How about using node_redis pub/sub  EDIT: the processes might run on different machines...

I'm looking at this code snippet:  var addSnippet = function( req, res ) {   getPostParams( req, function( obj ) {       var r = redis.createClient();        r.stream.on( 'connect', function() {         r.incr( 'nextid' , function...

I'm slowly digging in and learning redis in my spare time, and I am interested in the options available for creating a 'listener' for a website that subscribes to a channel, and updates a webpage as messages are received.   Now, from my o...

I have been using node and redis for some time. The problem I am experiencing is, when I use hgetall in redis, it returns an object.   { uid: '6203453597',     first_name: 'Name',     last_name: 'Surname',     gender: 'mal...

I was following Stephen Grinder tutorial where he started using Promisify.   For that he gave very vague explanation saying that redis needs a callback function and he finds that very untidy + redis does not support promises in NodeJS   And afterward...

I am working with node.js and using redis for caching some of the data on the server.  My code:  var client = redis.createClient(); client.on("error", function (err) {     console.log("Error " + err); });  client.flushall();  function...

For example,  function user(){     flow.exec(         function(){             call a;          },         function(){             call b;         }     ); }  function posts(){     flow.exec(         function(){             call a;          },...

Background  I am making a publish/subscribe typical application where a publisher sends messages to a consumer.   The publisher and the consumer are on different machines and the connection between them can break occasionally.   Objective  The goal h...

Is there a way to directly connect to Redis using client side (not Node.js) javascript?  I'm already using Node.js + PHP + Redis + Socket.io (for the client) successfully for a few projects. However, I really think this could be further simplifie...

I'm using setTimeout in Node.js and it seems to behave differently from client-side setTimeout in that it returns an object instead of a number. I want to store this in redis, but since redis only stores strings, I need to convert the object to a...