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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines