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.36 by root, Thu Aug 6 10:46:48 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
27
28 # linking two ports, so they both crash together
29 lnk $port1, $port2;
30 37
31 # monitoring 38 # monitoring
32 mon $port, $cb->(@msg) # callback is invoked on death 39 mon $port, $cb->(@msg) # callback is invoked on death
33 mon $port, $otherport # kill otherport on abnormal death 40 mon $port, $otherport # kill otherport on abnormal death
34 mon $port, $otherport, @msg # send message on death 41 mon $port, $otherport, @msg # send message on death
35 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.
51
36=head1 DESCRIPTION 52=head1 DESCRIPTION
37 53
38This module (-family) implements a simple message passing framework. 54This module (-family) implements a simple message passing framework.
39 55
40Despite its simplicity, you can securely message other processes running 56Despite its simplicity, you can securely message other processes running
43For 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>
44manual page. 60manual page.
45 61
46At the moment, this module family is severly broken and underdocumented, 62At the moment, this module family is severly broken and underdocumented,
47so 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 -
48stay tuned! The basic API should be finished, however. 64stay tuned!
49 65
50=head1 CONCEPTS 66=head1 CONCEPTS
51 67
52=over 4 68=over 4
53 69
98 114
99=cut 115=cut
100 116
101package AnyEvent::MP; 117package AnyEvent::MP;
102 118
103use AnyEvent::MP::Base; 119use AnyEvent::MP::Kernel;
104 120
105use common::sense; 121use common::sense;
106 122
107use Carp (); 123use Carp ();
108 124
109use AE (); 125use AE ();
110 126
111use base "Exporter"; 127use base "Exporter";
112 128
113our $VERSION = '0.1'; 129our $VERSION = $AnyEvent::MP::Kernel::VERSION;
130
114our @EXPORT = qw( 131our @EXPORT = qw(
115 NODE $NODE *SELF node_of _any_ 132 NODE $NODE *SELF node_of _any_
116 resolve_node initialise_node 133 resolve_node initialise_node
117 snd rcv mon kil reg psub 134 snd rcv mon kil reg psub spawn
118 port 135 port
119); 136);
120 137
121our $SELF; 138our $SELF;
122 139
146it should know the noderefs of some other nodes in the network. 163it should know the noderefs of some other nodes in the network.
147 164
148This function initialises a node - it must be called exactly once (or 165This function initialises a node - it must be called exactly once (or
149never) before calling other AnyEvent::MP functions. 166never) before calling other AnyEvent::MP functions.
150 167
151All arguments are noderefs, which can be either resolved or unresolved. 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.
152 176
153There are two types of networked nodes, public nodes and slave nodes: 177There are two types of networked nodes, public nodes and slave nodes:
154 178
155=over 4 179=over 4
156 180
157=item public nodes 181=item public nodes
158 182
159For public nodes, C<$noderef> must either be a (possibly unresolved) 183For public nodes, C<$noderef> (supplied either directly to
160noderef, in which case it will be resolved, or C<undef> (or missing), in 184C<initialise_node> or indirectly via a profile or the nodename) must be a
161which case the noderef will be guessed. 185noderef (possibly unresolved, in which case it will be resolved).
162 186
163Afterwards, the node will bind itself on all endpoints and try to connect 187After resolving, the node will bind itself on all endpoints and try to
164to all additional C<$seednodes> that are specified. Seednodes are optional 188connect to all additional C<$seednodes> that are specified. Seednodes are
165and can be used to quickly bootstrap the node into an existing network. 189optional and can be used to quickly bootstrap the node into an existing
190network.
166 191
167=item slave nodes 192=item slave nodes
168 193
169When the C<$noderef> is the special string C<slave/>, then the node will 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
170become a slave node. Slave nodes cannot be contacted from outside and will 196node. Slave nodes cannot be contacted from outside and will route most of
171route most of their traffic to the master node that they attach to. 197their traffic to the master node that they attach to.
172 198
173At least one additional noderef is required: The node will try to connect 199At least one additional noderef is required (either by specifying it
174to all of them and will become a slave attached to the first node it can 200directly or because it is part of the configuration profile): The node
175successfully connect to. 201will try to connect to all of them and will become a slave attached to the
202first node it can successfully connect to.
176 203
177=back 204=back
178 205
179This function will block until all nodes have been resolved and, for slave 206This function will block until all nodes have been resolved and, for slave
180nodes, until it has successfully established a connection to a master 207nodes, until it has successfully established a connection to a master
181server. 208server.
182 209
183Example: become a public node listening on the default node. 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.
184 213
185 initialise_node; 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";
186 225
187Example: become a public node, and try to contact some well-known master 226Example: become a public node, and try to contact some well-known master
188servers to become part of the network. 227servers to become part of the network.
189 228
190 initialise_node undef, "master1", "master2"; 229 initialise_node undef, "master1", "master2";
193 232
194 initialise_node 4041; 233 initialise_node 4041;
195 234
196Example: become a public node, only visible on localhost port 4044. 235Example: become a public node, only visible on localhost port 4044.
197 236
198 initialise_node "locahost:4044"; 237 initialise_node "localhost:4044";
199
200Example: become a slave node to any of the specified master servers.
201
202 initialise_node "slave/", "master1", "192.168.13.17", "mp.example.net";
203 238
204=item $cv = resolve_node $noderef 239=item $cv = resolve_node $noderef
205 240
206Takes an unresolved node reference that may contain hostnames and 241Takes an unresolved node reference that may contain hostnames and
207abbreviated IDs, resolves all of them and returns a resolved node 242abbreviated IDs, resolves all of them and returns a resolved node
263that Storable can serialise and deserialise is allowed, and for the local 298that Storable can serialise and deserialise is allowed, and for the local
264node, anything can be passed. 299node, anything can be passed.
265 300
266=item $local_port = port 301=item $local_port = port
267 302
268Create 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
269matching port ("full port") or a single-callback port ("miniport"), 304no callbacks set and will throw an error when it receives messages.
270depending on how C<rcv> callbacks are bound to the object.
271 305
272=item $port = port { my @msg = @_; $finished } 306=item $local_port = port { my @msg = @_ }
273 307
274Creates a "miniport", that is, a very lightweight port without any pattern 308Creates a new local port, and returns its ID. Semantically the same as
275matching behind it, and returns its ID. Semantically the same as creating
276a port and calling C<rcv $port, $callback> on it. 309creating a port and calling C<rcv $port, $callback> on it.
277 310
278The 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
279callback 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
280will 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.
281 315
282The 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:
283be passed to the callback.
284 317
285If you need the local port id in the callback, this works nicely: 318 my $port = port {
286 319 my @msg = @_;
287 my $port; $port = port { 320 ...
288 snd $otherport, reply => $port; 321 kil $SELF;
289 }; 322 };
290 323
291=cut 324=cut
292 325
293sub rcv($@); 326sub rcv($@);
327
328sub _kilme {
329 die "received message on port without callback";
330}
294 331
295sub port(;&) { 332sub port(;&) {
296 my $id = "$UNIQ." . $ID++; 333 my $id = "$UNIQ." . $ID++;
297 my $port = "$NODE#$id"; 334 my $port = "$NODE#$id";
298 335
299 if (@_) { 336 rcv $port, shift || \&_kilme;
300 rcv $port, shift;
301 } else {
302 $PORT{$id} = sub { }; # nop
303 }
304 337
305 $port 338 $port
306} 339}
307 340
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) 341=item rcv $local_port, $callback->(@msg)
328 342
329Replaces the callback on the specified miniport (after converting it to 343Replaces the default callback on the specified port. There is no way to
330one if required). 344remove the default callback: use C<sub { }> to disable it, or better
331 345C<kil> the port when it is no longer needed.
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 346
345The global C<$SELF> (exported by this module) contains C<$port> while 347The global C<$SELF> (exported by this module) contains C<$port> while
346executing the callback. 348executing the callback. Runtime errors during callback execution will
349result in the port being C<kil>ed.
347 350
348Runtime errors wdurign callback execution will result in the port being 351The default callback received all messages not matched by a more specific
349C<kil>ed. 352C<tag> match.
350 353
351If the match is an array reference, then it will be matched against the 354=item rcv $local_port, tag => $callback->(@msg_without_tag), ...
352first elements of the message, otherwise only the first element is being
353matched.
354 355
355Any 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
356exported 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>).
357 359
358While not required, it is highly recommended that the first matching 360The original message will be passed to the callback, after the first
359element is a string identifying the message. The one-string-only match is 361element (the tag) has been removed. The callback will use the same
360also the most efficient match (by far). 362environment as the default callback (see above).
361 363
362Example: create a port and bind receivers on it in one go. 364Example: create a port and bind receivers on it in one go.
363 365
364 my $port = rcv port, 366 my $port = rcv port,
365 msg1 => sub { ...; 0 }, 367 msg1 => sub { ... },
366 msg2 => sub { ...; 0 }, 368 msg2 => sub { ... },
367 ; 369 ;
368 370
369Example: create a port, bind receivers and send it in a message elsewhere 371Example: create a port, bind receivers and send it in a message elsewhere
370in one go: 372in one go:
371 373
372 snd $otherport, reply => 374 snd $otherport, reply =>
373 rcv port, 375 rcv port,
374 msg1 => sub { ...; 0 }, 376 msg1 => sub { ... },
375 ... 377 ...
376 ; 378 ;
377 379
378=cut 380=cut
379 381
382 my ($noderef, $portid) = split /#/, $port, 2; 384 my ($noderef, $portid) = split /#/, $port, 2;
383 385
384 ($NODE{$noderef} || add_node $noderef) == $NODE{""} 386 ($NODE{$noderef} || add_node $noderef) == $NODE{""}
385 or Carp::croak "$port: rcv can only be called on local ports, caught"; 387 or Carp::croak "$port: rcv can only be called on local ports, caught";
386 388
387 if (@_ == 1) { 389 while (@_) {
390 if (ref $_[0]) {
391 if (my $self = $PORT_DATA{$portid}) {
392 "AnyEvent::MP::Port" eq ref $self
393 or Carp::croak "$port: rcv can only be called on message matching ports, caught";
394
395 $self->[2] = shift;
396 } else {
388 my $cb = shift; 397 my $cb = shift;
389 delete $PORT_DATA{$portid};
390 $PORT{$portid} = sub { 398 $PORT{$portid} = sub {
391 local $SELF = $port; 399 local $SELF = $port;
392 eval { 400 eval { &$cb }; _self_die if $@;
393 &$cb 401 };
394 and kil $port;
395 }; 402 }
396 _self_die if $@; 403 } elsif (defined $_[0]) {
397 };
398 } else {
399 my $self = $PORT_DATA{$portid} ||= do { 404 my $self = $PORT_DATA{$portid} ||= do {
400 my $self = bless { 405 my $self = bless [$PORT{$port} || sub { }, { }, $port], "AnyEvent::MP::Port";
401 id => $port,
402 }, "AnyEvent::MP::Port";
403 406
404 $PORT{$portid} = sub { 407 $PORT{$portid} = sub {
405 local $SELF = $port; 408 local $SELF = $port;
406 409
407 eval {
408 for (@{ $self->{rc0}{$_[0]} }) { 410 if (my $cb = $self->[1]{$_[0]}) {
409 $_ && &{$_->[0]} 411 shift;
410 && undef $_; 412 eval { &$cb }; _self_die if $@;
411 } 413 } else {
412
413 for (@{ $self->{rcv}{$_[0]} }) {
414 $_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1]
415 && &{$_->[0]} 414 &{ $self->[0] };
416 && undef $_;
417 }
418
419 for (@{ $self->{any} }) {
420 $_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1]
421 && &{$_->[0]}
422 && undef $_;
423 } 415 }
424 }; 416 };
425 _self_die if $@; 417
418 $self
426 }; 419 };
427 420
428 $self
429 };
430
431 "AnyEvent::MP::Port" eq ref $self 421 "AnyEvent::MP::Port" eq ref $self
432 or Carp::croak "$port: rcv can only be called on message matching ports, caught"; 422 or Carp::croak "$port: rcv can only be called on message matching ports, caught";
433 423
434 while (@_) {
435 my ($match, $cb) = splice @_, 0, 2; 424 my ($tag, $cb) = splice @_, 0, 2;
436 425
437 if (!ref $match) { 426 if (defined $cb) {
438 push @{ $self->{rc0}{$match} }, [$cb]; 427 $self->[1]{$tag} = $cb;
439 } elsif (("ARRAY" eq ref $match && !ref $match->[0])) {
440 my ($type, @match) = @$match;
441 @match
442 ? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match]
443 : push @{ $self->{rc0}{$match->[0]} }, [$cb];
444 } else { 428 } else {
445 push @{ $self->{any} }, [$cb, $match]; 429 delete $self->[1]{$tag};
446 } 430 }
447 } 431 }
448 } 432 }
449 433
450 $port 434 $port
494 478
495=item $guard = mon $port 479=item $guard = mon $port
496 480
497=item $guard = mon $port, $rcvport, @msg 481=item $guard = mon $port, $rcvport, @msg
498 482
499Monitor the given port and do something when the port is killed, and 483Monitor the given port and do something when the port is killed or
500optionally return a guard that can be used to stop monitoring again. 484messages to it were lost, and optionally return a guard that can be used
485to stop monitoring again.
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.
501 494
502In the first form (callback), the callback is simply called with any 495In the first form (callback), the callback is simply called with any
503number of C<@reason> elements (no @reason means that the port was deleted 496number 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 497"normally"). Note also that I<< the callback B<must> never die >>, so use
505C<eval> if unsure. 498C<eval> if unsure.
506 499
507In the second form (another port given), the other port (C<$rcvport) 500In the second form (another port given), the other port (C<$rcvport>)
508will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on 501will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on
509"normal" kils nothing happens, while under all other conditions, the other 502"normal" kils nothing happens, while under all other conditions, the other
510port is killed with the same reason. 503port is killed with the same reason.
511 504
512The third form (kill self) is the same as the second form, except that 505The third form (kill self) is the same as the second form, except that
513C<$rvport> defaults to C<$SELF>. 506C<$rvport> defaults to C<$SELF>.
514 507
515In the last form (message), a message of the form C<@msg, @reason> will be 508In the last form (message), a message of the form C<@msg, @reason> will be
516C<snd>. 509C<snd>.
517 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.
517
518Example: call a given callback when C<$port> is killed. 518Example: call a given callback when C<$port> is killed.
519 519
520 mon $port, sub { warn "port died because of <@_>\n" }; 520 mon $port, sub { warn "port died because of <@_>\n" };
521 521
522Example: kill ourselves when C<$port> is killed abnormally. 522Example: kill ourselves when C<$port> is killed abnormally.
532sub mon { 532sub mon {
533 my ($noderef, $port) = split /#/, shift, 2; 533 my ($noderef, $port) = split /#/, shift, 2;
534 534
535 my $node = $NODE{$noderef} || add_node $noderef; 535 my $node = $NODE{$noderef} || add_node $noderef;
536 536
537 my $cb = @_ ? $_[0] : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,'; 537 my $cb = @_ ? shift : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,';
538 538
539 unless (ref $cb) { 539 unless (ref $cb) {
540 if (@_) { 540 if (@_) {
541 # send a kill info message 541 # send a kill info message
542 my (@msg) = @_; 542 my (@msg) = ($cb, @_);
543 $cb = sub { snd @msg, @_ }; 543 $cb = sub { snd @msg, @_ };
544 } else { 544 } else {
545 # simply kill other port 545 # simply kill other port
546 my $port = $cb; 546 my $port = $cb;
547 $cb = sub { kil $port, @_ if @_ }; 547 $cb = sub { kil $port, @_ if @_ };
578 #TODO: mon-less form? 578 #TODO: mon-less form?
579 579
580 mon $port, sub { 0 && @refs } 580 mon $port, sub { 0 && @refs }
581} 581}
582 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] 583=item kil $port[, @reason]
608 584
609Kill the specified port with the given C<@reason>. 585Kill the specified port with the given C<@reason>.
610 586
611If 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
617Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks 593Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
618will be reported as reason C<< die => $@ >>. 594will be reported as reason C<< die => $@ >>.
619 595
620Transport/communication errors are reported as C<< transport_error => 596Transport/communication errors are reported as C<< transport_error =>
621$message >>. 597$message >>.
598
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}
622 669
623=back 670=back
624 671
625=head1 NODE MESSAGES 672=head1 NODE MESSAGES
626 673
759or I<none>, there is no in-between, so monitoring single processes is 806or I<none>, there is no in-between, so monitoring single processes is
760difficult to implement. Monitoring in AEMP is more flexible than in 807difficult to implement. Monitoring in AEMP is more flexible than in
761Erlang, as one can choose between automatic kill, exit message or callback 808Erlang, as one can choose between automatic kill, exit message or callback
762on a per-process basis. 809on a per-process basis.
763 810
764=item * Erlang has different semantics for monitoring and linking, AEMP has the same. 811=item * Erlang tries to hide remote/local connections, AEMP does not.
765 812
766Monitoring in Erlang is not an indicator of process death/crashes, 813Monitoring in Erlang is not an indicator of process death/crashes,
767as linking is (except linking is unreliable in Erlang). In AEMP, the 814as linking is (except linking is unreliable in Erlang).
768semantics of monitoring and linking are identical, linking is simply 815
769two-way monitoring with automatic kill. 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.
770 859
771=back 860=back
772 861
773=head1 SEE ALSO 862=head1 SEE ALSO
774 863

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines