Documentation

ask in the console for the port number and initializes a node in the port specified It needs the application to be initialized with keep to get input from the user. the port can be entered in the command line with "program -p start/PORT"

A node is also a web server that send to the browser the program if it has been compiled to JavaScript with ghcjs. initNode also initializes the web nodes.

This sequence compiles to JScript and executes the program with a node in the port 8080

ghc program.hs
ghcjs program.hs -o static/out
./program -p start/myhost/8080

initNode, when the application has been loaded and executed in the browser, will perform a wormhole to his server node. So the application run within this wormhole.

Since the code is executed both in server node and browser node, to avoid confusion and in order to execute in a single logical thread, use onServer for code that you need to execute only in the server node, and onBrowser for code that you need in the browser, although server code could call the browser and vice-versa.

To invoke from browser to server and vice-versa, use atRemote.

To translate the code from the browser to the server node, use teleport.

ask for nodes to be added to the list of known nodes. it also ask to connect to the node to get his list of known nodes. It returns empty

executes the application in the server and the Web browser. the browser must point to http://hostname:port where port is the first parameter. It creates a wormhole to the server. The code of the program after simpleWebApp run in the browser unless teleport translates the execution to the server. To run something in the server and get the result back to the browser, use atRemote This last also works in the other side; If the application was teleported to the server, atRemote will execute his parameter in the browser.

It is necesary to compile the application with ghcjs:

ghcjs program.js
ghcjs program.hs -o static/out

./program

use this instead of smpleWebApp when you have to do some initializations in the server prior to the initialization of the web server

only executes the computaion if it is in the server, but the computation can call the browser. Otherwise return empty

only execute if the the program is executing in the browser. The code inside can contain calls to the server. Otherwise return empty (so it stop the computation and may execute alternative computations).

If the computation is running in the browser, translates i to the server and return back. If it is already in the server, just execute it

If the computation is running in the server, translates i to the browser and return back. If it is already in the browser, just execute it

run N nodes (N ports to listen) in the same program. For testing purposes. It add them to the list of known nodes, so it is possible to perform clustered operations with them.