On Mon, Apr 22, 2013 at 1:46 PM, Brandon Dimcheff <[email protected]>wrote:
> On Mon, Apr 22, 2013 at 12:40:46PM -0700, Bryan Talbot wrote: > > So it looks like there's no way to properly support socket.io currently > > with haproxy without hacking the client. I've been doing that (duplicate > > the token in the query string or header) during testing but don't want to > > do it generally since I'm not always in control of client code. > > We've just been doing source-ip based load balancing, which seems to > work fine for our socket.io stuff... Would that not work for you? > I think that would work for some cases, but there are a few common use cases for us when that won't work well: devices that change IP often (e.g., mobile), users behind proxies, load testing. There are probably others. Since mobile users tend to change IP address much more often than non-mobile clients, their sessions and websocket would get broken as well. Some of our users are being proxies which can change the user's external IP address more often as well and produces uneven load when there are many clients from a small number of IPs. Finally, for my immediate use case, is load testing using a smallish number of EC2 hosts where src based routing is just not effective but that's the easiest one to work around. -Bryan
