ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent-MP/MP.pm
(Generate patch)

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.82 by root, Mon Sep 7 18:42:09 2009 UTC vs.
Revision 1.86 by root, Wed Sep 9 01:47:01 2009 UTC

… …
83 83
84Nodes are either public (have one or more listening ports) or private 84Nodes are either public (have one or more listening ports) or private
85(no listening ports). Private nodes cannot talk to other private nodes 85(no listening ports). Private nodes cannot talk to other private nodes
86currently. 86currently.
87 87
88=item node ID - C<[a-za-Z0-9_\-.:]+> 88=item node ID - C<[A-Z_][a-zA-Z0-9_\-.:]*>
89 89
90A node ID is a string that uniquely identifies the node within a 90A node ID is a string that uniquely identifies the node within a
91network. Depending on the configuration used, node IDs can look like a 91network. Depending on the configuration used, node IDs can look like a
92hostname, a hostname and a port, or a random string. AnyEvent::MP itself 92hostname, a hostname and a port, or a random string. AnyEvent::MP itself
93doesn't interpret node IDs in any way. 93doesn't interpret node IDs in any way.
… …
97Nodes can only talk to each other by creating some kind of connection to 97Nodes can only talk to each other by creating some kind of connection to
98each other. To do this, nodes should listen on one or more local transport 98each other. To do this, nodes should listen on one or more local transport
99endpoints - binds. Currently, only standard C<ip:port> specifications can 99endpoints - binds. Currently, only standard C<ip:port> specifications can
100be used, which specify TCP ports to listen on. 100be used, which specify TCP ports to listen on.
101 101
102=item seeds - C<host:port> 102=item seed nodes
103 103
104When a node starts, it knows nothing about the network. To teach the node 104When a node starts, it knows nothing about the network. To teach the node
105about the network it first has to contact some other node within the 105about the network it first has to contact some other node within the
106network. This node is called a seed. 106network. This node is called a seed.
107 107
108Seeds are transport endpoint(s) of as many nodes as one wants. Those nodes 108Apart from the fact that other nodes know them as seed nodes and they have
109to have fixed listening addresses, seed nodes are perfectly normal nodes -
110any node can function as a seed node for others.
111
112In addition to discovering the network, seed nodes are also used to
113maintain the network and to connect nodes that otherwise would have
114trouble connecting. They form the backbone of an AnyEvent::MP network.
115
109are expected to be long-running, and at least one of those should always 116Seed nodes are expected to be long-running, and at least one seed node
110be available. When nodes run out of connections (e.g. due to a network 117should always be available. They should also be relatively responsive - a
111error), they try to re-establish connections to some seednodes again to 118seed node that blocks for long periods will slow down everybody else.
112join the network.
113 119
114Apart from being sued for seeding, seednodes are not special in any way - 120=item seeds - C<host:port>
115every public node can be a seednode. 121
122Seeds are transport endpoint(s) (usually a hostname/IP address and a
123TCP port) of nodes thta should be used as seed nodes.
124
125The nodes listening on those endpoints are expected to be long-running,
126and at least one of those should always be available. When nodes run out
127of connections (e.g. due to a network error), they try to re-establish
128connections to some seednodes again to join the network.
116 129
117=back 130=back
118 131
119=head1 VARIABLES/FUNCTIONS 132=head1 VARIABLES/FUNCTIONS
120 133

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines