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.9 by root, Sun Aug 2 15:47:04 2009 UTC vs.
Revision 1.35 by root, Thu Aug 6 10:21: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 resreve 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 _any_ 115 NODE $NODE *SELF node_of _any_
90 create_port create_port_on 116 resolve_node initialise_node
91 become_slave become_public 117 snd rcv mon kil reg psub
118 port
92); 119);
93 120
121our $SELF;
122
123sub _self_die() {
124 my $msg = $@;
125 $msg =~ s/\n+$// unless ref $msg;
126 kil $SELF, die => $msg;
127}
128
94=item NODE / $NODE 129=item $thisnode = NODE / $NODE
95 130
96The C<NODE ()> function and the C<$NODE> variable contain the noderef of 131The C<NODE> function returns, and the C<$NODE> variable contains
97the 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
98C<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.
99 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
100=item snd $portid, type => @data 244=item snd $port, type => @data
101 245
102=item snd $portid, @msg 246=item snd $port, @msg
103 247
104Send 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
105a 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
106stringifies a sa port ID (such as a port object :). 250stringifies a sa port ID (such as a port object :).
107 251
117JSON is used, then only strings, numbers and arrays and hashes consisting 261JSON is used, then only strings, numbers and arrays and hashes consisting
118of those are allowed (no objects). When Storable is used, then anything 262of those are allowed (no objects). When Storable is used, then anything
119that Storable can serialise and deserialise is allowed, and for the local 263that Storable can serialise and deserialise is allowed, and for the local
120node, anything can be passed. 264node, anything can be passed.
121 265
122=item $local_port = create_port 266=item $local_port = port
123 267
124Create a new local port object. See the next section for allowed methods. 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.
125 271
126=cut 272=item $port = port { my @msg = @_; $finished }
127 273
128sub create_port { 274Creates a "miniport", that is, a very lightweight port without any pattern
129 my $id = "$AnyEvent::MP::Base::UNIQ." . ++$AnyEvent::MP::Base::ID; 275matching behind it, and returns its ID. Semantically the same as creating
276a port and calling C<rcv $port, $callback> on it.
130 277
131 my $self = bless { 278The block will be called for every message received on the port. When the
132 id => "$NODE#$id", 279callback returns a true value its job is considered "done" and the port
133 names => [$id], 280will be destroyed. Otherwise it will stay alive.
134 }, "AnyEvent::MP::Port";
135 281
136 $AnyEvent::MP::Base::PORT{$id} = sub { 282The message will be passed as-is, no extra argument (i.e. no port id) will
137 unshift @_, $self; 283be passed to the callback.
138 284
139 for (@{ $self->{rc0}{$_[1]} }) { 285If you need the local port id in the callback, this works nicely:
140 $_ && &{$_->[0]}
141 && undef $_;
142 }
143 286
144 for (@{ $self->{rcv}{$_[1]} }) { 287 my $port; $port = port {
145 $_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1] 288 snd $otherport, reply => $port;
146 && &{$_->[0]}
147 && undef $_;
148 }
149
150 for (@{ $self->{any} }) {
151 $_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1]
152 && &{$_->[0]}
153 && undef $_;
154 }
155 }; 289 };
156 290
157 $self 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
158} 306}
159 307
160package AnyEvent::MP::Port; 308=item reg $port, $name
161 309
162=back 310Registers the given port under the name C<$name>. If the name already
311exists it is replaced.
163 312
164=head1 METHODS FOR PORT OBJECTS 313A port can only be registered under one well known name.
165 314
166=over 4 315A port automatically becomes unregistered when it is killed.
167 316
168=item "$port"
169
170A port object stringifies to its port ID, so can be used directly for
171C<snd> operations.
172
173=cut 317=cut
174 318
175use overload 319sub reg(@) {
176 '""' => sub { $_[0]{id} }, 320 my ($port, $name) = @_;
177 fallback => 1;
178 321
179=item $port->rcv (type => $callback->($port, @msg)) 322 $REG{$name} = $port;
323}
180 324
181=item $port->rcv ($smartmatch => $callback->($port, @msg)) 325=item rcv $port, $callback->(@msg)
182 326
327Replaces the callback on the specified miniport (after converting it to
328one if required).
329
330=item rcv $port, tagstring => $callback->(@msg), ...
331
332=item rcv $port, $smartmatch => $callback->(@msg), ...
333
183=item $port->rcv ([$smartmatch...] => $callback->($port, @msg)) 334=item rcv $port, [$smartmatch...] => $callback->(@msg), ...
184 335
185Register a callback on the given port. 336Register callbacks to be called on matching messages on the given full
337port (after converting it to one if required).
186 338
187The callback has to return a true value when its work is done, after 339The callback has to return a true value when its work is done, after
188which is will be removed, or a false value in which case it will stay 340which is will be removed, or a false value in which case it will stay
189registered. 341registered.
190 342
343The global C<$SELF> (exported by this module) contains C<$port> while
344executing the callback.
345
346Runtime errors wdurign callback execution will result in the port being
347C<kil>ed.
348
191If the match is an array reference, then it will be matched against the 349If the match is an array reference, then it will be matched against the
192first elements of the message, otherwise only the first element is being 350first elements of the message, otherwise only the first element is being
193matched. 351matched.
194 352
195Any element in the match that is specified as C<_any_> (a function 353Any element in the match that is specified as C<_any_> (a function
200also the most efficient match (by far). 358also the most efficient match (by far).
201 359
202=cut 360=cut
203 361
204sub rcv($@) { 362sub rcv($@) {
205 my ($self, $match, $cb) = @_; 363 my $port = shift;
364 my ($noderef, $portid) = split /#/, $port, 2;
206 365
207 if (!ref $match) { 366 ($NODE{$noderef} || add_node $noderef) == $NODE{""}
208 push @{ $self->{rc0}{$match} }, [$cb]; 367 or Carp::croak "$port: rcv can only be called on local ports, caught";
209 } elsif (("ARRAY" eq ref $match && !ref $match->[0])) { 368
210 my ($type, @match) = @$match; 369 if (@_ == 1) {
211 @match 370 my $cb = shift;
212 ? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match] 371 delete $PORT_DATA{$portid};
213 : push @{ $self->{rc0}{$match->[0]} }, [$cb]; 372 $PORT{$portid} = sub {
373 local $SELF = $port;
374 eval {
375 &$cb
376 and kil $port;
377 };
378 _self_die if $@;
379 };
214 } else { 380 } else {
381 my $self = $PORT_DATA{$portid} ||= do {
382 my $self = bless {
383 id => $port,
384 }, "AnyEvent::MP::Port";
385
386 $PORT{$portid} = sub {
387 local $SELF = $port;
388
389 eval {
390 for (@{ $self->{rc0}{$_[0]} }) {
391 $_ && &{$_->[0]}
392 && undef $_;
393 }
394
395 for (@{ $self->{rcv}{$_[0]} }) {
396 $_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1]
397 && &{$_->[0]}
398 && undef $_;
399 }
400
401 for (@{ $self->{any} }) {
402 $_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1]
403 && &{$_->[0]}
404 && undef $_;
405 }
406 };
407 _self_die if $@;
408 };
409
410 $self
411 };
412
413 "AnyEvent::MP::Port" eq ref $self
414 or Carp::croak "$port: rcv can only be called on message matching ports, caught";
415
416 while (@_) {
417 my ($match, $cb) = splice @_, 0, 2;
418
419 if (!ref $match) {
420 push @{ $self->{rc0}{$match} }, [$cb];
421 } elsif (("ARRAY" eq ref $match && !ref $match->[0])) {
422 my ($type, @match) = @$match;
423 @match
424 ? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match]
425 : push @{ $self->{rc0}{$match->[0]} }, [$cb];
426 } else {
215 push @{ $self->{any} }, [$cb, $match]; 427 push @{ $self->{any} }, [$cb, $match];
428 }
429 }
430 }
431
432 $port
433}
434
435=item $closure = psub { BLOCK }
436
437Remembers C<$SELF> and creates a closure out of the BLOCK. When the
438closure is executed, sets up the environment in the same way as in C<rcv>
439callbacks, i.e. runtime errors will cause the port to get C<kil>ed.
440
441This is useful when you register callbacks from C<rcv> callbacks:
442
443 rcv delayed_reply => sub {
444 my ($delay, @reply) = @_;
445 my $timer = AE::timer $delay, 0, psub {
446 snd @reply, $SELF;
447 };
448 };
449
450=cut
451
452sub psub(&) {
453 my $cb = shift;
454
455 my $port = $SELF
456 or Carp::croak "psub can only be called from within rcv or psub callbacks, not";
457
458 sub {
459 local $SELF = $port;
460
461 if (wantarray) {
462 my @res = eval { &$cb };
463 _self_die if $@;
464 @res
465 } else {
466 my $res = eval { &$cb };
467 _self_die if $@;
468 $res
469 }
216 } 470 }
217} 471}
218 472
219=item $port->register ($name) 473=item $guard = mon $port, $cb->(@reason)
220 474
221Registers the given port under the well known name C<$name>. If the name 475=item $guard = mon $port, $otherport
222already exists it is replaced.
223 476
224A port can only be registered under one well known name. 477=item $guard = mon $port, $otherport, @msg
225 478
226=cut 479Monitor the given port and do something when the port is killed.
227 480
228sub register { 481In the first form, the callback is simply called with any number
229 my ($self, $name) = @_; 482of C<@reason> elements (no @reason means that the port was deleted
483"normally"). Note also that I<< the callback B<must> never die >>, so use
484C<eval> if unsure.
230 485
231 $self->{wkname} = $name; 486In the second form, the other port will be C<kil>'ed with C<@reason>, iff
232 $AnyEvent::MP::Base::WKP{$name} = "$self"; 487a @reason was specified, i.e. on "normal" kils nothing happens, while
488under all other conditions, the other port is killed with the same reason.
489
490In the last form, a message of the form C<@msg, @reason> will be C<snd>.
491
492Example: call a given callback when C<$port> is killed.
493
494 mon $port, sub { warn "port died because of <@_>\n" };
495
496Example: kill ourselves when C<$port> is killed abnormally.
497
498 mon $port, $self;
499
500Example: send us a restart message another C<$port> is killed.
501
502 mon $port, $self => "restart";
503
504=cut
505
506sub mon {
507 my ($noderef, $port) = split /#/, shift, 2;
508
509 my $node = $NODE{$noderef} || add_node $noderef;
510
511 my $cb = shift;
512
513 unless (ref $cb) {
514 if (@_) {
515 # send a kill info message
516 my (@msg) = ($cb, @_);
517 $cb = sub { snd @msg, @_ };
518 } else {
519 # simply kill other port
520 my $port = $cb;
521 $cb = sub { kil $port, @_ if @_ };
522 }
523 }
524
525 $node->monitor ($port, $cb);
526
527 defined wantarray
528 and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }
233} 529}
234 530
235=item $port->destroy 531=item $guard = mon_guard $port, $ref, $ref...
236 532
237Explicitly destroy/remove/nuke/vaporise the port. 533Monitors the given C<$port> and keeps the passed references. When the port
534is killed, the references will be freed.
238 535
239Ports are normally kept alive by there mere existance alone, and need to 536Optionally returns a guard that will stop the monitoring.
240be destroyed explicitly.
241 537
242=cut 538This function is useful when you create e.g. timers or other watchers and
539want to free them when the port gets killed:
243 540
244sub destroy { 541 $port->rcv (start => sub {
245 my ($self) = @_; 542 my $timer; $timer = mon_guard $port, AE::timer 1, 1, sub {
543 undef $timer if 0.9 < rand;
544 });
545 });
246 546
247 delete $AnyEvent::MP::Base::WKP{ $self->{wkname} }; 547=cut
248 548
249 delete $AnyEvent::MP::Base::PORT{$_} 549sub mon_guard {
250 for @{ $self->{names} }; 550 my ($port, @refs) = @_;
551
552 mon $port, sub { 0 && @refs }
251} 553}
252 554
253=back 555=item lnk $port1, $port2
254 556
255=head1 FUNCTIONS FOR NODES 557Link two ports. This is simply a shorthand for:
256 558
257=over 4 559 mon $port1, $port2;
560 mon $port2, $port1;
258 561
259=item mon $noderef, $callback->($noderef, $status, $) 562It means that if either one is killed abnormally, the other one gets
563killed as well.
260 564
261Monitors the given noderef. 565=item kil $port[, @reason]
262 566
263=item become_public endpoint... 567Kill the specified port with the given C<@reason>.
264 568
265Tells the node to become a public node, i.e. reachable from other nodes. 569If no C<@reason> is specified, then the port is killed "normally" (linked
570ports will not be kileld, or even notified).
266 571
267If no arguments are given, or the first argument is C<undef>, then 572Otherwise, linked ports get killed with the same reason (second form of
268AnyEvent::MP tries to bind on port C<4040> on all IP addresses that the 573C<mon>, see below).
269local nodename resolves to.
270 574
271Otherwise the first argument must be an array-reference with transport 575Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
272endpoints ("ip:port", "hostname:port") or port numbers (in which case the 576will be reported as reason C<< die => $@ >>.
273local nodename is used as hostname). The endpoints are all resolved and
274will become the node reference.
275 577
276=cut 578Transport/communication errors are reported as C<< transport_error =>
579$message >>.
277 580
278=back 581=back
279 582
280=head1 NODE MESSAGES 583=head1 NODE MESSAGES
281 584
282Nodes understand the following messages sent to them. Many of them take 585Nodes understand the following messages sent to them. Many of them take
283arguments called C<@reply>, which will simply be used to compose a reply 586arguments called C<@reply>, which will simply be used to compose a reply
284message - C<$reply[0]> is the port to reply to, C<$reply[1]> the type and 587message - C<$reply[0]> is the port to reply to, C<$reply[1]> the type and
285the remaining arguments are simply the message data. 588the remaining arguments are simply the message data.
286 589
590While other messages exist, they are not public and subject to change.
591
287=over 4 592=over 4
288 593
289=cut 594=cut
290 595
291=item wkp => $name, @reply 596=item lookup => $name, @reply
292 597
293Replies with the port ID of the specified well-known port, or C<undef>. 598Replies with the port ID of the specified well-known port, or C<undef>.
294 599
295=item devnull => ... 600=item devnull => ...
296 601
319 snd $NODE, time => $myport, timereply => 1, 2; 624 snd $NODE, time => $myport, timereply => 1, 2;
320 # => snd $myport, timereply => 1, 2, <time> 625 # => snd $myport, timereply => 1, 2, <time>
321 626
322=back 627=back
323 628
629=head1 AnyEvent::MP vs. Distributed Erlang
630
631AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
632== aemp node, Erlang process == aemp port), so many of the documents and
633programming techniques employed by Erlang apply to AnyEvent::MP. Here is a
634sample:
635
636 http://www.Erlang.se/doc/programming_rules.shtml
637 http://Erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4
638 http://Erlang.org/download/Erlang-book-part1.pdf # chapters 5 and 6
639 http://Erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5
640
641Despite the similarities, there are also some important differences:
642
643=over 4
644
645=item * Node references contain the recipe on how to contact them.
646
647Erlang relies on special naming and DNS to work everywhere in the
648same way. AEMP relies on each node knowing it's own address(es), with
649convenience functionality.
650
651This means that AEMP requires a less tightly controlled environment at the
652cost of longer node references and a slightly higher management overhead.
653
654=item * Erlang uses processes and a mailbox, AEMP does not queue.
655
656Erlang uses processes that selctively receive messages, and therefore
657needs a queue. AEMP is event based, queuing messages would serve no useful
658purpose.
659
660(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).
661
662=item * Erlang sends are synchronous, AEMP sends are asynchronous.
663
664Sending messages in Erlang is synchronous and blocks the process. AEMP
665sends are immediate, connection establishment is handled in the
666background.
667
668=item * Erlang can silently lose messages, AEMP cannot.
669
670Erlang makes few guarantees on messages delivery - messages can get lost
671without any of the processes realising it (i.e. you send messages a, b,
672and c, and the other side only receives messages a and c).
673
674AEMP guarantees correct ordering, and the guarantee that there are no
675holes in the message sequence.
676
677=item * In Erlang, processes can be declared dead and later be found to be
678alive.
679
680In Erlang it can happen that a monitored process is declared dead and
681linked processes get killed, but later it turns out that the process is
682still alive - and can receive messages.
683
684In AEMP, when port monitoring detects a port as dead, then that port will
685eventually be killed - it cannot happen that a node detects a port as dead
686and then later sends messages to it, finding it is still alive.
687
688=item * Erlang can send messages to the wrong port, AEMP does not.
689
690In Erlang it is quite possible that a node that restarts reuses a process
691ID known to other nodes for a completely different process, causing
692messages destined for that process to end up in an unrelated process.
693
694AEMP never reuses port IDs, so old messages or old port IDs floating
695around in the network will not be sent to an unrelated port.
696
697=item * Erlang uses unprotected connections, AEMP uses secure
698authentication and can use TLS.
699
700AEMP can use a proven protocol - SSL/TLS - to protect connections and
701securely authenticate nodes.
702
703=item * The AEMP protocol is optimised for both text-based and binary
704communications.
705
706The AEMP protocol, unlike the Erlang protocol, supports both
707language-independent text-only protocols (good for debugging) and binary,
708language-specific serialisers (e.g. Storable).
709
710It has also been carefully designed to be implementable in other languages
711with a minimum of work while gracefully degrading fucntionality to make the
712protocol simple.
713
714=item * AEMP has more flexible monitoring options than Erlang.
715
716In Erlang, you can chose to receive I<all> exit signals as messages
717or I<none>, there is no in-between, so monitoring single processes is
718difficult to implement. Monitoring in AEMP is more flexible than in
719Erlang, as one can choose between automatic kill, exit message or callback
720on a per-process basis.
721
722=item * Erlang has different semantics for monitoring and linking, AEMP has the same.
723
724Monitoring in Erlang is not an indicator of process death/crashes,
725as linking is (except linking is unreliable in Erlang). In AEMP, the
726semantics of monitoring and linking are identical, linking is simply
727two-way monitoring with automatic kill.
728
729=back
730
324=head1 SEE ALSO 731=head1 SEE ALSO
325 732
326L<AnyEvent>. 733L<AnyEvent>.
327 734
328=head1 AUTHOR 735=head1 AUTHOR

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines