Issue #296 has been updated by Vicente J. Ruiz Jurado.

Feature #296: Websocket configurable in a different port and/or subdomain

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).

That is, we would be able to split these two different traffics. This would allow the use of proxies, caches or CDNs for the "normal traffic".

https://issues.apache.org/jira/browse/WAVE-357


You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://redmine.ourproject.org/my/account