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.80 by root, Fri Sep 4 22:30:29 2009 UTC vs.
Revision 1.84 by root, Tue Sep 8 01:42:14 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 the 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.
111error), they try to re-establish connections to some seednodes again to
112join the network.
113 118
114Apart from being sued for seeding, seednodes are not special in any way - 119=item seeds - C<host:port>
115every public node can be a seednode. 120
121Seeds are transport endpoint(s) (usually a hostname/IP address and a
122TCP port) of nodes thta should be used as seed nodes.
123
124The nodes listening on those endpoints are expected to be long-running,
125and at least one of those should always be available. When nodes run out
126of connections (e.g. due to a network error), they try to re-establish
127connections to some seednodes again to join the network.
116 128
117=back 129=back
118 130
119=head1 VARIABLES/FUNCTIONS 131=head1 VARIABLES/FUNCTIONS
120 132
… …
621the package, then the package above the package and so on (e.g. 633the package, then the package above the package and so on (e.g.
622C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function 634C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
623exists or it runs out of package names. 635exists or it runs out of package names.
624 636
625The init function is then called with the newly-created port as context 637The init function is then called with the newly-created port as context
626object (C<$SELF>) and the C<@initdata> values as arguments. 638object (C<$SELF>) and the C<@initdata> values as arguments. It I<must>
639call one of the C<rcv> functions to set callbacks on C<$SELF>, otherwise
640the port might not get created.
627 641
628A common idiom is to pass a local port, immediately monitor the spawned 642A common idiom is to pass a local port, immediately monitor the spawned
629port, and in the remote init function, immediately monitor the passed 643port, and in the remote init function, immediately monitor the passed
630local port. This two-way monitoring ensures that both ports get cleaned up 644local port. This two-way monitoring ensures that both ports get cleaned up
631when there is a problem. 645when there is a problem.
… …
655 669
656sub _spawn { 670sub _spawn {
657 my $port = shift; 671 my $port = shift;
658 my $init = shift; 672 my $init = shift;
659 673
674 # rcv will create the actual port
660 local $SELF = "$NODE#$port"; 675 local $SELF = "$NODE#$port";
661 eval { 676 eval {
662 &{ load_func $init } 677 &{ load_func $init }
663 }; 678 };
664 _self_die if $@; 679 _self_die if $@;
… …
860L<AnyEvent::MP::Kernel> - more, lower-level, stuff. 875L<AnyEvent::MP::Kernel> - more, lower-level, stuff.
861 876
862L<AnyEvent::MP::Global> - network maintainance and port groups, to find 877L<AnyEvent::MP::Global> - network maintainance and port groups, to find
863your applications. 878your applications.
864 879
880L<AnyEvent::MP::LogCatcher> - simple service to display log messages from
881all nodes.
882
865L<AnyEvent>. 883L<AnyEvent>.
866 884
867=head1 AUTHOR 885=head1 AUTHOR
868 886
869 Marc Lehmann <schmorp@schmorp.de> 887 Marc Lehmann <schmorp@schmorp.de>

Diff Legend

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