Hi, The idea is that the client uses two configurable listening addresses: - one for the normal traffic (all the common server petitions), the current http_frontend_public_address - and a new one for the websocket traffic (that can be configured to a different subdomain or port if it's necessary).
The goal is to separate these two different traffics. This will allow the use of proxies, caches, or a CDN for the normal traffic. Making some fast tests, seems that websockets works ok using a different port or subdomain in recent versions of chrome and firefox, but I didn't start to do a serious patch. Any experience with something similar? My proposal is to add a new parameter in the configuration if we think that this is reasonable. BR, -- Vicente J. Ruiz Jurado http://comunes.org http://ourproject.org http://homes.ourproject.org/~vjrj/blog (@vjrj) "There's no way you're going to get a quote from us to use on your book cover" [Metropolitan Police Spokesperson, Banksy, Wall and Piece back cover, Random House, 2005]
