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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines