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

Comparing cvsroot/AnyEvent-MP/MP.pm (file contents):
Revision 1.32 by root, Wed Aug 5 19:58:46 2009 UTC vs.
Revision 1.50 by root, Fri Aug 14 14:01:05 2009 UTC

8 8
9 $NODE # contains this node's noderef 9 $NODE # contains this node's noderef
10 NODE # returns this node's noderef 10 NODE # returns this node's noderef
11 NODE $port # returns the noderef of the port 11 NODE $port # returns the noderef of the port
12 12
13 $SELF # receiving/own port id in rcv callbacks
14
15 # initialise the node so it can send/receive messages
16 initialise_node; # -OR-
17 initialise_node "localhost:4040"; # -OR-
18 initialise_node "slave/", "localhost:4040"
19
20 # ports are message endpoints
21
22 # sending messages
13 snd $port, type => data...; 23 snd $port, type => data...;
24 snd $port, @msg;
25 snd @msg_with_first_element_being_a_port;
14 26
15 $SELF # receiving/own port id in rcv callbacks 27 # creating/using ports, the simple way
28 my $somple_port = port { my @msg = @_; 0 };
16 29
17 rcv $port, smartmatch => $cb->($port, @msg); 30 # creating/using ports, type matching
18 31 my $port = port;
19 # examples:
20 rcv $port2, ping => sub { snd $_[0], "pong"; 0 }; 32 rcv $port, ping => sub { snd $_[0], "pong"; 0 };
21 rcv $port1, pong => sub { warn "pong received\n" }; 33 rcv $port, pong => sub { warn "pong received\n"; 0 };
22 snd $port2, ping => $port1;
23 34
24 # more, smarter, matches (_any_ is exported by this module) 35 # create a port on another node
25 rcv $port, [child_died => $pid] => sub { ... 36 my $port = spawn $node, $initfunc, @initdata;
26 rcv $port, [_any_, _any_, 3] => sub { .. $_[2] is 3 37
38 # monitoring
39 mon $port, $cb->(@msg) # callback is invoked on death
40 mon $port, $otherport # kill otherport on abnormal death
41 mon $port, $otherport, @msg # send message on death
42
43=head1 CURRENT STATUS
44
45 AnyEvent::MP - stable API, should work
46 AnyEvent::MP::Intro - outdated
47 AnyEvent::MP::Kernel - WIP
48 AnyEvent::MP::Transport - mostly stable
49
50 stay tuned.
27 51
28=head1 DESCRIPTION 52=head1 DESCRIPTION
29 53
30This module (-family) implements a simple message passing framework. 54This module (-family) implements a simple message passing framework.
31 55
35For an introduction to this module family, see the L<AnyEvent::MP::Intro> 59For an introduction to this module family, see the L<AnyEvent::MP::Intro>
36manual page. 60manual page.
37 61
38At the moment, this module family is severly broken and underdocumented, 62At the moment, this module family is severly broken and underdocumented,
39so do not use. This was uploaded mainly to reserve the CPAN namespace - 63so do not use. This was uploaded mainly to reserve the CPAN namespace -
40stay tuned! The basic API should be finished, however. 64stay tuned!
41 65
42=head1 CONCEPTS 66=head1 CONCEPTS
43 67
44=over 4 68=over 4
45 69
90 114
91=cut 115=cut
92 116
93package AnyEvent::MP; 117package AnyEvent::MP;
94 118
95use AnyEvent::MP::Base; 119use AnyEvent::MP::Kernel;
96 120
97use common::sense; 121use common::sense;
98 122
99use Carp (); 123use Carp ();
100 124
101use AE (); 125use AE ();
102 126
103use base "Exporter"; 127use base "Exporter";
104 128
105our $VERSION = '0.1'; 129our $VERSION = $AnyEvent::MP::Kernel::VERSION;
130
106our @EXPORT = qw( 131our @EXPORT = qw(
107 NODE $NODE *SELF node_of _any_ 132 NODE $NODE *SELF node_of _any_
108 resolve_node initialise_node 133 resolve_node initialise_node
109 snd rcv mon kil reg psub 134 snd rcv mon kil reg psub spawn
110 port 135 port
111); 136);
112 137
113our $SELF; 138our $SELF;
114 139
123The C<NODE> function returns, and the C<$NODE> variable contains 148The C<NODE> function returns, and the C<$NODE> variable contains
124the noderef of the local node. The value is initialised by a call 149the 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 150to C<become_public> or C<become_slave>, after which all local port
126identifiers become invalid. 151identifiers become invalid.
127 152
128=item $noderef = node_of $portid 153=item $noderef = node_of $port
129 154
130Extracts and returns the noderef from a portid or a noderef. 155Extracts and returns the noderef from a portid or a noderef.
156
157=item initialise_node $noderef, $seednode, $seednode...
158
159=item initialise_node "slave/", $master, $master...
160
161Before a node can talk to other nodes on the network it has to initialise
162itself - the minimum a node needs to know is it's own name, and optionally
163it should know the noderefs of some other nodes in the network.
164
165This function initialises a node - it must be called exactly once (or
166never) before calling other AnyEvent::MP functions.
167
168All arguments (optionally except for the first) are noderefs, which can be
169either resolved or unresolved.
170
171The first argument will be looked up in the configuration database first
172(if it is C<undef> then the current nodename will be used instead) to find
173the relevant configuration profile (see L<aemp>). If none is found then
174the default configuration is used. The configuration supplies additional
175seed/master nodes and can override the actual noderef.
176
177There are two types of networked nodes, public nodes and slave nodes:
178
179=over 4
180
181=item public nodes
182
183For public nodes, C<$noderef> (supplied either directly to
184C<initialise_node> or indirectly via a profile or the nodename) must be a
185noderef (possibly unresolved, in which case it will be resolved).
186
187After resolving, the node will bind itself on all endpoints and try to
188connect to all additional C<$seednodes> that are specified. Seednodes are
189optional and can be used to quickly bootstrap the node into an existing
190network.
191
192=item slave nodes
193
194When the C<$noderef> (either as given or overriden by the config file)
195is the special string C<slave/>, then the node will become a slave
196node. Slave nodes cannot be contacted from outside and will route most of
197their traffic to the master node that they attach to.
198
199At least one additional noderef is required (either by specifying it
200directly or because it is part of the configuration profile): The node
201will try to connect to all of them and will become a slave attached to the
202first node it can successfully connect to.
203
204=back
205
206This function will block until all nodes have been resolved and, for slave
207nodes, until it has successfully established a connection to a master
208server.
209
210Example: become a public node listening on the guessed noderef, or the one
211specified via C<aemp> for the current node. This should be the most common
212form of invocation for "daemon"-type nodes.
213
214 initialise_node;
215
216Example: become a slave node to any of the the seednodes specified via
217C<aemp>. This form is often used for commandline clients.
218
219 initialise_node "slave/";
220
221Example: become a slave node to any of the specified master servers. This
222form is also often used for commandline clients.
223
224 initialise_node "slave/", "master1", "192.168.13.17", "mp.example.net";
225
226Example: become a public node, and try to contact some well-known master
227servers to become part of the network.
228
229 initialise_node undef, "master1", "master2";
230
231Example: become a public node listening on port C<4041>.
232
233 initialise_node 4041;
234
235Example: become a public node, only visible on localhost port 4044.
236
237 initialise_node "localhost:4044";
131 238
132=item $cv = resolve_node $noderef 239=item $cv = resolve_node $noderef
133 240
134Takes an unresolved node reference that may contain hostnames and 241Takes an unresolved node reference that may contain hostnames and
135abbreviated IDs, resolves all of them and returns a resolved node 242abbreviated IDs, resolves all of them and returns a resolved node
167 274
168Due to some quirks in how perl exports variables, it is impossible to 275Due 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 276just export C<$SELF>, all the symbols called C<SELF> are exported by this
170module, but only C<$SELF> is currently used. 277module, but only C<$SELF> is currently used.
171 278
172=item snd $portid, type => @data 279=item snd $port, type => @data
173 280
174=item snd $portid, @msg 281=item snd $port, @msg
175 282
176Send the given message to the given port ID, which can identify either 283Send 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 284a local or a remote port, and can be either a string or soemthignt hat
178stringifies a sa port ID (such as a port object :). 285stringifies a sa port ID (such as a port object :).
179 286
191that Storable can serialise and deserialise is allowed, and for the local 298that Storable can serialise and deserialise is allowed, and for the local
192node, anything can be passed. 299node, anything can be passed.
193 300
194=item $local_port = port 301=item $local_port = port
195 302
196Create a new local port object that can be used either as a pattern 303Create a new local port object and returns its port ID. Initially it has
197matching port ("full port") or a single-callback port ("miniport"), 304no callbacks set and will throw an error when it receives messages.
198depending on how C<rcv> callbacks are bound to the object.
199 305
200=item $portid = port { my @msg = @_; $finished } 306=item $local_port = port { my @msg = @_ }
201 307
202Creates a "mini port", that is, a very lightweight port without any 308Creates a new local port, and returns its ID. Semantically the same as
203pattern matching behind it, and returns its ID. 309creating a port and calling C<rcv $port, $callback> on it.
204 310
205The block will be called for every message received on the port. When the 311The block will be called for every message received on the port, with the
206callback returns a true value its job is considered "done" and the port 312global variable C<$SELF> set to the port ID. Runtime errors will cause the
207will be destroyed. Otherwise it will stay alive. 313port to be C<kil>ed. The message will be passed as-is, no extra argument
314(i.e. no port ID) will be passed to the callback.
208 315
209The message will be passed as-is, no extra argument (i.e. no port id) will 316If you want to stop/destroy the port, simply C<kil> it:
210be passed to the callback.
211 317
212If you need the local port id in the callback, this works nicely: 318 my $port = port {
213 319 my @msg = @_;
214 my $port; $port = port { 320 ...
215 snd $otherport, reply => $port; 321 kil $SELF;
216 }; 322 };
217 323
218=cut 324=cut
325
326sub rcv($@);
327
328sub _kilme {
329 die "received message on port without callback";
330}
219 331
220sub port(;&) { 332sub port(;&) {
221 my $id = "$UNIQ." . $ID++; 333 my $id = "$UNIQ." . $ID++;
222 my $port = "$NODE#$id"; 334 my $port = "$NODE#$id";
223 335
224 if (@_) { 336 rcv $port, shift || \&_kilme;
225 my $cb = shift;
226 $PORT{$id} = sub {
227 local $SELF = $port;
228 eval {
229 &$cb
230 and kil $id;
231 };
232 _self_die if $@;
233 };
234 } else {
235 my $self = bless {
236 id => "$NODE#$id",
237 }, "AnyEvent::MP::Port";
238
239 $PORT_DATA{$id} = $self;
240 $PORT{$id} = sub {
241 local $SELF = $port;
242
243 eval {
244 for (@{ $self->{rc0}{$_[0]} }) {
245 $_ && &{$_->[0]}
246 && undef $_;
247 }
248
249 for (@{ $self->{rcv}{$_[0]} }) {
250 $_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1]
251 && &{$_->[0]}
252 && undef $_;
253 }
254
255 for (@{ $self->{any} }) {
256 $_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1]
257 && &{$_->[0]}
258 && undef $_;
259 }
260 };
261 _self_die if $@;
262 };
263 }
264 337
265 $port 338 $port
266} 339}
267 340
268=item reg $portid, $name
269
270Registers the given port under the name C<$name>. If the name already
271exists it is replaced.
272
273A port can only be registered under one well known name.
274
275A port automatically becomes unregistered when it is killed.
276
277=cut
278
279sub reg(@) {
280 my ($portid, $name) = @_;
281
282 $REG{$name} = $portid;
283}
284
285=item rcv $portid, $callback->(@msg) 341=item rcv $local_port, $callback->(@msg)
286 342
287Replaces the callback on the specified miniport (or newly created port 343Replaces the default callback on the specified port. There is no way to
288object, see C<port>). Full ports are configured with the following calls: 344remove the default callback: use C<sub { }> to disable it, or better
345C<kil> the port when it is no longer needed.
289 346
290=item rcv $portid, tagstring => $callback->(@msg), ...
291
292=item rcv $portid, $smartmatch => $callback->(@msg), ...
293
294=item rcv $portid, [$smartmatch...] => $callback->(@msg), ...
295
296Register callbacks to be called on matching messages on the given full
297port (or newly created port).
298
299The callback has to return a true value when its work is done, after
300which is will be removed, or a false value in which case it will stay
301registered.
302
303The global C<$SELF> (exported by this module) contains C<$portid> while 347The global C<$SELF> (exported by this module) contains C<$port> while
304executing the callback. 348executing the callback. Runtime errors during callback execution will
349result in the port being C<kil>ed.
305 350
306Runtime errors wdurign callback execution will result in the port being 351The default callback received all messages not matched by a more specific
307C<kil>ed. 352C<tag> match.
308 353
309If the match is an array reference, then it will be matched against the 354=item rcv $local_port, tag => $callback->(@msg_without_tag), ...
310first elements of the message, otherwise only the first element is being
311matched.
312 355
313Any element in the match that is specified as C<_any_> (a function 356Register callbacks to be called on messages starting with the given tag on
314exported by this module) matches any single element of the message. 357the given port (and return the port), or unregister it (when C<$callback>
358is C<$undef>).
315 359
316While not required, it is highly recommended that the first matching 360The original message will be passed to the callback, after the first
317element is a string identifying the message. The one-string-only match is 361element (the tag) has been removed. The callback will use the same
318also the most efficient match (by far). 362environment as the default callback (see above).
363
364Example: create a port and bind receivers on it in one go.
365
366 my $port = rcv port,
367 msg1 => sub { ... },
368 msg2 => sub { ... },
369 ;
370
371Example: create a port, bind receivers and send it in a message elsewhere
372in one go:
373
374 snd $otherport, reply =>
375 rcv port,
376 msg1 => sub { ... },
377 ...
378 ;
319 379
320=cut 380=cut
321 381
322sub rcv($@) { 382sub rcv($@) {
323 my $portid = shift; 383 my $port = shift;
324 my ($noderef, $port) = split /#/, $port, 2; 384 my ($noderef, $portid) = split /#/, $port, 2;
325 385
326 ($NODE{$noderef} || add_node $noderef) == $NODE{""} 386 ($NODE{$noderef} || add_node $noderef) == $NODE{""}
327 or Carp::croak "$noderef#$port: rcv can only be called on local ports, caught"; 387 or Carp::croak "$port: rcv can only be called on local ports, caught";
328
329 my $self = $PORT_DATA{$port}
330 or Carp::croak "$noderef#$port: rcv can only be called on message matching ports, caught";
331
332 "AnyEvent::MP::Port" eq ref $self
333 or Carp::croak "$noderef#$port: rcv can only be called on message matching ports, caught";
334 388
335 while (@_) { 389 while (@_) {
336 my ($match, $cb) = splice @_, 0, 2;
337
338 if (!ref $match) { 390 if (ref $_[0]) {
339 push @{ $self->{rc0}{$match} }, [$cb]; 391 if (my $self = $PORT_DATA{$portid}) {
340 } elsif (("ARRAY" eq ref $match && !ref $match->[0])) { 392 "AnyEvent::MP::Port" eq ref $self
341 my ($type, @match) = @$match; 393 or Carp::croak "$port: rcv can only be called on message matching ports, caught";
342 @match 394
343 ? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match] 395 $self->[2] = shift;
344 : push @{ $self->{rc0}{$match->[0]} }, [$cb];
345 } else { 396 } else {
346 push @{ $self->{any} }, [$cb, $match]; 397 my $cb = shift;
398 $PORT{$portid} = sub {
399 local $SELF = $port;
400 eval { &$cb }; _self_die if $@;
401 };
402 }
403 } elsif (defined $_[0]) {
404 my $self = $PORT_DATA{$portid} ||= do {
405 my $self = bless [$PORT{$port} || sub { }, { }, $port], "AnyEvent::MP::Port";
406
407 $PORT{$portid} = sub {
408 local $SELF = $port;
409
410 if (my $cb = $self->[1]{$_[0]}) {
411 shift;
412 eval { &$cb }; _self_die if $@;
413 } else {
414 &{ $self->[0] };
415 }
416 };
417
418 $self
419 };
420
421 "AnyEvent::MP::Port" eq ref $self
422 or Carp::croak "$port: rcv can only be called on message matching ports, caught";
423
424 my ($tag, $cb) = splice @_, 0, 2;
425
426 if (defined $cb) {
427 $self->[1]{$tag} = $cb;
428 } else {
429 delete $self->[1]{$tag};
430 }
347 } 431 }
348 } 432 }
349 433
350 $portid 434 $port
351} 435}
352 436
353=item $closure = psub { BLOCK } 437=item $closure = psub { BLOCK }
354 438
355Remembers C<$SELF> and creates a closure out of the BLOCK. When the 439Remembers C<$SELF> and creates a closure out of the BLOCK. When the
386 $res 470 $res
387 } 471 }
388 } 472 }
389} 473}
390 474
391=item $guard = mon $portid, $cb->(@reason) 475=item $guard = mon $port, $cb->(@reason)
392 476
393=item $guard = mon $portid, $otherport 477=item $guard = mon $port, $rcvport
394 478
479=item $guard = mon $port
480
395=item $guard = mon $portid, $otherport, @msg 481=item $guard = mon $port, $rcvport, @msg
396 482
397Monitor the given port and do something when the port is killed. 483Monitor the given port and do something when the port is killed or
484messages to it were lost, and optionally return a guard that can be used
485to stop monitoring again.
398 486
487C<mon> effectively guarantees that, in the absence of hardware failures,
488that after starting the monitor, either all messages sent to the port
489will arrive, or the monitoring action will be invoked after possible
490message loss has been detected. No messages will be lost "in between"
491(after the first lost message no further messages will be received by the
492port). After the monitoring action was invoked, further messages might get
493delivered again.
494
399In the first form, the callback is simply called with any number 495In the first form (callback), the callback is simply called with any
400of C<@reason> elements (no @reason means that the port was deleted 496number of C<@reason> elements (no @reason means that the port was deleted
401"normally"). Note also that I<< the callback B<must> never die >>, so use 497"normally"). Note also that I<< the callback B<must> never die >>, so use
402C<eval> if unsure. 498C<eval> if unsure.
403 499
404In the second form, the other port will be C<kil>'ed with C<@reason>, iff 500In the second form (another port given), the other port (C<$rcvport>)
405a @reason was specified, i.e. on "normal" kils nothing happens, while 501will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on
406under all other conditions, the other port is killed with the same reason. 502"normal" kils nothing happens, while under all other conditions, the other
503port is killed with the same reason.
407 504
505The third form (kill self) is the same as the second form, except that
506C<$rvport> defaults to C<$SELF>.
507
408In the last form, a message of the form C<@msg, @reason> will be C<snd>. 508In the last form (message), a message of the form C<@msg, @reason> will be
509C<snd>.
510
511As a rule of thumb, monitoring requests should always monitor a port from
512a local port (or callback). The reason is that kill messages might get
513lost, just like any other message. Another less obvious reason is that
514even monitoring requests can get lost (for exmaple, when the connection
515to the other node goes down permanently). When monitoring a port locally
516these problems do not exist.
409 517
410Example: call a given callback when C<$port> is killed. 518Example: call a given callback when C<$port> is killed.
411 519
412 mon $port, sub { warn "port died because of <@_>\n" }; 520 mon $port, sub { warn "port died because of <@_>\n" };
413 521
414Example: kill ourselves when C<$port> is killed abnormally. 522Example: kill ourselves when C<$port> is killed abnormally.
415 523
416 mon $port, $self; 524 mon $port;
417 525
418Example: send us a restart message another C<$port> is killed. 526Example: send us a restart message when another C<$port> is killed.
419 527
420 mon $port, $self => "restart"; 528 mon $port, $self => "restart";
421 529
422=cut 530=cut
423 531
424sub mon { 532sub mon {
425 my ($noderef, $port) = split /#/, shift, 2; 533 my ($noderef, $port) = split /#/, shift, 2;
426 534
427 my $node = $NODE{$noderef} || add_node $noderef; 535 my $node = $NODE{$noderef} || add_node $noderef;
428 536
429 my $cb = shift; 537 my $cb = @_ ? shift : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,';
430 538
431 unless (ref $cb) { 539 unless (ref $cb) {
432 if (@_) { 540 if (@_) {
433 # send a kill info message 541 # send a kill info message
434 my (@msg) = ($cb, @_); 542 my (@msg) = ($cb, @_);
465=cut 573=cut
466 574
467sub mon_guard { 575sub mon_guard {
468 my ($port, @refs) = @_; 576 my ($port, @refs) = @_;
469 577
578 #TODO: mon-less form?
579
470 mon $port, sub { 0 && @refs } 580 mon $port, sub { 0 && @refs }
471} 581}
472 582
473=item lnk $port1, $port2
474
475Link two ports. This is simply a shorthand for:
476
477 mon $port1, $port2;
478 mon $port2, $port1;
479
480It means that if either one is killed abnormally, the other one gets
481killed as well.
482
483=item kil $portid[, @reason] 583=item kil $port[, @reason]
484 584
485Kill the specified port with the given C<@reason>. 585Kill the specified port with the given C<@reason>.
486 586
487If no C<@reason> is specified, then the port is killed "normally" (linked 587If no C<@reason> is specified, then the port is killed "normally" (linked
488ports will not be kileld, or even notified). 588ports will not be kileld, or even notified).
494will be reported as reason C<< die => $@ >>. 594will be reported as reason C<< die => $@ >>.
495 595
496Transport/communication errors are reported as C<< transport_error => 596Transport/communication errors are reported as C<< transport_error =>
497$message >>. 597$message >>.
498 598
499=back
500
501=head1 FUNCTIONS FOR NODES
502
503=over 4
504
505=item become_public $noderef
506
507Tells the node to become a public node, i.e. reachable from other nodes.
508
509The first argument is the (unresolved) node reference of the local node
510(if missing then the empty string is used).
511
512It is quite common to not specify anything, in which case the local node
513tries to listen on the default port, or to only specify a port number, in
514which case AnyEvent::MP tries to guess the local addresses.
515
516=cut 599=cut
600
601=item $port = spawn $node, $initfunc[, @initdata]
602
603Creates a port on the node C<$node> (which can also be a port ID, in which
604case it's the node where that port resides).
605
606The port ID of the newly created port is return immediately, and it is
607permissible to immediately start sending messages or monitor the port.
608
609After the port has been created, the init function is
610called. This function must be a fully-qualified function name
611(e.g. C<MyApp::Chat::Server::init>). To specify a function in the main
612program, use C<::name>.
613
614If the function doesn't exist, then the node tries to C<require>
615the package, then the package above the package and so on (e.g.
616C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
617exists or it runs out of package names.
618
619The init function is then called with the newly-created port as context
620object (C<$SELF>) and the C<@initdata> values as arguments.
621
622A common idiom is to pass your own port, monitor the spawned port, and
623in the init function, monitor the original port. This two-way monitoring
624ensures that both ports get cleaned up when there is a problem.
625
626Example: spawn a chat server port on C<$othernode>.
627
628 # this node, executed from within a port context:
629 my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;
630 mon $server;
631
632 # init function on C<$othernode>
633 sub connect {
634 my ($srcport) = @_;
635
636 mon $srcport;
637
638 rcv $SELF, sub {
639 ...
640 };
641 }
642
643=cut
644
645sub _spawn {
646 my $port = shift;
647 my $init = shift;
648
649 local $SELF = "$NODE#$port";
650 eval {
651 &{ load_func $init }
652 };
653 _self_die if $@;
654}
655
656sub spawn(@) {
657 my ($noderef, undef) = split /#/, shift, 2;
658
659 my $id = "$RUNIQ." . $ID++;
660
661 $_[0] =~ /::/
662 or Carp::croak "spawn init function must be a fully-qualified name, caught";
663
664 ($NODE{$noderef} || add_node $noderef)
665 ->send (["", "AnyEvent::MP::_spawn" => $id, @_]);
666
667 "$noderef#$id"
668}
517 669
518=back 670=back
519 671
520=head1 NODE MESSAGES 672=head1 NODE MESSAGES
521 673
563 715
564=back 716=back
565 717
566=head1 AnyEvent::MP vs. Distributed Erlang 718=head1 AnyEvent::MP vs. Distributed Erlang
567 719
568AnyEvent::MP got lots of its ideas from distributed erlang (erlang node 720AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
569== aemp node, erlang process == aemp port), so many of the documents and 721== aemp node, Erlang process == aemp port), so many of the documents and
570programming techniques employed by erlang apply to AnyEvent::MP. Here is a 722programming techniques employed by Erlang apply to AnyEvent::MP. Here is a
571sample: 723sample:
572 724
573 http://www.erlang.se/doc/programming_rules.shtml 725 http://www.Erlang.se/doc/programming_rules.shtml
574 http://erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4 726 http://Erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4
575 http://erlang.org/download/erlang-book-part1.pdf # chapters 5 and 6 727 http://Erlang.org/download/Erlang-book-part1.pdf # chapters 5 and 6
576 http://erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5 728 http://Erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5
577 729
578Despite the similarities, there are also some important differences: 730Despite the similarities, there are also some important differences:
579 731
580=over 4 732=over 4
581 733
592 744
593Erlang uses processes that selctively receive messages, and therefore 745Erlang uses processes that selctively receive messages, and therefore
594needs a queue. AEMP is event based, queuing messages would serve no useful 746needs a queue. AEMP is event based, queuing messages would serve no useful
595purpose. 747purpose.
596 748
597(But see L<Coro::MP> for a more erlang-like process model on top of AEMP). 749(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).
598 750
599=item * Erlang sends are synchronous, AEMP sends are asynchronous. 751=item * Erlang sends are synchronous, AEMP sends are asynchronous.
600 752
601Sending messages in erlang is synchronous and blocks the process. AEMP 753Sending messages in Erlang is synchronous and blocks the process. AEMP
602sends are immediate, connection establishment is handled in the 754sends are immediate, connection establishment is handled in the
603background. 755background.
604 756
605=item * Erlang can silently lose messages, AEMP cannot. 757=item * Erlang can silently lose messages, AEMP cannot.
606 758
609and c, and the other side only receives messages a and c). 761and c, and the other side only receives messages a and c).
610 762
611AEMP guarantees correct ordering, and the guarantee that there are no 763AEMP guarantees correct ordering, and the guarantee that there are no
612holes in the message sequence. 764holes in the message sequence.
613 765
614=item * In erlang, processes can be declared dead and later be found to be 766=item * In Erlang, processes can be declared dead and later be found to be
615alive. 767alive.
616 768
617In erlang it can happen that a monitored process is declared dead and 769In Erlang it can happen that a monitored process is declared dead and
618linked processes get killed, but later it turns out that the process is 770linked processes get killed, but later it turns out that the process is
619still alive - and can receive messages. 771still alive - and can receive messages.
620 772
621In AEMP, when port monitoring detects a port as dead, then that port will 773In AEMP, when port monitoring detects a port as dead, then that port will
622eventually be killed - it cannot happen that a node detects a port as dead 774eventually be killed - it cannot happen that a node detects a port as dead
623and then later sends messages to it, finding it is still alive. 775and then later sends messages to it, finding it is still alive.
624 776
625=item * Erlang can send messages to the wrong port, AEMP does not. 777=item * Erlang can send messages to the wrong port, AEMP does not.
626 778
627In erlang it is quite possible that a node that restarts reuses a process 779In Erlang it is quite possible that a node that restarts reuses a process
628ID known to other nodes for a completely different process, causing 780ID known to other nodes for a completely different process, causing
629messages destined for that process to end up in an unrelated process. 781messages destined for that process to end up in an unrelated process.
630 782
631AEMP never reuses port IDs, so old messages or old port IDs floating 783AEMP never reuses port IDs, so old messages or old port IDs floating
632around in the network will not be sent to an unrelated port. 784around in the network will not be sent to an unrelated port.
638securely authenticate nodes. 790securely authenticate nodes.
639 791
640=item * The AEMP protocol is optimised for both text-based and binary 792=item * The AEMP protocol is optimised for both text-based and binary
641communications. 793communications.
642 794
643The AEMP protocol, unlike the erlang protocol, supports both 795The AEMP protocol, unlike the Erlang protocol, supports both
644language-independent text-only protocols (good for debugging) and binary, 796language-independent text-only protocols (good for debugging) and binary,
645language-specific serialisers (e.g. Storable). 797language-specific serialisers (e.g. Storable).
646 798
647It has also been carefully designed to be implementable in other languages 799It has also been carefully designed to be implementable in other languages
648with a minimum of work while gracefully degrading fucntionality to make the 800with a minimum of work while gracefully degrading fucntionality to make the
649protocol simple. 801protocol simple.
650 802
803=item * AEMP has more flexible monitoring options than Erlang.
804
805In Erlang, you can chose to receive I<all> exit signals as messages
806or I<none>, there is no in-between, so monitoring single processes is
807difficult to implement. Monitoring in AEMP is more flexible than in
808Erlang, as one can choose between automatic kill, exit message or callback
809on a per-process basis.
810
811=item * Erlang tries to hide remote/local connections, AEMP does not.
812
813Monitoring in Erlang is not an indicator of process death/crashes,
814as linking is (except linking is unreliable in Erlang).
815
816In AEMP, you don't "look up" registered port names or send to named ports
817that might or might not be persistent. Instead, you normally spawn a port
818on the remote node. The init function monitors the you, and you monitor
819the remote port. Since both monitors are local to the node, they are much
820more reliable.
821
822This also saves round-trips and avoids sending messages to the wrong port
823(hard to do in Erlang).
824
825=back
826
827=head1 RATIONALE
828
829=over 4
830
831=item Why strings for ports and noderefs, why not objects?
832
833We considered "objects", but found that the actual number of methods
834thatc an be called are very low. Since port IDs and noderefs travel over
835the network frequently, the serialising/deserialising would add lots of
836overhead, as well as having to keep a proxy object.
837
838Strings can easily be printed, easily serialised etc. and need no special
839procedures to be "valid".
840
841And a a miniport consists of a single closure stored in a global hash - it
842can't become much cheaper.
843
844=item Why favour JSON, why not real serialising format such as Storable?
845
846In fact, any AnyEvent::MP node will happily accept Storable as framing
847format, but currently there is no way to make a node use Storable by
848default.
849
850The default framing protocol is JSON because a) JSON::XS is many times
851faster for small messages and b) most importantly, after years of
852experience we found that object serialisation is causing more problems
853than it gains: Just like function calls, objects simply do not travel
854easily over the network, mostly because they will always be a copy, so you
855always have to re-think your design.
856
857Keeping your messages simple, concentrating on data structures rather than
858objects, will keep your messages clean, tidy and efficient.
859
651=back 860=back
652 861
653=head1 SEE ALSO 862=head1 SEE ALSO
654 863
655L<AnyEvent>. 864L<AnyEvent>.

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines