Load balancing is outside the scope of node-http-proxy. Configuration of load balancing algorithms is complex and least common denominator often leads to problems with things that use in memory storage across connections such as non-database sessions etc. There are multiple examples on npm and github of load balancers using node-http-proxy, but I doubt it will ever support configuration only load balancing.
For socket.io in particular I would recommend using source to destination IP hashing, so that the same client always reaches a consistent server per proxy, but even that is only a few lines of code inside of your proxy. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
