File	Date	Author	Commit
edoc	2010-03-28	Francesco Feltrinelli	[d8e504] comments on code
include	2010-03-28	Francesco Feltrinelli	[d8e504] comments on code
src	2010-03-28	Francesco Feltrinelli	[d8e504] comments on code
.gitignore	2010-03-26	Francesco Feltrinelli	[f482cb] modified edoc folder structure
Makefile	2010-03-26	Francesco Feltrinelli	[f482cb] modified edoc folder structure
README	2010-03-28	Francesco Feltrinelli	[fbb3db] added README file

Read Me

HOW TO COMPILE BINARIES AND EDOCS

1) Extract EPSI archive in an arbitrary directory.
2) Make sure you installed Erlang base-runtime and Edoc-builder in your system.
3) cd to EPSI top directory
4) "make"

Binaries are created in "ebin" folder, edocs in "edoc/edoc" folder.
To clean: "make clean".

HOW TO EXECUTE

1) cd to ebin folder
2) start erlang virtual machine
 2.1) if you want to test application locally, use "erl -sname <node_name>@localhost" and refer to nodes in function calls with "<node_name>@localhost"
 2.2) if you want to test with distributed machines, use "erl -name <node_name>@<IP_address> -setcookie <your_cookie>" and refer to nodes in function calls with "'<node_name>@<IP_address>'" (because of dot notation of IP address the node name atom requires single quotes)
 2.3) if you want to test with distributed machines but still use symbolic names, add corresponding lines to your hosts file (/etc/hosts in Unix systems):
   - "127.0.0.1 <my_host_name>" to refer to your machine
   - "<remote_IP_address> <remote_host_name>" to refer to another remote machine
  This way you can start virtual machines with "erl -sname <node_name>@<host_name> -setcookie <your_cookie>" and refer to nodes in function calls with "<node_name>@<host_name>"
3) From inside virtual machine consoles call EPSI functions; for example, start a broker with "epsi_broker:start()." or "epsi_broker:start(<parent_node>).", or start a subscriber with "epsi_client:subscribe().", or publish a message with "epsi_client:publish()."