ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent-MP/MP.pm
(Generate patch)

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.24 by root, Tue Aug 4 20:00:00 2009 UTC vs.
Revision 1.34 by root, Wed Aug 5 23:50:46 2009 UTC

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines