named-data.net

how best to use port 80 for both HTTP and Websocket ?

not sure, first pass:

https://code.google.com/p/pywebsocket/
http://arguments.callee.info/2010/04/20/running-apache-and-node-js-together/
https://github.com/nodejitsu/node-http-proxy
http://thatextramile.be/blog/2012/01/hosting-a-node-js-site-through-apache/

jeff B suggested this.

http://httpd.apache.org/docs/2.4/mod/mod_proxy_wstunnel.html

yet, does this negate need for nodejs ? how does the websocket get converted to ndn ?

This is completely separate from nodejs.

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.

No ndn-js code changes are needed, only changing the app port and installing/configuring the proxy.

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

however, yet to figure out the configuration.

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.

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.

This Feature can be abandoned because NFD 0.2.0 is deployed on testbed HUBs which has native support of WebSocket faces.