<html>
<head>
<style>
body {
font-family: Verdana, sans-serif;
font-size: 0.8em;
color:#484848;
}
h1, h2, h3 { font-family: "Trebuchet MS", Verdana, sans-serif; margin: 0px; }
h1 { font-size: 1.2em; }
h2, h3 { font-size: 1.1em; }
a, a:link, a:visited { color: #2A5685;}
a:hover, a:active { color: #c61a1a; }
a.wiki-anchor { display: none; }
hr {
width: 100%;
height: 1px;
background: #ccc;
border: 0;
}
.footer {
font-size: 0.8em;
font-style: italic;
}
</style>
</head>
<body>
<span class="header"></span>
Issue #296 has been updated by Vicente J. Ruiz Jurado.
<ul>
<li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li>
<li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li>
</ul>
<hr />
<h1><a href="http://redmine.ourproject.org/issues/296#change-381">Feature #296: Websocket configurable in a different port and/or subdomain </a></h1>
<ul>
<li>Author: Vicente J. Ruiz Jurado</li>
<li>Status: Closed</li>
<li>Priority: Normal</li>
<li>Assignee: </li>
<li>Category: WIAB Server</li>
<li>Target version: 0.2.0</li>
<li>Resolution: </li>
</ul>
<p>The idea is that the client uses two configurable listening addresses:</p>
<pre><code>• one for the normal traffic (all the common server petitions), the current http_frontend_public_address<br /> • and a new one for the websocket traffic (that can be configured to a different subdomain or port if it's necessary).</code></pre>
<p>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".</p>
<p><a class="external" href="https://issues.apache.org/jira/browse/WAVE-357">https://issues.apache.org/jira/browse/WAVE-357</a></p>
<hr />
<span class="footer"><p>You have received this notification because you have either subscribed to it, or are involved in it.<br />To change your notification preferences, please click here: <a class="external" href="http://redmine.ourproject.org/my/account">http://redmine.ourproject.org/my/account</a></p></span>
</body>
</html>