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.71 by root, Sun Aug 30 19:52:56 2009 UTC vs.
Revision 1.78 by root, Thu Sep 3 20:16:36 2009 UTC

4 4
5=head1 SYNOPSIS 5=head1 SYNOPSIS
6 6
7 use AnyEvent::MP; 7 use AnyEvent::MP;
8 8
9 $NODE # contains this node's noderef 9 $NODE # contains this node's node ID
10 NODE # returns this node's noderef 10 NODE # returns this node's node ID
11 NODE $port # returns the noderef of the port
12 11
13 $SELF # receiving/own port id in rcv callbacks 12 $SELF # receiving/own port id in rcv callbacks
14 13
15 # initialise the node so it can send/receive messages 14 # initialise the node so it can send/receive messages
16 initialise_node; 15 configure;
17 16
18 # ports are message endpoints 17 # ports are message destinations
19 18
20 # sending messages 19 # sending messages
21 snd $port, type => data...; 20 snd $port, type => data...;
22 snd $port, @msg; 21 snd $port, @msg;
23 snd @msg_with_first_element_being_a_port; 22 snd @msg_with_first_element_being_a_port;
24 23
25 # creating/using ports, the simple way 24 # creating/using ports, the simple way
26 my $simple_port = port { my @msg = @_; 0 }; 25 my $simple_port = port { my @msg = @_ };
27 26
28 # creating/using ports, tagged message matching 27 # creating/using ports, tagged message matching
29 my $port = port; 28 my $port = port;
30 rcv $port, ping => sub { snd $_[0], "pong"; 0 }; 29 rcv $port, ping => sub { snd $_[0], "pong" };
31 rcv $port, pong => sub { warn "pong received\n"; 0 }; 30 rcv $port, pong => sub { warn "pong received\n" };
32 31
33 # create a port on another node 32 # create a port on another node
34 my $port = spawn $node, $initfunc, @initdata; 33 my $port = spawn $node, $initfunc, @initdata;
35 34
36 # monitoring 35 # monitoring
40 39
41=head1 CURRENT STATUS 40=head1 CURRENT STATUS
42 41
43 bin/aemp - stable. 42 bin/aemp - stable.
44 AnyEvent::MP - stable API, should work. 43 AnyEvent::MP - stable API, should work.
45 AnyEvent::MP::Intro - uptodate, but incomplete. 44 AnyEvent::MP::Intro - explains most concepts.
46 AnyEvent::MP::Kernel - mostly stable. 45 AnyEvent::MP::Kernel - mostly stable.
47 AnyEvent::MP::Global - stable API, protocol not yet final. 46 AnyEvent::MP::Global - stable API, protocol not yet final.
48 47
49 stay tuned. 48 stay tuned.
50 49
55Despite its simplicity, you can securely message other processes running 54Despite its simplicity, you can securely message other processes running
56on the same or other hosts, and you can supervise entities remotely. 55on the same or other hosts, and you can supervise entities remotely.
57 56
58For an introduction to this module family, see the L<AnyEvent::MP::Intro> 57For an introduction to this module family, see the L<AnyEvent::MP::Intro>
59manual page and the examples under F<eg/>. 58manual page and the examples under F<eg/>.
60
61At the moment, this module family is a bit underdocumented.
62 59
63=head1 CONCEPTS 60=head1 CONCEPTS
64 61
65=over 4 62=over 4
66 63
138 135
139our $VERSION = $AnyEvent::MP::Kernel::VERSION; 136our $VERSION = $AnyEvent::MP::Kernel::VERSION;
140 137
141our @EXPORT = qw( 138our @EXPORT = qw(
142 NODE $NODE *SELF node_of after 139 NODE $NODE *SELF node_of after
143 initialise_node 140 configure
144 snd rcv mon mon_guard kil reg psub spawn 141 snd rcv mon mon_guard kil reg psub spawn
145 port 142 port
146); 143);
147 144
148our $SELF; 145our $SELF;
155 152
156=item $thisnode = NODE / $NODE 153=item $thisnode = NODE / $NODE
157 154
158The C<NODE> function returns, and the C<$NODE> variable contains, the node 155The C<NODE> function returns, and the C<$NODE> variable contains, the node
159ID of the node running in the current process. This value is initialised by 156ID of the node running in the current process. This value is initialised by
160a call to C<initialise_node>. 157a call to C<configure>.
161 158
162=item $nodeid = node_of $port 159=item $nodeid = node_of $port
163 160
164Extracts and returns the node ID from a port ID or a node ID. 161Extracts and returns the node ID from a port ID or a node ID.
165 162
166=item initialise_node $profile_name, key => value... 163=item configure $profile, key => value...
164
165=item configure key => value...
167 166
168Before a node can talk to other nodes on the network (i.e. enter 167Before a node can talk to other nodes on the network (i.e. enter
169"distributed mode") it has to initialise itself - the minimum a node needs 168"distributed mode") it has to configure itself - the minimum a node needs
170to know is its own name, and optionally it should know the addresses of 169to know is its own name, and optionally it should know the addresses of
171some other nodes in the network to discover other nodes. 170some other nodes in the network to discover other nodes.
172 171
173This function initialises a node - it must be called exactly once (or 172This function configures a node - it must be called exactly once (or
174never) before calling other AnyEvent::MP functions. 173never) before calling other AnyEvent::MP functions.
175 174
176The first argument is a profile name. If it is C<undef> or missing, then 175=over 4
177the current nodename will be used instead (i.e. F<uname -n>).
178 176
177=item step 1, gathering configuration from profiles
178
179The function first looks up the profile in the aemp configuration (see the 179The function first looks up a profile in the aemp configuration (see the
180L<aemp> commandline utility). the profile is calculated as follows: 180L<aemp> commandline utility). The profile name can be specified via the
181named C<profile> parameter or can simply be the first parameter). If it is
182missing, then the nodename (F<uname -n>) will be used as profile name.
181 183
184The profile data is then gathered as follows:
185
182First, all remaining key => value pairs (all of which are conviniently 186First, all remaining key => value pairs (all of which are conveniently
183undocumented at the moment) will be used. Then they will be overwritten by 187undocumented at the moment) will be interpreted as configuration
184any values specified in the global default configuration (see the F<aemp> 188data. Then they will be overwritten by any values specified in the global
185utility), then the chain of profiles selected, if any. That means that 189default configuration (see the F<aemp> utility), then the chain of
190profiles chosen by the profile name (and any C<parent> attributes).
191
186the values specified in the profile have highest priority and the values 192That means that the values specified in the profile have highest priority
187specified via C<initialise_node> have lowest priority. 193and the values specified directly via C<configure> have lowest priority,
194and can only be used to specify defaults.
188 195
189If the profile specifies a node ID, then this will become the node ID of 196If the profile specifies a node ID, then this will become the node ID of
190this process. If not, then the profile name will be used as node ID. The 197this process. If not, then the profile name will be used as node ID. The
191special node ID of C<anon/> will be replaced by a random node ID. 198special node ID of C<anon/> will be replaced by a random node ID.
199
200=item step 2, bind listener sockets
192 201
193The next step is to look up the binds in the profile, followed by binding 202The next step is to look up the binds in the profile, followed by binding
194aemp protocol listeners on all binds specified (it is possible and valid 203aemp protocol listeners on all binds specified (it is possible and valid
195to have no binds, meaning that the node cannot be contacted form the 204to have no binds, meaning that the node cannot be contacted form the
196outside. This means the node cannot talk to other nodes that also have no 205outside. This means the node cannot talk to other nodes that also have no
197binds, but it can still talk to all "normal" nodes). 206binds, but it can still talk to all "normal" nodes).
198 207
199If the profile does not specify a binds list, then a default of C<*> is 208If the profile does not specify a binds list, then a default of C<*> is
200used. 209used, meaning the node will bind on a dynamically-assigned port on every
210local IP address it finds.
201 211
212=item step 3, connect to seed nodes
213
202Lastly, the seeds list from the profile is passed to the 214As the last step, the seeds list from the profile is passed to the
203L<AnyEvent::MP::Global> module, which will then use it to keep 215L<AnyEvent::MP::Global> module, which will then use it to keep
204connectivity with at least on of those seed nodes at any point in time. 216connectivity with at least one node at any point in time.
205 217
206Example: become a distributed node listening on the guessed noderef, or 218=back
207the one specified via C<aemp> for the current node. This should be the 219
220Example: become a distributed node using the locla node name as profile.
208most common form of invocation for "daemon"-type nodes. 221This should be the most common form of invocation for "daemon"-type nodes.
209 222
210 initialise_node; 223 configure
211 224
212Example: become an anonymous node. This form is often used for commandline 225Example: become an anonymous node. This form is often used for commandline
213clients. 226clients.
214 227
215 initialise_node "anon/"; 228 configure nodeid => "anon/";
216 229
217Example: become a distributed node. If there is no profile of the given 230Example: configure a node using a profile called seed, which si suitable
218name, or no binds list was specified, resolve C<localhost:4044> and bind 231for a seed node as it binds on all local addresses on a fixed port (4040,
219on the resulting addresses. 232customary for aemp).
220 233
221 initialise_node "localhost:4044"; 234 # use the aemp commandline utility
235 # aemp profile seed nodeid anon/ binds '*:4040'
236
237 # then use it
238 configure profile => "seed";
239
240 # or simply use aemp from the shell again:
241 # aemp run profile seed
242
243 # or provide a nicer-to-remember nodeid
244 # aemp run profile seed nodeid "$(hostname)"
222 245
223=item $SELF 246=item $SELF
224 247
225Contains the current port id while executing C<rcv> callbacks or C<psub> 248Contains the current port id while executing C<rcv> callbacks or C<psub>
226blocks. 249blocks.
348 371
349=cut 372=cut
350 373
351sub rcv($@) { 374sub rcv($@) {
352 my $port = shift; 375 my $port = shift;
353 my ($noderef, $portid) = split /#/, $port, 2; 376 my ($nodeid, $portid) = split /#/, $port, 2;
354 377
355 $NODE{$noderef} == $NODE{""} 378 $NODE{$nodeid} == $NODE{""}
356 or Carp::croak "$port: rcv can only be called on local ports, caught"; 379 or Carp::croak "$port: rcv can only be called on local ports, caught";
357 380
358 while (@_) { 381 while (@_) {
359 if (ref $_[0]) { 382 if (ref $_[0]) {
360 if (my $self = $PORT_DATA{$portid}) { 383 if (my $self = $PORT_DATA{$portid}) {
468number of C<@reason> elements (no @reason means that the port was deleted 491number of C<@reason> elements (no @reason means that the port was deleted
469"normally"). Note also that I<< the callback B<must> never die >>, so use 492"normally"). Note also that I<< the callback B<must> never die >>, so use
470C<eval> if unsure. 493C<eval> if unsure.
471 494
472In the second form (another port given), the other port (C<$rcvport>) 495In the second form (another port given), the other port (C<$rcvport>)
473will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on 496will be C<kil>'ed with C<@reason>, if a @reason was specified, i.e. on
474"normal" kils nothing happens, while under all other conditions, the other 497"normal" kils nothing happens, while under all other conditions, the other
475port is killed with the same reason. 498port is killed with the same reason.
476 499
477The third form (kill self) is the same as the second form, except that 500The third form (kill self) is the same as the second form, except that
478C<$rvport> defaults to C<$SELF>. 501C<$rvport> defaults to C<$SELF>.
481C<snd>. 504C<snd>.
482 505
483As a rule of thumb, monitoring requests should always monitor a port from 506As a rule of thumb, monitoring requests should always monitor a port from
484a local port (or callback). The reason is that kill messages might get 507a local port (or callback). The reason is that kill messages might get
485lost, just like any other message. Another less obvious reason is that 508lost, just like any other message. Another less obvious reason is that
486even monitoring requests can get lost (for exmaple, when the connection 509even monitoring requests can get lost (for example, when the connection
487to the other node goes down permanently). When monitoring a port locally 510to the other node goes down permanently). When monitoring a port locally
488these problems do not exist. 511these problems do not exist.
489 512
490Example: call a given callback when C<$port> is killed. 513Example: call a given callback when C<$port> is killed.
491 514
500 mon $port, $self => "restart"; 523 mon $port, $self => "restart";
501 524
502=cut 525=cut
503 526
504sub mon { 527sub mon {
505 my ($noderef, $port) = split /#/, shift, 2; 528 my ($nodeid, $port) = split /#/, shift, 2;
506 529
507 my $node = $NODE{$noderef} || add_node $noderef; 530 my $node = $NODE{$nodeid} || add_node $nodeid;
508 531
509 my $cb = @_ ? shift : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,'; 532 my $cb = @_ ? shift : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,';
510 533
511 unless (ref $cb) { 534 unless (ref $cb) {
512 if (@_) { 535 if (@_) {
626 }; 649 };
627 _self_die if $@; 650 _self_die if $@;
628} 651}
629 652
630sub spawn(@) { 653sub spawn(@) {
631 my ($noderef, undef) = split /#/, shift, 2; 654 my ($nodeid, undef) = split /#/, shift, 2;
632 655
633 my $id = "$RUNIQ." . $ID++; 656 my $id = "$RUNIQ." . $ID++;
634 657
635 $_[0] =~ /::/ 658 $_[0] =~ /::/
636 or Carp::croak "spawn init function must be a fully-qualified name, caught"; 659 or Carp::croak "spawn init function must be a fully-qualified name, caught";
637 660
638 snd_to_func $noderef, "AnyEvent::MP::_spawn" => $id, @_; 661 snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;
639 662
640 "$noderef#$id" 663 "$nodeid#$id"
641} 664}
642 665
643=item after $timeout, @msg 666=item after $timeout, @msg
644 667
645=item after $timeout, $callback 668=item after $timeout, $callback
684 707
685=item * Node IDs are arbitrary strings in AEMP. 708=item * Node IDs are arbitrary strings in AEMP.
686 709
687Erlang relies on special naming and DNS to work everywhere in the same 710Erlang relies on special naming and DNS to work everywhere in the same
688way. AEMP relies on each node somehow knowing its own address(es) (e.g. by 711way. AEMP relies on each node somehow knowing its own address(es) (e.g. by
689configuraiton or DNS), but will otherwise discover other odes itself. 712configuration or DNS), but will otherwise discover other odes itself.
690 713
691=item * Erlang has a "remote ports are like local ports" philosophy, AEMP 714=item * Erlang has a "remote ports are like local ports" philosophy, AEMP
692uses "local ports are like remote ports". 715uses "local ports are like remote ports".
693 716
694The failure modes for local ports are quite different (runtime errors 717The failure modes for local ports are quite different (runtime errors
707 730
708Erlang uses processes that selectively receive messages, and therefore 731Erlang uses processes that selectively receive messages, and therefore
709needs a queue. AEMP is event based, queuing messages would serve no 732needs a queue. AEMP is event based, queuing messages would serve no
710useful purpose. For the same reason the pattern-matching abilities of 733useful purpose. For the same reason the pattern-matching abilities of
711AnyEvent::MP are more limited, as there is little need to be able to 734AnyEvent::MP are more limited, as there is little need to be able to
712filter messages without dequeing them. 735filter messages without dequeuing them.
713 736
714(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP). 737(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).
715 738
716=item * Erlang sends are synchronous, AEMP sends are asynchronous. 739=item * Erlang sends are synchronous, AEMP sends are asynchronous.
717 740

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines