| … | |
… | |
| 93 | |
93 | |
| 94 | Nodes are either public (have one or more listening ports) or private |
94 | Nodes are either public (have one or more listening ports) or private |
| 95 | (no listening ports). Private nodes cannot talk to other private nodes |
95 | (no listening ports). Private nodes cannot talk to other private nodes |
| 96 | currently. |
96 | currently. |
| 97 | |
97 | |
| 98 | =item node ID - C<[A-Z_][a-zA-Z0-9_\-.:]*> |
98 | =item node ID - C<[A-Za-z0-9_\-.:]*> |
| 99 | |
99 | |
| 100 | A node ID is a string that uniquely identifies the node within a |
100 | A node ID is a string that uniquely identifies the node within a |
| 101 | network. Depending on the configuration used, node IDs can look like a |
101 | network. Depending on the configuration used, node IDs can look like a |
| 102 | hostname, a hostname and a port, or a random string. AnyEvent::MP itself |
102 | hostname, a hostname and a port, or a random string. AnyEvent::MP itself |
| 103 | doesn't interpret node IDs in any way. |
103 | doesn't interpret node IDs in any way. |
| … | |
… | |
| 882 | |
882 | |
| 883 | Erlang implements few guarantees on messages delivery - messages can get |
883 | Erlang implements few guarantees on messages delivery - messages can get |
| 884 | lost without any of the processes realising it (i.e. you send messages a, |
884 | lost without any of the processes realising it (i.e. you send messages a, |
| 885 | b, and c, and the other side only receives messages a and c). |
885 | b, and c, and the other side only receives messages a and c). |
| 886 | |
886 | |
| 887 | AEMP guarantees correct ordering, and the guarantee that after one message |
887 | AEMP guarantees (modulo hardware errors) correct ordering, and the |
| 888 | is lost, all following ones sent to the same port are lost as well, until |
888 | guarantee that after one message is lost, all following ones sent to the |
| 889 | monitoring raises an error, so there are no silent "holes" in the message |
889 | same port are lost as well, until monitoring raises an error, so there are |
| 890 | sequence. |
890 | no silent "holes" in the message sequence. |
| 891 | |
891 | |
| 892 | =item * Erlang can send messages to the wrong port, AEMP does not. |
892 | =item * Erlang can send messages to the wrong port, AEMP does not. |
| 893 | |
893 | |
| 894 | In Erlang it is quite likely that a node that restarts reuses a process ID |
894 | In Erlang it is quite likely that a node that restarts reuses a process ID |
| 895 | known to other nodes for a completely different process, causing messages |
895 | known to other nodes for a completely different process, causing messages |
| … | |
… | |
| 953 | |
953 | |
| 954 | Strings can easily be printed, easily serialised etc. and need no special |
954 | Strings can easily be printed, easily serialised etc. and need no special |
| 955 | procedures to be "valid". |
955 | procedures to be "valid". |
| 956 | |
956 | |
| 957 | And as a result, a port with just a default receiver consists of a single |
957 | And as a result, a port with just a default receiver consists of a single |
| 958 | closure stored in a global hash - it can't become much cheaper. |
958 | code reference stored in a global hash - it can't become much cheaper. |
| 959 | |
959 | |
| 960 | =item Why favour JSON, why not a real serialising format such as Storable? |
960 | =item Why favour JSON, why not a real serialising format such as Storable? |
| 961 | |
961 | |
| 962 | In fact, any AnyEvent::MP node will happily accept Storable as framing |
962 | In fact, any AnyEvent::MP node will happily accept Storable as framing |
| 963 | format, but currently there is no way to make a node use Storable by |
963 | format, but currently there is no way to make a node use Storable by |
