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.21 by root, Tue Aug 4 14:10:51 2009 UTC vs.
Revision 1.36 by root, Thu Aug 6 10:46:48 2009 UTC

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines