[WAVE-357] Websocket configurable in a different port and/or subdomain

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Assignee: Vicente J. Ruiz Jurado
• Reporter: Vicente J. Ruiz Jurado
• Created: 13/Jun/12 11:41
• Updated: 15/Oct/12 18:04
• Resolved: 15/Oct/12 18:04

Description

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

I'll attach a patch for review.