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.31 by root, Wed Aug 5 19:55:58 2009 UTC vs.
Revision 1.36 by root, Thu Aug 6 10:46:48 2009 UTC

22 snd $port2, ping => $port1; 22 snd $port2, ping => $port1;
23 23
24 # more, smarter, matches (_any_ is exported by this module) 24 # more, smarter, matches (_any_ is exported by this module)
25 rcv $port, [child_died => $pid] => sub { ... 25 rcv $port, [child_died => $pid] => sub { ...
26 rcv $port, [_any_, _any_, 3] => sub { .. $_[2] is 3 26 rcv $port, [_any_, _any_, 3] => sub { .. $_[2] is 3
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
27 35
28=head1 DESCRIPTION 36=head1 DESCRIPTION
29 37
30This module (-family) implements a simple message passing framework. 38This module (-family) implements a simple message passing framework.
31 39
123The C<NODE> function returns, and the C<$NODE> variable contains 131The C<NODE> function returns, and the C<$NODE> variable contains
124the noderef of the local node. The value is initialised by a call 132the noderef of the local node. The value is initialised by a call
125to C<become_public> or C<become_slave>, after which all local port 133to C<become_public> or C<become_slave>, after which all local port
126identifiers become invalid. 134identifiers become invalid.
127 135
128=item $noderef = node_of $portid 136=item $noderef = node_of $port
129 137
130Extracts and returns the noderef from a portid or a noderef. 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";
131 203
132=item $cv = resolve_node $noderef 204=item $cv = resolve_node $noderef
133 205
134Takes an unresolved node reference that may contain hostnames and 206Takes an unresolved node reference that may contain hostnames and
135abbreviated IDs, resolves all of them and returns a resolved node 207abbreviated IDs, resolves all of them and returns a resolved node
167 239
168Due to some quirks in how perl exports variables, it is impossible to 240Due to some quirks in how perl exports variables, it is impossible to
169just export C<$SELF>, all the symbols called C<SELF> are exported by this 241just export C<$SELF>, all the symbols called C<SELF> are exported by this
170module, but only C<$SELF> is currently used. 242module, but only C<$SELF> is currently used.
171 243
172=item snd $portid, type => @data 244=item snd $port, type => @data
173 245
174=item snd $portid, @msg 246=item snd $port, @msg
175 247
176Send 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
177a 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
178stringifies a sa port ID (such as a port object :). 250stringifies a sa port ID (such as a port object :).
179 251
189JSON is used, then only strings, numbers and arrays and hashes consisting 261JSON is used, then only strings, numbers and arrays and hashes consisting
190of those are allowed (no objects). When Storable is used, then anything 262of those are allowed (no objects). When Storable is used, then anything
191that Storable can serialise and deserialise is allowed, and for the local 263that Storable can serialise and deserialise is allowed, and for the local
192node, anything can be passed. 264node, anything can be passed.
193 265
194=item kil $portid[, @reason]
195
196Kill the specified port with the given C<@reason>.
197
198If no C<@reason> is specified, then the port is killed "normally" (linked
199ports will not be kileld, or even notified).
200
201Otherwise, linked ports get killed with the same reason (second form of
202C<mon>, see below).
203
204Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
205will be reported as reason C<< die => $@ >>.
206
207Transport/communication errors are reported as C<< transport_error =>
208$message >>.
209
210=item $guard = mon $portid, $cb->(@reason)
211
212=item $guard = mon $portid, $otherport
213
214=item $guard = mon $portid, $otherport, @msg
215
216Monitor the given port and do something when the port is killed.
217
218In the first form, the callback is simply called with any number
219of C<@reason> elements (no @reason means that the port was deleted
220"normally"). Note also that I<< the callback B<must> never die >>, so use
221C<eval> if unsure.
222
223In the second form, the other port will be C<kil>'ed with C<@reason>, iff
224a @reason was specified, i.e. on "normal" kils nothing happens, while
225under all other conditions, the other port is killed with the same reason.
226
227In the last form, a message of the form C<@msg, @reason> will be C<snd>.
228
229Example: call a given callback when C<$port> is killed.
230
231 mon $port, sub { warn "port died because of <@_>\n" };
232
233Example: kill ourselves when C<$port> is killed abnormally.
234
235 mon $port, $self;
236
237Example: send us a restart message another C<$port> is killed.
238
239 mon $port, $self => "restart";
240
241=cut
242
243sub mon {
244 my ($noderef, $port) = split /#/, shift, 2;
245
246 my $node = $NODE{$noderef} || add_node $noderef;
247
248 my $cb = shift;
249
250 unless (ref $cb) {
251 if (@_) {
252 # send a kill info message
253 my (@msg) = ($cb, @_);
254 $cb = sub { snd @msg, @_ };
255 } else {
256 # simply kill other port
257 my $port = $cb;
258 $cb = sub { kil $port, @_ if @_ };
259 }
260 }
261
262 $node->monitor ($port, $cb);
263
264 defined wantarray
265 and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }
266}
267
268=item $guard = mon_guard $port, $ref, $ref...
269
270Monitors the given C<$port> and keeps the passed references. When the port
271is killed, the references will be freed.
272
273Optionally returns a guard that will stop the monitoring.
274
275This function is useful when you create e.g. timers or other watchers and
276want to free them when the port gets killed:
277
278 $port->rcv (start => sub {
279 my $timer; $timer = mon_guard $port, AE::timer 1, 1, sub {
280 undef $timer if 0.9 < rand;
281 });
282 });
283
284=cut
285
286sub mon_guard {
287 my ($port, @refs) = @_;
288
289 mon $port, sub { 0 && @refs }
290}
291
292=item lnk $port1, $port2
293
294Link two ports. This is simply a shorthand for:
295
296 mon $port1, $port2;
297 mon $port2, $port1;
298
299It means that if either one is killed abnormally, the other one gets
300killed as well.
301
302=item $local_port = port 266=item $local_port = port
303 267
304Create a new local port object that can be used either as a pattern 268Create a new local port object that can be used either as a pattern
305matching port ("full port") or a single-callback port ("miniport"), 269matching port ("full port") or a single-callback port ("miniport"),
306depending on how C<rcv> callbacks are bound to the object. 270depending on how C<rcv> callbacks are bound to the object.
307 271
308=item $portid = port { my @msg = @_; $finished } 272=item $port = port { my @msg = @_; $finished }
309 273
310Creates a "mini port", that is, a very lightweight port without any 274Creates a "miniport", that is, a very lightweight port without any pattern
311pattern matching behind it, and returns its ID. 275matching behind it, and returns its ID. Semantically the same as creating
276a port and calling C<rcv $port, $callback> on it.
312 277
313The block will be called for every message received on the port. When the 278The block will be called for every message received on the port. When the
314callback returns a true value its job is considered "done" and the port 279callback returns a true value its job is considered "done" and the port
315will be destroyed. Otherwise it will stay alive. 280will be destroyed. Otherwise it will stay alive.
316 281
323 snd $otherport, reply => $port; 288 snd $otherport, reply => $port;
324 }; 289 };
325 290
326=cut 291=cut
327 292
293sub rcv($@);
294
328sub port(;&) { 295sub port(;&) {
329 my $id = "$UNIQ." . $ID++; 296 my $id = "$UNIQ." . $ID++;
330 my $port = "$NODE#$id"; 297 my $port = "$NODE#$id";
331 298
332 if (@_) { 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) {
333 my $cb = shift; 388 my $cb = shift;
389 delete $PORT_DATA{$portid};
334 $PORT{$id} = sub { 390 $PORT{$portid} = sub {
335 local $SELF = $port; 391 local $SELF = $port;
336 eval { 392 eval {
337 &$cb 393 &$cb
338 and kil $id; 394 and kil $port;
339 }; 395 };
340 _self_die if $@; 396 _self_die if $@;
341 }; 397 };
342 } else { 398 } else {
399 my $self = $PORT_DATA{$portid} ||= do {
343 my $self = bless { 400 my $self = bless {
344 id => "$NODE#$id", 401 id => $port,
345 }, "AnyEvent::MP::Port"; 402 }, "AnyEvent::MP::Port";
346 403
347 $PORT_DATA{$id} = $self;
348 $PORT{$id} = sub { 404 $PORT{$portid} = sub {
349 local $SELF = $port; 405 local $SELF = $port;
350 406
351 eval { 407 eval {
352 for (@{ $self->{rc0}{$_[0]} }) { 408 for (@{ $self->{rc0}{$_[0]} }) {
353 $_ && &{$_->[0]} 409 $_ && &{$_->[0]}
354 && undef $_; 410 && undef $_;
355 } 411 }
356 412
357 for (@{ $self->{rcv}{$_[0]} }) { 413 for (@{ $self->{rcv}{$_[0]} }) {
358 $_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1] 414 $_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1]
359 && &{$_->[0]} 415 && &{$_->[0]}
360 && undef $_; 416 && undef $_;
361 } 417 }
362 418
363 for (@{ $self->{any} }) { 419 for (@{ $self->{any} }) {
364 $_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1] 420 $_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1]
365 && &{$_->[0]} 421 && &{$_->[0]}
366 && undef $_; 422 && undef $_;
423 }
367 } 424 };
425 _self_die if $@;
368 }; 426 };
369 _self_die if $@; 427
428 $self
370 }; 429 };
371 }
372 430
373 $port
374}
375
376=item reg $portid, $name
377
378Registers the given port under the name C<$name>. If the name already
379exists it is replaced.
380
381A port can only be registered under one well known name.
382
383A port automatically becomes unregistered when it is killed.
384
385=cut
386
387sub reg(@) {
388 my ($portid, $name) = @_;
389
390 $REG{$name} = $portid;
391}
392
393=item rcv $portid, $callback->(@msg)
394
395Replaces the callback on the specified miniport (or newly created port
396object, see C<port>). Full ports are configured with the following calls:
397
398=item rcv $portid, tagstring => $callback->(@msg), ...
399
400=item rcv $portid, $smartmatch => $callback->(@msg), ...
401
402=item rcv $portid, [$smartmatch...] => $callback->(@msg), ...
403
404Register callbacks to be called on matching messages on the given port.
405
406The callback has to return a true value when its work is done, after
407which is will be removed, or a false value in which case it will stay
408registered.
409
410The global C<$SELF> (exported by this module) contains C<$portid> while
411executing the callback.
412
413Runtime errors wdurign callback execution will result in the port being
414C<kil>ed.
415
416If the match is an array reference, then it will be matched against the
417first elements of the message, otherwise only the first element is being
418matched.
419
420Any element in the match that is specified as C<_any_> (a function
421exported by this module) matches any single element of the message.
422
423While not required, it is highly recommended that the first matching
424element is a string identifying the message. The one-string-only match is
425also the most efficient match (by far).
426
427=cut
428
429sub rcv($@) {
430 my $portid = shift;
431 my ($noderef, $port) = split /#/, $port, 2;
432
433 ($NODE{$noderef} || add_node $noderef) == $NODE{""}
434 or Carp::croak "$noderef#$port: rcv can only be called on local ports, caught";
435
436 my $self = $PORT_DATA{$port}
437 or Carp::croak "$noderef#$port: rcv can only be called on message matching ports, caught";
438
439 "AnyEvent::MP::Port" eq ref $self 431 "AnyEvent::MP::Port" eq ref $self
440 or Carp::croak "$noderef#$port: rcv can only be called on message matching ports, caught"; 432 or Carp::croak "$port: rcv can only be called on message matching ports, caught";
441 433
442 while (@_) { 434 while (@_) {
443 my ($match, $cb) = splice @_, 0, 2; 435 my ($match, $cb) = splice @_, 0, 2;
444 436
445 if (!ref $match) { 437 if (!ref $match) {
446 push @{ $self->{rc0}{$match} }, [$cb]; 438 push @{ $self->{rc0}{$match} }, [$cb];
447 } elsif (("ARRAY" eq ref $match && !ref $match->[0])) { 439 } elsif (("ARRAY" eq ref $match && !ref $match->[0])) {
448 my ($type, @match) = @$match; 440 my ($type, @match) = @$match;
449 @match 441 @match
450 ? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match] 442 ? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match]
451 : push @{ $self->{rc0}{$match->[0]} }, [$cb]; 443 : push @{ $self->{rc0}{$match->[0]} }, [$cb];
452 } else { 444 } else {
453 push @{ $self->{any} }, [$cb, $match]; 445 push @{ $self->{any} }, [$cb, $match];
446 }
454 } 447 }
455 } 448 }
456 449
457 $portid 450 $port
458} 451}
459 452
460=item $closure = psub { BLOCK } 453=item $closure = psub { BLOCK }
461 454
462Remembers C<$SELF> and creates a closure out of the BLOCK. When the 455Remembers C<$SELF> and creates a closure out of the BLOCK. When the
493 $res 486 $res
494 } 487 }
495 } 488 }
496} 489}
497 490
498=back 491=item $guard = mon $port, $cb->(@reason)
499 492
500=head1 FUNCTIONS FOR NODES 493=item $guard = mon $port, $rcvport
501 494
502=over 4 495=item $guard = mon $port
503 496
504=item become_public $noderef 497=item $guard = mon $port, $rcvport, @msg
505 498
506Tells the node to become a public node, i.e. reachable from other nodes. 499Monitor the given port and do something when the port is killed, and
500optionally return a guard that can be used to stop monitoring again.
507 501
508The first argument is the (unresolved) node reference of the local node 502In the first form (callback), the callback is simply called with any
509(if missing then the empty string is used). 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.
510 506
511It is quite common to not specify anything, in which case the local node 507In the second form (another port given), the other port (C<$rcvport)
512tries to listen on the default port, or to only specify a port number, in 508will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on
513which case AnyEvent::MP tries to guess the local addresses. 509"normal" kils nothing happens, while under all other conditions, the other
510port is killed with the same reason.
514 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";
529
515=cut 530=cut
531
532sub mon {
533 my ($noderef, $port) = split /#/, shift, 2;
534
535 my $node = $NODE{$noderef} || add_node $noderef;
536
537 my $cb = @_ ? $_[0] : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,';
538
539 unless (ref $cb) {
540 if (@_) {
541 # send a kill info message
542 my (@msg) = @_;
543 $cb = sub { snd @msg, @_ };
544 } else {
545 # simply kill other port
546 my $port = $cb;
547 $cb = sub { kil $port, @_ if @_ };
548 }
549 }
550
551 $node->monitor ($port, $cb);
552
553 defined wantarray
554 and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }
555}
556
557=item $guard = mon_guard $port, $ref, $ref...
558
559Monitors the given C<$port> and keeps the passed references. When the port
560is killed, the references will be freed.
561
562Optionally returns a guard that will stop the monitoring.
563
564This function is useful when you create e.g. timers or other watchers and
565want to free them when the port gets killed:
566
567 $port->rcv (start => sub {
568 my $timer; $timer = mon_guard $port, AE::timer 1, 1, sub {
569 undef $timer if 0.9 < rand;
570 });
571 });
572
573=cut
574
575sub mon_guard {
576 my ($port, @refs) = @_;
577
578 #TODO: mon-less form?
579
580 mon $port, sub { 0 && @refs }
581}
582
583=item lnk $port1, $port2
584
585=item lnk $otherport
586
587Link two ports. This is simply a shorthand for:
588
589 mon $port1, $port2;
590 mon $port2, $port1;
591
592It means that if either one is killed abnormally, the other one gets
593killed as well.
594
595The one-argument form assumes that one port is C<$SELF>.
596
597=cut
598
599sub lnk {
600 my $port1 = shift;
601 my $port2 = @_ ? shift : $SELF || Carp::croak 'lnk: called with one argument only, but $SELF not set,';
602
603 mon $port1, $port2;
604 mon $port2, $port1;
605}
606
607=item kil $port[, @reason]
608
609Kill the specified port with the given C<@reason>.
610
611If no C<@reason> is specified, then the port is killed "normally" (linked
612ports will not be kileld, or even notified).
613
614Otherwise, linked ports get killed with the same reason (second form of
615C<mon>, see below).
616
617Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
618will be reported as reason C<< die => $@ >>.
619
620Transport/communication errors are reported as C<< transport_error =>
621$message >>.
516 622
517=back 623=back
518 624
519=head1 NODE MESSAGES 625=head1 NODE MESSAGES
520 626
562 668
563=back 669=back
564 670
565=head1 AnyEvent::MP vs. Distributed Erlang 671=head1 AnyEvent::MP vs. Distributed Erlang
566 672
567AnyEvent::MP got lots of its ideas from distributed erlang (erlang node 673AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
568== aemp node, erlang process == aemp port), so many of the documents and 674== aemp node, Erlang process == aemp port), so many of the documents and
569programming techniques employed by erlang apply to AnyEvent::MP. Here is a 675programming techniques employed by Erlang apply to AnyEvent::MP. Here is a
570sample: 676sample:
571 677
572 http://www.erlang.se/doc/programming_rules.shtml 678 http://www.Erlang.se/doc/programming_rules.shtml
573 http://erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4 679 http://Erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4
574 http://erlang.org/download/erlang-book-part1.pdf # chapters 5 and 6 680 http://Erlang.org/download/Erlang-book-part1.pdf # chapters 5 and 6
575 http://erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5 681 http://Erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5
576 682
577Despite the similarities, there are also some important differences: 683Despite the similarities, there are also some important differences:
578 684
579=over 4 685=over 4
580 686
591 697
592Erlang uses processes that selctively receive messages, and therefore 698Erlang uses processes that selctively receive messages, and therefore
593needs a queue. AEMP is event based, queuing messages would serve no useful 699needs a queue. AEMP is event based, queuing messages would serve no useful
594purpose. 700purpose.
595 701
596(But see L<Coro::MP> for a more erlang-like process model on top of AEMP). 702(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).
597 703
598=item * Erlang sends are synchronous, AEMP sends are asynchronous. 704=item * Erlang sends are synchronous, AEMP sends are asynchronous.
599 705
600Sending messages in erlang is synchronous and blocks the process. AEMP 706Sending messages in Erlang is synchronous and blocks the process. AEMP
601sends are immediate, connection establishment is handled in the 707sends are immediate, connection establishment is handled in the
602background. 708background.
603 709
604=item * Erlang can silently lose messages, AEMP cannot. 710=item * Erlang can silently lose messages, AEMP cannot.
605 711
608and c, and the other side only receives messages a and c). 714and c, and the other side only receives messages a and c).
609 715
610AEMP guarantees correct ordering, and the guarantee that there are no 716AEMP guarantees correct ordering, and the guarantee that there are no
611holes in the message sequence. 717holes in the message sequence.
612 718
613=item * In erlang, processes can be declared dead and later be found to be 719=item * In Erlang, processes can be declared dead and later be found to be
614alive. 720alive.
615 721
616In erlang it can happen that a monitored process is declared dead and 722In Erlang it can happen that a monitored process is declared dead and
617linked processes get killed, but later it turns out that the process is 723linked processes get killed, but later it turns out that the process is
618still alive - and can receive messages. 724still alive - and can receive messages.
619 725
620In AEMP, when port monitoring detects a port as dead, then that port will 726In AEMP, when port monitoring detects a port as dead, then that port will
621eventually be killed - it cannot happen that a node detects a port as dead 727eventually be killed - it cannot happen that a node detects a port as dead
622and then later sends messages to it, finding it is still alive. 728and then later sends messages to it, finding it is still alive.
623 729
624=item * Erlang can send messages to the wrong port, AEMP does not. 730=item * Erlang can send messages to the wrong port, AEMP does not.
625 731
626In erlang it is quite possible that a node that restarts reuses a process 732In Erlang it is quite possible that a node that restarts reuses a process
627ID known to other nodes for a completely different process, causing 733ID known to other nodes for a completely different process, causing
628messages destined for that process to end up in an unrelated process. 734messages destined for that process to end up in an unrelated process.
629 735
630AEMP never reuses port IDs, so old messages or old port IDs floating 736AEMP never reuses port IDs, so old messages or old port IDs floating
631around in the network will not be sent to an unrelated port. 737around in the network will not be sent to an unrelated port.
637securely authenticate nodes. 743securely authenticate nodes.
638 744
639=item * The AEMP protocol is optimised for both text-based and binary 745=item * The AEMP protocol is optimised for both text-based and binary
640communications. 746communications.
641 747
642The AEMP protocol, unlike the erlang protocol, supports both 748The AEMP protocol, unlike the Erlang protocol, supports both
643language-independent text-only protocols (good for debugging) and binary, 749language-independent text-only protocols (good for debugging) and binary,
644language-specific serialisers (e.g. Storable). 750language-specific serialisers (e.g. Storable).
645 751
646It has also been carefully designed to be implementable in other languages 752It has also been carefully designed to be implementable in other languages
647with a minimum of work while gracefully degrading fucntionality to make the 753with a minimum of work while gracefully degrading fucntionality to make the
648protocol simple. 754protocol simple.
649 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
650=back 771=back
651 772
652=head1 SEE ALSO 773=head1 SEE ALSO
653 774
654L<AnyEvent>. 775L<AnyEvent>.

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines