[kune-commits] [Kune - Feature #296] (Closed) Websocket configurable in a different port and/or subdomain

Redmine Comunes noreply at ourproject.org
Sun Aug 19 21:57:58 CEST 2012


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

Status changed from Resolved to Closed
% Done changed from 80 to 100

----------------------------------------
Feature #296: Websocket configurable in a different port and/or subdomain 
http://redmine.ourproject.org/issues/296#change-381

* Author: Vicente J. Ruiz Jurado
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: WIAB Server
* Target version: 0.2.0
* Resolution: 
----------------------------------------
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ourproject.org/pipermail/kune-commits/attachments/20120819/1661ed9d/attachment-0001.htm 


More information about the kune-commits mailing list