diff options
author | David Barksdale <amatus@amatus.name> | 2013-11-02 15:54:52 -0500 |
---|---|---|
committer | David Barksdale <amatus@amatus.name> | 2013-11-02 15:54:52 -0500 |
commit | 86239e453405df8ba0d6ad160041a1f63aa431a8 (patch) | |
tree | a5674896f3050a12260db3acb943b1d9159983bf /README.md | |
parent | 379a1b18657f87e430f2ceccb9417981bca217a8 (diff) |
Added gnunet.html page.
This loads gnunet-service-peerinfo.js but doesn't do much.
Also updated the README.
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -33,19 +33,19 @@ What You Can Do Now ### Compile GNUnet with emscripten ### 0. Install [emscripten] and add it to your `PATH`. 1. Execute `./build-gnunet.sh` -2. Load src/peerinfo/.libs/gnunet-service-peerinfo.html in a browser. +2. Execute `lein run` +3. Open http://localhost:3000/gnunet.html We're a long way from running GNUnet in the browser. Currently we have the -peerinfo service linked into an HTML file which displays error messages in a -text box. +peerinfo service linked into a javascript file which will load but has no +way of receiving commands. Eventually we will have each GNUnet service running in its own [Web Worker] -thread. The services normally communicate through UNIX sockets which we will -implement using [Web Messaging]. +thread. The APIs used by the services to schedule tasks and communicate with +each other is being implemented in javascript. [gnunet]: https://gnunet.org [webrtc]: http://www.webrtc.org [emscripten]: https://github.com/kripken/emscripten [rfc3264]: http://www.ietf.org/rfc/rfc3264.txt [web worker]: http://www.w3.org/TR/workers/ - [web messaging]: http://www.w3.org/TR/webmessaging/ |