title: Socket.IO RedisStore and xhr-polling
body: <p>I have a problem scaling my Node.js app on heroku.  I am using RedisStore to keep my socket connection persistent between node processes.  I am scaling to 2, 3 processes.  I followed this code here <a href="https://gist.github.com/1391583" rel="nofollow">https://gist.github.com/1391583</a>.  Everything works fine on one process, but when I scale out, broadcasts do not reach other nodes.  Connection info is persistent however,  and I do not get constant handshake errors and disconnects.</p>
  
  <p>My understanding is that socket.io RedisStore also handles the redis Pub/Sub internally to keep multiple processes in-sync.  As mentioned here <a href="https://groups.google.com/forum/?fromgroups&amp;hl=en#!topic/socket_io/gymBTlruYxs" rel="nofollow">https://groups.google.com/forum/?fromgroups&amp;hl=en#!topic/socket_io/gymBTlruYxs</a>  And by the way, I applied the #848 socket.io patch, it did not seem to fix the problem for me.</p>
  
  <p>As of May 14, 2012, Heroku supports only xhr-polling transport for socket.io, which is what I am using.  So is this problem with long polling only?  Is there a work-around for this?</p>
  
  <p>Thanks in advance.</p>