https://redmine.named-data.net/https://redmine.named-data.net/favicon.ico?14759811232013-09-27T10:47:11ZNDN project issue tracking systemnamed-data.net - Feature #1042: NDN-WS Proxy for Appshttps://redmine.named-data.net/issues/1042?journal_id=432013-09-27T10:47:11ZAlexander Hornalexnano@ucla.edu
<ul></ul><p>how best to use port 80 for both HTTP and Websocket ? </p>
<p>not sure, first pass:</p>
<p><a href="https://code.google.com/p/pywebsocket/">https://code.google.com/p/pywebsocket/</a><br>
<a href="http://arguments.callee.info/2010/04/20/running-apache-and-node-js-together/">http://arguments.callee.info/2010/04/20/running-apache-and-node-js-together/</a><br>
<a href="https://github.com/nodejitsu/node-http-proxy">https://github.com/nodejitsu/node-http-proxy</a><br>
<a href="http://thatextramile.be/blog/2012/01/hosting-a-node-js-site-through-apache/">http://thatextramile.be/blog/2012/01/hosting-a-node-js-site-through-apache/</a></p>
named-data.net - Feature #1042: NDN-WS Proxy for Appshttps://redmine.named-data.net/issues/1042?journal_id=442013-09-27T11:02:02ZAlexander Hornalexnano@ucla.edu
<ul></ul><p>jeff B suggested this. </p>
<p><a href="http://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html">http://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html</a></p>
<p>yet, does this negate need for nodejs ? how does the websocket get converted to ndn ? </p>
named-data.net - Feature #1042: NDN-WS Proxy for Appshttps://redmine.named-data.net/issues/1042?journal_id=452013-09-28T10:00:43ZJeff Burkejaburke@gmail.com
<ul></ul><p>This is completely separate from nodejs.</p>
<p>The idea is to simply proxy websocket transport through port 80 on named-data.net (this is a typical envisioned use for websockets), so that apps deployed on named-data.net/apps/live can use port 80 for ndn traffic and work anywhere the website can be accessed. </p>
<p>No ndn-js code changes are needed, only changing the app port and installing/configuring the proxy. </p>
named-data.net - Feature #1042: NDN-WS Proxy for Appshttps://redmine.named-data.net/issues/1042?journal_id=472013-10-01T18:22:40ZAlexander Hornalexnano@ucla.edu
<ul></ul><p>well THAT was fun. as it's not part of normal distribution yet. i had to check out apache from source, apply a patch, sacrifice a few oxen, and voila have mod_wsproxy enabled on </p>
<p>however, yet to figure out the configuration. </p>
<p>it seems possible to run both on the same domain, yet it seems to demand an 'absolute path' for the proxy - http:/// or ws://... neither of which is perhaps giving the 'clean' / header-less content that ccnd is likely expecting. </p>
<p>i'll play with this more, but at the moment it still seems to me like there is a step missing / that we need to run node proxy, so we can convert websocket to ccnd face. </p>
named-data.net - Feature #1042: NDN-WS Proxy for Appshttps://redmine.named-data.net/issues/1042?journal_id=48142014-09-09T14:55:19ZJunxiao Shi
<ul></ul><p>This Feature can be abandoned because NFD 0.2.0 is deployed on testbed HUBs which has native support of WebSocket faces.</p>
named-data.net - Feature #1042: NDN-WS Proxy for Appshttps://redmine.named-data.net/issues/1042?journal_id=66852014-12-11T08:49:17ZAlexander Hornalexnano@ucla.edu
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Abandoned</i></li></ul>