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.24 by root, Tue Aug 4 20:00:00 2009 UTC vs.
Revision 1.41 by root, Sat Aug 8 21:56:29 2009 UTC

8 8
9 $NODE # contains this node's noderef 9 $NODE # contains this node's noderef
10 NODE # returns this node's noderef 10 NODE # returns this node's noderef
11 NODE $port # returns the noderef of the port 11 NODE $port # returns the noderef of the port
12 12
13 $SELF # receiving/own port id in rcv callbacks
14
15 # ports are message endpoints
16
17 # sending messages
13 snd $port, type => data...; 18 snd $port, type => data...;
19 snd $port, @msg;
20 snd @msg_with_first_element_being_a_port;
14 21
15 $SELF # receiving/own port id in rcv callbacks 22 # miniports
23 my $miniport = port { my @msg = @_; 0 };
16 24
25 # full ports
26 my $port = port;
17 rcv $port, smartmatch => $cb->($port, @msg); 27 rcv $port, smartmatch => $cb->(@msg);
18
19 # examples:
20 rcv $port2, ping => sub { snd $_[0], "pong"; 0 }; 28 rcv $port, ping => sub { snd $_[0], "pong"; 0 };
21 rcv $port1, pong => sub { warn "pong received\n" }; 29 rcv $port, pong => sub { warn "pong received\n"; 0 };
22 snd $port2, ping => $port1; 30
31 # remote ports
32 my $port = spawn $node, $initfunc, @initdata;
23 33
24 # more, smarter, matches (_any_ is exported by this module) 34 # more, smarter, matches (_any_ is exported by this module)
25 rcv $port, [child_died => $pid] => sub { ... 35 rcv $port, [child_died => $pid] => sub { ...
26 rcv $port, [_any_, _any_, 3] => sub { .. $_[2] is 3 36 rcv $port, [_any_, _any_, 3] => sub { .. $_[2] is 3
27 37
38 # monitoring
39 mon $port, $cb->(@msg) # callback is invoked on death
40 mon $port, $otherport # kill otherport on abnormal death
41 mon $port, $otherport, @msg # send message on death
42
28=head1 DESCRIPTION 43=head1 DESCRIPTION
29 44
30This module (-family) implements a simple message passing framework. 45This module (-family) implements a simple message passing framework.
31 46
32Despite its simplicity, you can securely message other processes running 47Despite its simplicity, you can securely message other processes running
43 58
44=over 4 59=over 4
45 60
46=item port 61=item port
47 62
48A port is something you can send messages to with the C<snd> function, and 63A port is something you can send messages to (with the C<snd> function).
49you can register C<rcv> handlers with. All C<rcv> handlers will receive 64
50messages they match, messages will not be queued. 65Some ports allow you to register C<rcv> handlers that can match specific
66messages. All C<rcv> handlers will receive messages they match, messages
67will not be queued.
51 68
52=item port id - C<noderef#portname> 69=item port id - C<noderef#portname>
53 70
54A port id is always the noderef, a hash-mark (C<#>) as separator, followed 71A port id is normaly the concatenation of a noderef, a hash-mark (C<#>) as
55by a port name (a printable string of unspecified format). 72separator, and a port name (a printable string of unspecified format). An
73exception is the the node port, whose ID is identical to its node
74reference.
56 75
57=item node 76=item node
58 77
59A node is a single process containing at least one port - the node 78A node is a single process containing at least one port - the node
60port. You can send messages to node ports to let them create new ports, 79port. You can send messages to node ports to find existing ports or to
61among other things. 80create new ports, among other things.
62 81
63Initially, nodes are either private (single-process only) or hidden 82Nodes are either private (single-process only), slaves (connected to a
64(connected to a master node only). Only when they epxlicitly "become 83master node only) or public nodes (connectable from unrelated nodes).
65public" can you send them messages from unrelated other nodes.
66 84
67=item noderef - C<host:port,host:port...>, C<id@noderef>, C<id> 85=item noderef - C<host:port,host:port...>, C<id@noderef>, C<id>
68 86
69A noderef is a string that either uniquely identifies a given node (for 87A node reference is a string that either simply identifies the node (for
70private and hidden nodes), or contains a recipe on how to reach a given 88private and slave nodes), or contains a recipe on how to reach a given
71node (for public nodes). 89node (for public nodes).
72 90
91This recipe is simply a comma-separated list of C<address:port> pairs (for
92TCP/IP, other protocols might look different).
93
94Node references come in two flavours: resolved (containing only numerical
95addresses) or unresolved (where hostnames are used instead of addresses).
96
97Before using an unresolved node reference in a message you first have to
98resolve it.
99
73=back 100=back
74 101
75=head1 VARIABLES/FUNCTIONS 102=head1 VARIABLES/FUNCTIONS
76 103
77=over 4 104=over 4
88 115
89use AE (); 116use AE ();
90 117
91use base "Exporter"; 118use base "Exporter";
92 119
93our $VERSION = '0.02'; 120our $VERSION = '0.1';
94our @EXPORT = qw( 121our @EXPORT = qw(
95 NODE $NODE *SELF node_of _any_ 122 NODE $NODE *SELF node_of _any_
96 become_slave become_public 123 resolve_node initialise_node
97 snd rcv mon kil reg psub 124 snd rcv mon kil reg psub spawn
98 port 125 port
99); 126);
100 127
101our $SELF; 128our $SELF;
102 129
111The C<NODE> function returns, and the C<$NODE> variable contains 138The C<NODE> function returns, and the C<$NODE> variable contains
112the noderef of the local node. The value is initialised by a call 139the noderef of the local node. The value is initialised by a call
113to C<become_public> or C<become_slave>, after which all local port 140to C<become_public> or C<become_slave>, after which all local port
114identifiers become invalid. 141identifiers become invalid.
115 142
116=item $noderef = node_of $portid 143=item $noderef = node_of $port
117 144
118Extracts and returns the noderef from a portid or a noderef. 145Extracts and returns the noderef from a portid or a noderef.
146
147=item initialise_node $noderef, $seednode, $seednode...
148
149=item initialise_node "slave/", $master, $master...
150
151Before a node can talk to other nodes on the network it has to initialise
152itself - the minimum a node needs to know is it's own name, and optionally
153it should know the noderefs of some other nodes in the network.
154
155This function initialises a node - it must be called exactly once (or
156never) before calling other AnyEvent::MP functions.
157
158All arguments are noderefs, which can be either resolved or unresolved.
159
160There are two types of networked nodes, public nodes and slave nodes:
161
162=over 4
163
164=item public nodes
165
166For public nodes, C<$noderef> must either be a (possibly unresolved)
167noderef, in which case it will be resolved, or C<undef> (or missing), in
168which case the noderef will be guessed.
169
170Afterwards, the node will bind itself on all endpoints and try to connect
171to all additional C<$seednodes> that are specified. Seednodes are optional
172and can be used to quickly bootstrap the node into an existing network.
173
174=item slave nodes
175
176When the C<$noderef> is the special string C<slave/>, then the node will
177become a slave node. Slave nodes cannot be contacted from outside and will
178route most of their traffic to the master node that they attach to.
179
180At least one additional noderef is required: The node will try to connect
181to all of them and will become a slave attached to the first node it can
182successfully connect to.
183
184=back
185
186This function will block until all nodes have been resolved and, for slave
187nodes, until it has successfully established a connection to a master
188server.
189
190Example: become a public node listening on the default node.
191
192 initialise_node;
193
194Example: become a public node, and try to contact some well-known master
195servers to become part of the network.
196
197 initialise_node undef, "master1", "master2";
198
199Example: become a public node listening on port C<4041>.
200
201 initialise_node 4041;
202
203Example: become a public node, only visible on localhost port 4044.
204
205 initialise_node "locahost:4044";
206
207Example: become a slave node to any of the specified master servers.
208
209 initialise_node "slave/", "master1", "192.168.13.17", "mp.example.net";
210
211=item $cv = resolve_node $noderef
212
213Takes an unresolved node reference that may contain hostnames and
214abbreviated IDs, resolves all of them and returns a resolved node
215reference.
216
217In addition to C<address:port> pairs allowed in resolved noderefs, the
218following forms are supported:
219
220=over 4
221
222=item the empty string
223
224An empty-string component gets resolved as if the default port (4040) was
225specified.
226
227=item naked port numbers (e.g. C<1234>)
228
229These are resolved by prepending the local nodename and a colon, to be
230further resolved.
231
232=item hostnames (e.g. C<localhost:1234>, C<localhost>)
233
234These are resolved by using AnyEvent::DNS to resolve them, optionally
235looking up SRV records for the C<aemp=4040> port, if no port was
236specified.
237
238=back
119 239
120=item $SELF 240=item $SELF
121 241
122Contains the current port id while executing C<rcv> callbacks or C<psub> 242Contains the current port id while executing C<rcv> callbacks or C<psub>
123blocks. 243blocks.
126 246
127Due to some quirks in how perl exports variables, it is impossible to 247Due to some quirks in how perl exports variables, it is impossible to
128just export C<$SELF>, all the symbols called C<SELF> are exported by this 248just export C<$SELF>, all the symbols called C<SELF> are exported by this
129module, but only C<$SELF> is currently used. 249module, but only C<$SELF> is currently used.
130 250
131=item snd $portid, type => @data 251=item snd $port, type => @data
132 252
133=item snd $portid, @msg 253=item snd $port, @msg
134 254
135Send the given message to the given port ID, which can identify either 255Send the given message to the given port ID, which can identify either
136a local or a remote port, and can be either a string or soemthignt hat 256a local or a remote port, and can be either a string or soemthignt hat
137stringifies a sa port ID (such as a port object :). 257stringifies a sa port ID (such as a port object :).
138 258
148JSON is used, then only strings, numbers and arrays and hashes consisting 268JSON is used, then only strings, numbers and arrays and hashes consisting
149of those are allowed (no objects). When Storable is used, then anything 269of those are allowed (no objects). When Storable is used, then anything
150that Storable can serialise and deserialise is allowed, and for the local 270that Storable can serialise and deserialise is allowed, and for the local
151node, anything can be passed. 271node, anything can be passed.
152 272
153=item kil $portid[, @reason]
154
155Kill the specified port with the given C<@reason>.
156
157If no C<@reason> is specified, then the port is killed "normally" (linked
158ports will not be kileld, or even notified).
159
160Otherwise, linked ports get killed with the same reason (second form of
161C<mon>, see below).
162
163Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
164will be reported as reason C<< die => $@ >>.
165
166Transport/communication errors are reported as C<< transport_error =>
167$message >>.
168
169=item $guard = mon $portid, $cb->(@reason)
170
171=item $guard = mon $portid, $otherport
172
173=item $guard = mon $portid, $otherport, @msg
174
175Monitor the given port and do something when the port is killed.
176
177In the first form, the callback is simply called with any number
178of C<@reason> elements (no @reason means that the port was deleted
179"normally"). Note also that I<< the callback B<must> never die >>, so use
180C<eval> if unsure.
181
182In the second form, the other port will be C<kil>'ed with C<@reason>, iff
183a @reason was specified, i.e. on "normal" kils nothing happens, while
184under all other conditions, the other port is killed with the same reason.
185
186In the last form, a message of the form C<@msg, @reason> will be C<snd>.
187
188Example: call a given callback when C<$port> is killed.
189
190 mon $port, sub { warn "port died because of <@_>\n" };
191
192Example: kill ourselves when C<$port> is killed abnormally.
193
194 mon $port, $self;
195
196Example: send us a restart message another C<$port> is killed.
197
198 mon $port, $self => "restart";
199
200=cut
201
202sub mon {
203 my ($noderef, $port, $cb) = ((split /#/, shift, 2), shift);
204
205 my $node = $NODE{$noderef} || add_node $noderef;
206
207 #TODO: ports must not be references
208 if (!ref $cb or "AnyEvent::MP::Port" eq ref $cb) {
209 if (@_) {
210 # send a kill info message
211 my (@msg) = ($cb, @_);
212 $cb = sub { snd @msg, @_ };
213 } else {
214 # simply kill other port
215 my $port = $cb;
216 $cb = sub { kil $port, @_ if @_ };
217 }
218 }
219
220 $node->monitor ($port, $cb);
221
222 defined wantarray
223 and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }
224}
225
226=item $guard = mon_guard $port, $ref, $ref...
227
228Monitors the given C<$port> and keeps the passed references. When the port
229is killed, the references will be freed.
230
231Optionally returns a guard that will stop the monitoring.
232
233This function is useful when you create e.g. timers or other watchers and
234want to free them when the port gets killed:
235
236 $port->rcv (start => sub {
237 my $timer; $timer = mon_guard $port, AE::timer 1, 1, sub {
238 undef $timer if 0.9 < rand;
239 });
240 });
241
242=cut
243
244sub mon_guard {
245 my ($port, @refs) = @_;
246
247 mon $port, sub { 0 && @refs }
248}
249
250=item lnk $port1, $port2
251
252Link two ports. This is simply a shorthand for:
253
254 mon $port1, $port2;
255 mon $port2, $port1;
256
257It means that if either one is killed abnormally, the other one gets
258killed as well.
259
260=item $local_port = port 273=item $local_port = port
261 274
262Create a new local port object that supports message matching. 275Create a new local port object that can be used either as a pattern
276matching port ("full port") or a single-callback port ("miniport"),
277depending on how C<rcv> callbacks are bound to the object.
263 278
264=item $portid = port { my @msg = @_; $finished } 279=item $port = port { my @msg = @_; $finished }
265 280
266Creates a "mini port", that is, a very lightweight port without any 281Creates a "miniport", that is, a very lightweight port without any pattern
267pattern matching behind it, and returns its ID. 282matching behind it, and returns its ID. Semantically the same as creating
283a port and calling C<rcv $port, $callback> on it.
268 284
269The block will be called for every message received on the port. When the 285The block will be called for every message received on the port. When the
270callback returns a true value its job is considered "done" and the port 286callback returns a true value its job is considered "done" and the port
271will be destroyed. Otherwise it will stay alive. 287will be destroyed. Otherwise it will stay alive.
272 288
273The message will be passed as-is, no extra argument (i.e. no port id) will 289The message will be passed as-is, no extra argument (i.e. no port id) will
274be passed to the callback. 290be passed to the callback.
275 291
276If you need the local port id in the callback, this works nicely: 292If you need the local port id in the callback, this works nicely:
277 293
278 my $port; $port = miniport { 294 my $port; $port = port {
279 snd $otherport, reply => $port; 295 snd $otherport, reply => $port;
280 }; 296 };
281 297
282=cut 298=cut
299
300sub rcv($@);
283 301
284sub port(;&) { 302sub port(;&) {
285 my $id = "$UNIQ." . $ID++; 303 my $id = "$UNIQ." . $ID++;
286 my $port = "$NODE#$id"; 304 my $port = "$NODE#$id";
287 305
288 if (@_) { 306 if (@_) {
307 rcv $port, shift;
308 } else {
309 $PORT{$id} = sub { }; # nop
310 }
311
312 $port
313}
314
315=item reg $port, $name
316
317=item reg $name
318
319Registers the given port (or C<$SELF><<< if missing) under the name
320C<$name>. If the name already exists it is replaced.
321
322A port can only be registered under one well known name.
323
324A port automatically becomes unregistered when it is killed.
325
326=cut
327
328sub reg(@) {
329 my $port = @_ > 1 ? shift : $SELF || Carp::croak 'reg: called with one argument only, but $SELF not set,';
330
331 $REG{$_[0]} = $port;
332}
333
334=item rcv $port, $callback->(@msg)
335
336Replaces the callback on the specified miniport (after converting it to
337one if required).
338
339=item rcv $port, tagstring => $callback->(@msg), ...
340
341=item rcv $port, $smartmatch => $callback->(@msg), ...
342
343=item rcv $port, [$smartmatch...] => $callback->(@msg), ...
344
345Register callbacks to be called on matching messages on the given full
346port (after converting it to one if required) and return the port.
347
348The callback has to return a true value when its work is done, after
349which is will be removed, or a false value in which case it will stay
350registered.
351
352The global C<$SELF> (exported by this module) contains C<$port> while
353executing the callback.
354
355Runtime errors during callback execution will result in the port being
356C<kil>ed.
357
358If the match is an array reference, then it will be matched against the
359first elements of the message, otherwise only the first element is being
360matched.
361
362Any element in the match that is specified as C<_any_> (a function
363exported by this module) matches any single element of the message.
364
365While not required, it is highly recommended that the first matching
366element is a string identifying the message. The one-string-only match is
367also the most efficient match (by far).
368
369Example: create a port and bind receivers on it in one go.
370
371 my $port = rcv port,
372 msg1 => sub { ...; 0 },
373 msg2 => sub { ...; 0 },
374 ;
375
376Example: create a port, bind receivers and send it in a message elsewhere
377in one go:
378
379 snd $otherport, reply =>
380 rcv port,
381 msg1 => sub { ...; 0 },
382 ...
383 ;
384
385=cut
386
387sub rcv($@) {
388 my $port = shift;
389 my ($noderef, $portid) = split /#/, $port, 2;
390
391 ($NODE{$noderef} || add_node $noderef) == $NODE{""}
392 or Carp::croak "$port: rcv can only be called on local ports, caught";
393
394 if (@_ == 1) {
289 my $cb = shift; 395 my $cb = shift;
396 delete $PORT_DATA{$portid};
290 $PORT{$id} = sub { 397 $PORT{$portid} = sub {
291 local $SELF = $port; 398 local $SELF = $port;
292 eval { 399 eval {
293 &$cb 400 &$cb
294 and kil $id; 401 and kil $port;
295 }; 402 };
296 _self_die if $@; 403 _self_die if $@;
297 }; 404 };
298 } else { 405 } else {
406 my $self = $PORT_DATA{$portid} ||= do {
299 my $self = bless { 407 my $self = bless {
300 id => "$NODE#$id", 408 id => $port,
301 }, "AnyEvent::MP::Port"; 409 }, "AnyEvent::MP::Port";
302 410
303 $PORT_DATA{$id} = $self;
304 $PORT{$id} = sub { 411 $PORT{$portid} = sub {
305 local $SELF = $port; 412 local $SELF = $port;
306 413
307 eval { 414 eval {
308 for (@{ $self->{rc0}{$_[0]} }) { 415 for (@{ $self->{rc0}{$_[0]} }) {
309 $_ && &{$_->[0]} 416 $_ && &{$_->[0]}
310 && undef $_; 417 && undef $_;
311 } 418 }
312 419
313 for (@{ $self->{rcv}{$_[0]} }) { 420 for (@{ $self->{rcv}{$_[0]} }) {
314 $_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1] 421 $_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1]
315 && &{$_->[0]} 422 && &{$_->[0]}
316 && undef $_; 423 && undef $_;
317 } 424 }
318 425
319 for (@{ $self->{any} }) { 426 for (@{ $self->{any} }) {
320 $_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1] 427 $_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1]
321 && &{$_->[0]} 428 && &{$_->[0]}
322 && undef $_; 429 && undef $_;
430 }
323 } 431 };
432 _self_die if $@;
324 }; 433 };
325 _self_die if $@; 434
435 $self
326 }; 436 };
327 }
328 437
329 $port
330}
331
332=item reg $portid, $name
333
334Registers the given port under the name C<$name>. If the name already
335exists it is replaced.
336
337A port can only be registered under one well known name.
338
339A port automatically becomes unregistered when it is killed.
340
341=cut
342
343sub reg(@) {
344 my ($portid, $name) = @_;
345
346 $REG{$name} = $portid;
347}
348
349=item rcv $portid, tagstring => $callback->(@msg), ...
350
351=item rcv $portid, $smartmatch => $callback->(@msg), ...
352
353=item rcv $portid, [$smartmatch...] => $callback->(@msg), ...
354
355Register callbacks to be called on matching messages on the given port.
356
357The callback has to return a true value when its work is done, after
358which is will be removed, or a false value in which case it will stay
359registered.
360
361The global C<$SELF> (exported by this module) contains C<$portid> while
362executing the callback.
363
364Runtime errors wdurign callback execution will result in the port being
365C<kil>ed.
366
367If the match is an array reference, then it will be matched against the
368first elements of the message, otherwise only the first element is being
369matched.
370
371Any element in the match that is specified as C<_any_> (a function
372exported by this module) matches any single element of the message.
373
374While not required, it is highly recommended that the first matching
375element is a string identifying the message. The one-string-only match is
376also the most efficient match (by far).
377
378=cut
379
380sub rcv($@) {
381 my ($noderef, $port) = split /#/, shift, 2;
382
383 ($NODE{$noderef} || add_node $noderef) == $NODE{""}
384 or Carp::croak "$noderef#$port: rcv can only be called on local ports, caught";
385
386 my $self = $PORT_DATA{$port}
387 or Carp::croak "$noderef#$port: rcv can only be called on message matching ports, caught";
388
389 "AnyEvent::MP::Port" eq ref $self 438 "AnyEvent::MP::Port" eq ref $self
390 or Carp::croak "$noderef#$port: rcv can only be called on message matching ports, caught"; 439 or Carp::croak "$port: rcv can only be called on message matching ports, caught";
391 440
392 while (@_) { 441 while (@_) {
393 my ($match, $cb) = splice @_, 0, 2; 442 my ($match, $cb) = splice @_, 0, 2;
394 443
395 if (!ref $match) { 444 if (!ref $match) {
396 push @{ $self->{rc0}{$match} }, [$cb]; 445 push @{ $self->{rc0}{$match} }, [$cb];
397 } elsif (("ARRAY" eq ref $match && !ref $match->[0])) { 446 } elsif (("ARRAY" eq ref $match && !ref $match->[0])) {
398 my ($type, @match) = @$match; 447 my ($type, @match) = @$match;
399 @match 448 @match
400 ? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match] 449 ? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match]
401 : push @{ $self->{rc0}{$match->[0]} }, [$cb]; 450 : push @{ $self->{rc0}{$match->[0]} }, [$cb];
402 } else { 451 } else {
403 push @{ $self->{any} }, [$cb, $match]; 452 push @{ $self->{any} }, [$cb, $match];
453 }
404 } 454 }
405 } 455 }
456
457 $port
406} 458}
407 459
408=item $closure = psub { BLOCK } 460=item $closure = psub { BLOCK }
409 461
410Remembers C<$SELF> and creates a closure out of the BLOCK. When the 462Remembers C<$SELF> and creates a closure out of the BLOCK. When the
441 $res 493 $res
442 } 494 }
443 } 495 }
444} 496}
445 497
446=back 498=item $guard = mon $port, $cb->(@reason)
447 499
448=head1 FUNCTIONS FOR NODES 500=item $guard = mon $port, $rcvport
449 501
450=over 4 502=item $guard = mon $port
451 503
452=item become_public endpoint... 504=item $guard = mon $port, $rcvport, @msg
453 505
454Tells the node to become a public node, i.e. reachable from other nodes. 506Monitor the given port and do something when the port is killed, and
507optionally return a guard that can be used to stop monitoring again.
455 508
456If no arguments are given, or the first argument is C<undef>, then 509In the first form (callback), the callback is simply called with any
457AnyEvent::MP tries to bind on port C<4040> on all IP addresses that the 510number of C<@reason> elements (no @reason means that the port was deleted
458local nodename resolves to. 511"normally"). Note also that I<< the callback B<must> never die >>, so use
512C<eval> if unsure.
459 513
460Otherwise the first argument must be an array-reference with transport 514In the second form (another port given), the other port (C<$rcvport)
461endpoints ("ip:port", "hostname:port") or port numbers (in which case the 515will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on
462local nodename is used as hostname). The endpoints are all resolved and 516"normal" kils nothing happens, while under all other conditions, the other
463will become the node reference. 517port is killed with the same reason.
464 518
519The third form (kill self) is the same as the second form, except that
520C<$rvport> defaults to C<$SELF>.
521
522In the last form (message), a message of the form C<@msg, @reason> will be
523C<snd>.
524
525As a rule of thumb, monitoring requests should always monitor a port from
526a local port (or callback). The reason is that kill messages might get
527lost, just like any other message. Another less obvious reason is that
528even monitoring requests can get lost (for exmaple, when the connection
529to the other node goes down permanently). When monitoring a port locally
530these problems do not exist.
531
532Example: call a given callback when C<$port> is killed.
533
534 mon $port, sub { warn "port died because of <@_>\n" };
535
536Example: kill ourselves when C<$port> is killed abnormally.
537
538 mon $port;
539
540Example: send us a restart message when another C<$port> is killed.
541
542 mon $port, $self => "restart";
543
465=cut 544=cut
545
546sub mon {
547 my ($noderef, $port) = split /#/, shift, 2;
548
549 my $node = $NODE{$noderef} || add_node $noderef;
550
551 my $cb = @_ ? shift : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,';
552
553 unless (ref $cb) {
554 if (@_) {
555 # send a kill info message
556 my (@msg) = ($cb, @_);
557 $cb = sub { snd @msg, @_ };
558 } else {
559 # simply kill other port
560 my $port = $cb;
561 $cb = sub { kil $port, @_ if @_ };
562 }
563 }
564
565 $node->monitor ($port, $cb);
566
567 defined wantarray
568 and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }
569}
570
571=item $guard = mon_guard $port, $ref, $ref...
572
573Monitors the given C<$port> and keeps the passed references. When the port
574is killed, the references will be freed.
575
576Optionally returns a guard that will stop the monitoring.
577
578This function is useful when you create e.g. timers or other watchers and
579want to free them when the port gets killed:
580
581 $port->rcv (start => sub {
582 my $timer; $timer = mon_guard $port, AE::timer 1, 1, sub {
583 undef $timer if 0.9 < rand;
584 });
585 });
586
587=cut
588
589sub mon_guard {
590 my ($port, @refs) = @_;
591
592 #TODO: mon-less form?
593
594 mon $port, sub { 0 && @refs }
595}
596
597=item kil $port[, @reason]
598
599Kill the specified port with the given C<@reason>.
600
601If no C<@reason> is specified, then the port is killed "normally" (linked
602ports will not be kileld, or even notified).
603
604Otherwise, linked ports get killed with the same reason (second form of
605C<mon>, see below).
606
607Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
608will be reported as reason C<< die => $@ >>.
609
610Transport/communication errors are reported as C<< transport_error =>
611$message >>.
612
613=cut
614
615=item $port = spawn $node, $initfunc[, @initdata]
616
617Creates a port on the node C<$node> (which can also be a port ID, in which
618case it's the node where that port resides).
619
620The port ID of the newly created port is return immediately, and it is
621permissible to immediately start sending messages or monitor the port.
622
623After the port has been created, the init function is
624called. This function must be a fully-qualified function name
625(e.g. C<MyApp::Chat::Server::init>). To specify a function in the main
626program, use C<::name>.
627
628If the function doesn't exist, then the node tries to C<require>
629the package, then the package above the package and so on (e.g.
630C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
631exists or it runs out of package names.
632
633The init function is then called with the newly-created port as context
634object (C<$SELF>) and the C<@initdata> values as arguments.
635
636A common idiom is to pass your own port, monitor the spawned port, and
637in the init function, monitor the original port. This two-way monitoring
638ensures that both ports get cleaned up when there is a problem.
639
640Example: spawn a chat server port on C<$othernode>.
641
642 # this node, executed from within a port context:
643 my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;
644 mon $server;
645
646 # init function on C<$othernode>
647 sub connect {
648 my ($srcport) = @_;
649
650 mon $srcport;
651
652 rcv $SELF, sub {
653 ...
654 };
655 }
656
657=cut
658
659sub _spawn {
660 my $port = shift;
661 my $init = shift;
662
663 local $SELF = "$NODE#$port";
664 eval {
665 &{ load_func $init }
666 };
667 _self_die if $@;
668}
669
670sub spawn(@) {
671 my ($noderef, undef) = split /#/, shift, 2;
672
673 my $id = "$RUNIQ." . $ID++;
674
675 $_[0] =~ /::/
676 or Carp::croak "spawn init function must be a fully-qualified name, caught";
677
678 ($NODE{$noderef} || add_node $noderef)
679 ->send (["", "AnyEvent::MP::_spawn" => $id, @_]);
680
681 "$noderef#$id"
682}
466 683
467=back 684=back
468 685
469=head1 NODE MESSAGES 686=head1 NODE MESSAGES
470 687
471Nodes understand the following messages sent to them. Many of them take 688Nodes understand the following messages sent to them. Many of them take
472arguments called C<@reply>, which will simply be used to compose a reply 689arguments called C<@reply>, which will simply be used to compose a reply
473message - C<$reply[0]> is the port to reply to, C<$reply[1]> the type and 690message - C<$reply[0]> is the port to reply to, C<$reply[1]> the type and
474the remaining arguments are simply the message data. 691the remaining arguments are simply the message data.
475 692
693While other messages exist, they are not public and subject to change.
694
476=over 4 695=over 4
477 696
478=cut 697=cut
479 698
480=item lookup => $name, @reply 699=item lookup => $name, @reply
508 snd $NODE, time => $myport, timereply => 1, 2; 727 snd $NODE, time => $myport, timereply => 1, 2;
509 # => snd $myport, timereply => 1, 2, <time> 728 # => snd $myport, timereply => 1, 2, <time>
510 729
511=back 730=back
512 731
732=head1 AnyEvent::MP vs. Distributed Erlang
733
734AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
735== aemp node, Erlang process == aemp port), so many of the documents and
736programming techniques employed by Erlang apply to AnyEvent::MP. Here is a
737sample:
738
739 http://www.Erlang.se/doc/programming_rules.shtml
740 http://Erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4
741 http://Erlang.org/download/Erlang-book-part1.pdf # chapters 5 and 6
742 http://Erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5
743
744Despite the similarities, there are also some important differences:
745
746=over 4
747
748=item * Node references contain the recipe on how to contact them.
749
750Erlang relies on special naming and DNS to work everywhere in the
751same way. AEMP relies on each node knowing it's own address(es), with
752convenience functionality.
753
754This means that AEMP requires a less tightly controlled environment at the
755cost of longer node references and a slightly higher management overhead.
756
757=item * Erlang uses processes and a mailbox, AEMP does not queue.
758
759Erlang uses processes that selctively receive messages, and therefore
760needs a queue. AEMP is event based, queuing messages would serve no useful
761purpose.
762
763(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).
764
765=item * Erlang sends are synchronous, AEMP sends are asynchronous.
766
767Sending messages in Erlang is synchronous and blocks the process. AEMP
768sends are immediate, connection establishment is handled in the
769background.
770
771=item * Erlang can silently lose messages, AEMP cannot.
772
773Erlang makes few guarantees on messages delivery - messages can get lost
774without any of the processes realising it (i.e. you send messages a, b,
775and c, and the other side only receives messages a and c).
776
777AEMP guarantees correct ordering, and the guarantee that there are no
778holes in the message sequence.
779
780=item * In Erlang, processes can be declared dead and later be found to be
781alive.
782
783In Erlang it can happen that a monitored process is declared dead and
784linked processes get killed, but later it turns out that the process is
785still alive - and can receive messages.
786
787In AEMP, when port monitoring detects a port as dead, then that port will
788eventually be killed - it cannot happen that a node detects a port as dead
789and then later sends messages to it, finding it is still alive.
790
791=item * Erlang can send messages to the wrong port, AEMP does not.
792
793In Erlang it is quite possible that a node that restarts reuses a process
794ID known to other nodes for a completely different process, causing
795messages destined for that process to end up in an unrelated process.
796
797AEMP never reuses port IDs, so old messages or old port IDs floating
798around in the network will not be sent to an unrelated port.
799
800=item * Erlang uses unprotected connections, AEMP uses secure
801authentication and can use TLS.
802
803AEMP can use a proven protocol - SSL/TLS - to protect connections and
804securely authenticate nodes.
805
806=item * The AEMP protocol is optimised for both text-based and binary
807communications.
808
809The AEMP protocol, unlike the Erlang protocol, supports both
810language-independent text-only protocols (good for debugging) and binary,
811language-specific serialisers (e.g. Storable).
812
813It has also been carefully designed to be implementable in other languages
814with a minimum of work while gracefully degrading fucntionality to make the
815protocol simple.
816
817=item * AEMP has more flexible monitoring options than Erlang.
818
819In Erlang, you can chose to receive I<all> exit signals as messages
820or I<none>, there is no in-between, so monitoring single processes is
821difficult to implement. Monitoring in AEMP is more flexible than in
822Erlang, as one can choose between automatic kill, exit message or callback
823on a per-process basis.
824
825=item * Erlang tries to hide remote/local connections, AEMP does not.
826
827Monitoring in Erlang is not an indicator of process death/crashes,
828as linking is (except linking is unreliable in Erlang).
829
830In AEMP, you don't "look up" registered port names or send to named ports
831that might or might not be persistent. Instead, you normally spawn a port
832on the remote node. The init function monitors the you, and you monitor
833the remote port. Since both monitors are local to the node, they are much
834more reliable.
835
836This also saves round-trips and avoids sending messages to the wrong port
837(hard to do in Erlang).
838
839=back
840
513=head1 SEE ALSO 841=head1 SEE ALSO
514 842
515L<AnyEvent>. 843L<AnyEvent>.
516 844
517=head1 AUTHOR 845=head1 AUTHOR

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines