--- AnyEvent-MP/MP.pm 2009/08/05 23:50:46 1.34 +++ AnyEvent-MP/MP.pm 2009/08/30 18:51:49 1.69 @@ -10,34 +10,56 @@ NODE # returns this node's noderef NODE $port # returns the noderef of the port + $SELF # receiving/own port id in rcv callbacks + + # initialise the node so it can send/receive messages + initialise_node; + + # ports are message endpoints + + # sending messages snd $port, type => data...; + snd $port, @msg; + snd @msg_with_first_element_being_a_port; - $SELF # receiving/own port id in rcv callbacks + # creating/using ports, the simple way + my $simple_port = port { my @msg = @_; 0 }; - rcv $port, smartmatch => $cb->($port, @msg); + # creating/using ports, tagged message matching + my $port = port; + rcv $port, ping => sub { snd $_[0], "pong"; 0 }; + rcv $port, pong => sub { warn "pong received\n"; 0 }; + + # create a port on another node + my $port = spawn $node, $initfunc, @initdata; + + # monitoring + mon $port, $cb->(@msg) # callback is invoked on death + mon $port, $otherport # kill otherport on abnormal death + mon $port, $otherport, @msg # send message on death + +=head1 CURRENT STATUS + + AnyEvent::MP - stable API, should work + AnyEvent::MP::Intro - outdated + AnyEvent::MP::Kernel - mostly stable + AnyEvent::MP::Global - mostly stable + AnyEvent::MP::Node - mostly stable, but internal anyways + AnyEvent::MP::Transport - mostly stable, but internal anyways - # examples: - rcv $port2, ping => sub { snd $_[0], "pong"; 0 }; - rcv $port1, pong => sub { warn "pong received\n" }; - snd $port2, ping => $port1; - - # more, smarter, matches (_any_ is exported by this module) - rcv $port, [child_died => $pid] => sub { ... - rcv $port, [_any_, _any_, 3] => sub { .. $_[2] is 3 + stay tuned. =head1 DESCRIPTION This module (-family) implements a simple message passing framework. Despite its simplicity, you can securely message other processes running -on the same or other hosts. +on the same or other hosts, and you can supervise entities remotely. For an introduction to this module family, see the L -manual page. +manual page and the examples under F. -At the moment, this module family is severly broken and underdocumented, -so do not use. This was uploaded mainly to reserve the CPAN namespace - -stay tuned! The basic API should be finished, however. +At the moment, this module family is a bit underdocumented. =head1 CONCEPTS @@ -47,40 +69,53 @@ A port is something you can send messages to (with the C function). -Some ports allow you to register C handlers that can match specific -messages. All C handlers will receive messages they match, messages -will not be queued. - -=item port id - C - -A port id is normaly the concatenation of a noderef, a hash-mark (C<#>) as -separator, and a port name (a printable string of unspecified format). An -exception is the the node port, whose ID is identical to its node -reference. - -=item node +Ports allow you to register C handlers that can match all or just +some messages. Messages send to ports will not be queued, regardless of +anything was listening for them or not. -A node is a single process containing at least one port - the node -port. You can send messages to node ports to find existing ports or to -create new ports, among other things. +=item port ID - C -Nodes are either private (single-process only), slaves (connected to a -master node only) or public nodes (connectable from unrelated nodes). +A port ID is the concatenation of a node ID, a hash-mark (C<#>) as +separator, and a port name (a printable string of unspecified format). -=item noderef - C, C, C - -A node reference is a string that either simply identifies the node (for -private and slave nodes), or contains a recipe on how to reach a given -node (for public nodes). - -This recipe is simply a comma-separated list of C pairs (for -TCP/IP, other protocols might look different). +=item node -Node references come in two flavours: resolved (containing only numerical -addresses) or unresolved (where hostnames are used instead of addresses). +A node is a single process containing at least one port - the node port, +which enables nodes to manage each other remotely, and to create new +ports. + +Nodes are either public (have one or more listening ports) or private +(no listening ports). Private nodes cannot talk to other private nodes +currently. + +=item node ID - C<[a-za-Z0-9_\-.:]+> + +A node ID is a string that uniquely identifies the node within a +network. Depending on the configuration used, node IDs can look like a +hostname, a hostname and a port, or a random string. AnyEvent::MP itself +doesn't interpret node IDs in any way. + +=item binds - C + +Nodes can only talk to each other by creating some kind of connection to +each other. To do this, nodes should listen on one or more local transport +endpoints - binds. Currently, only standard C specifications can +be used, which specify TCP ports to listen on. + +=item seeds - C + +When a node starts, it knows nothing about the network. To teach the node +about the network it first has to contact some other node within the +network. This node is called a seed. + +Seeds are transport endpoint(s) of as many nodes as one wants. Those nodes +are expected to be long-running, and at least one of those should always +be available. When nodes run out of connections (e.g. due to a network +error), they try to re-establish connections to some seednodes again to +join the network. -Before using an unresolved node reference in a message you first have to -resolve it. +Apart from being sued for seeding, seednodes are not special in any way - +every public node can be a seednode. =back @@ -92,7 +127,7 @@ package AnyEvent::MP; -use AnyEvent::MP::Base; +use AnyEvent::MP::Kernel; use common::sense; @@ -102,11 +137,12 @@ use base "Exporter"; -our $VERSION = '0.1'; +our $VERSION = $AnyEvent::MP::Kernel::VERSION; + our @EXPORT = qw( - NODE $NODE *SELF node_of _any_ - resolve_node initialise_node - snd rcv mon kil reg psub + NODE $NODE *SELF node_of after + initialise_node + snd rcv mon mon_guard kil reg psub spawn port ); @@ -120,234 +156,197 @@ =item $thisnode = NODE / $NODE -The C function returns, and the C<$NODE> variable contains -the noderef of the local node. The value is initialised by a call -to C or C, after which all local port -identifiers become invalid. +The C function returns, and the C<$NODE> variable contains, the node +ID of the node running in the current process. This value is initialised by +a call to C. -=item $noderef = node_of $port +=item $nodeid = node_of $port -Extracts and returns the noderef from a portid or a noderef. +Extracts and returns the node ID from a port ID or a node ID. -=item initialise_node $noderef, $seednode, $seednode... +=item initialise_node $profile_name, key => value... -=item initialise_node "slave/", $master, $master... - -Before a node can talk to other nodes on the network it has to initialise -itself - the minimum a node needs to know is it's own name, and optionally -it should know the noderefs of some other nodes in the network. +Before a node can talk to other nodes on the network (i.e. enter +"distributed mode") it has to initialise itself - the minimum a node needs +to know is its own name, and optionally it should know the addresses of +some other nodes in the network to discover other nodes. This function initialises a node - it must be called exactly once (or never) before calling other AnyEvent::MP functions. -All arguments are noderefs, which can be either resolved or unresolved. - -There are two types of networked nodes, public nodes and slave nodes: +The first argument is a profile name. If it is C or missing, then +the current nodename will be used instead (i.e. F). -=over 4 +The function first looks up the profile in the aemp configuration (see the +L commandline utility). the profile is calculated as follows: -=item public nodes - -For public nodes, C<$noderef> must either be a (possibly unresolved) -noderef, in which case it will be resolved, or C (or missing), in -which case the noderef will be guessed. - -Afterwards, the node will bind itself on all endpoints and try to connect -to all additional C<$seednodes> that are specified. Seednodes are optional -and can be used to quickly bootstrap the node into an existing network. - -=item slave nodes - -When the C<$noderef> is the special string C, then the node will -become a slave node. Slave nodes cannot be contacted from outside and will -route most of their traffic to the master node that they attach to. - -At least one additional noderef is required: The node will try to connect -to all of them and will become a slave attached to the first node it can -successfully connect to. - -=back - -This function will block until all nodes have been resolved and, for slave -nodes, until it has successfully established a connection to a master -server. - -Example: become a public node listening on the default node. +First, all remaining key => value pairs will be used. Then they will be +overwritten by any values specified in the global default configuration +(see the F utility), then the chain of profiles selected, if +any. That means that the values specified in the profile have highest +priority and the values specified via C have lowest +priority. + +If the profile specifies a node ID, then this will become the node ID of +this process. If not, then the profile name will be used as node ID. The +special node ID of C will be replaced by a random node ID. + +The next step is to look up the binds in the profile, followed by binding +aemp protocol listeners on all binds specified (it is possible and valid +to have no binds, meaning that the node cannot be contacted form the +outside. This means the node cannot talk to other nodes that also have no +binds, but it can still talk to all "normal" nodes). + +If the profile does not specify a binds list, then the node ID will be +treated as if it were of the form C, which will be resolved and +used as binds list. + +Lastly, the seeds list from the profile is passed to the +L module, which will then use it to keep +connectivity with at least on of those seed nodes at any point in time. + +Example: become a distributed node listening on the guessed noderef, or +the one specified via C for the current node. This should be the +most common form of invocation for "daemon"-type nodes. initialise_node; -Example: become a public node, and try to contact some well-known master -servers to become part of the network. - - initialise_node undef, "master1", "master2"; - -Example: become a public node listening on port C<4041>. - - initialise_node 4041; - -Example: become a public node, only visible on localhost port 4044. - - initialise_node "locahost:4044"; +Example: become an anonymous node. This form is often used for commandline +clients. -Example: become a slave node to any of the specified master servers. + initialise_node "anon/"; - initialise_node "slave/", "master1", "192.168.13.17", "mp.example.net"; +Example: become a distributed node. If there is no profile of the given +name, or no binds list was specified, resolve C and bind +on the resulting addresses. -=item $cv = resolve_node $noderef - -Takes an unresolved node reference that may contain hostnames and -abbreviated IDs, resolves all of them and returns a resolved node -reference. - -In addition to C pairs allowed in resolved noderefs, the -following forms are supported: - -=over 4 - -=item the empty string - -An empty-string component gets resolved as if the default port (4040) was -specified. - -=item naked port numbers (e.g. C<1234>) - -These are resolved by prepending the local nodename and a colon, to be -further resolved. - -=item hostnames (e.g. C, C) - -These are resolved by using AnyEvent::DNS to resolve them, optionally -looking up SRV records for the C port, if no port was -specified. - -=back + initialise_node "localhost:4044"; =item $SELF Contains the current port id while executing C callbacks or C blocks. -=item SELF, %SELF, @SELF... +=item *SELF, SELF, %SELF, @SELF... Due to some quirks in how perl exports variables, it is impossible to -just export C<$SELF>, all the symbols called C are exported by this +just export C<$SELF>, all the symbols named C are exported by this module, but only C<$SELF> is currently used. =item snd $port, type => @data =item snd $port, @msg -Send the given message to the given port ID, which can identify either -a local or a remote port, and can be either a string or soemthignt hat -stringifies a sa port ID (such as a port object :). - -While the message can be about anything, it is highly recommended to use a -string as first element (a portid, or some word that indicates a request -type etc.). - -The message data effectively becomes read-only after a call to this -function: modifying any argument is not allowed and can cause many -problems. +Send the given message to the given port, which can identify either a +local or a remote port, and must be a port ID. + +While the message can be almost anything, it is highly recommended to +use a string as first element (a port ID, or some word that indicates a +request type etc.) and to consist if only simple perl values (scalars, +arrays, hashes) - if you think you need to pass an object, think again. + +The message data logically becomes read-only after a call to this +function: modifying any argument (or values referenced by them) is +forbidden, as there can be considerable time between the call to C +and the time the message is actually being serialised - in fact, it might +never be copied as within the same process it is simply handed to the +receiving port. The type of data you can transfer depends on the transport protocol: when JSON is used, then only strings, numbers and arrays and hashes consisting of those are allowed (no objects). When Storable is used, then anything that Storable can serialise and deserialise is allowed, and for the local -node, anything can be passed. +node, anything can be passed. Best rely only on the common denominator of +these. =item $local_port = port -Create a new local port object that can be used either as a pattern -matching port ("full port") or a single-callback port ("miniport"), -depending on how C callbacks are bound to the object. - -=item $port = port { my @msg = @_; $finished } +Create a new local port object and returns its port ID. Initially it has +no callbacks set and will throw an error when it receives messages. -Creates a "miniport", that is, a very lightweight port without any pattern -matching behind it, and returns its ID. Semantically the same as creating -a port and calling C on it. +=item $local_port = port { my @msg = @_ } -The block will be called for every message received on the port. When the -callback returns a true value its job is considered "done" and the port -will be destroyed. Otherwise it will stay alive. +Creates a new local port, and returns its ID. Semantically the same as +creating a port and calling C on it. -The message will be passed as-is, no extra argument (i.e. no port id) will -be passed to the callback. +The block will be called for every message received on the port, with the +global variable C<$SELF> set to the port ID. Runtime errors will cause the +port to be Ced. The message will be passed as-is, no extra argument +(i.e. no port ID) will be passed to the callback. -If you need the local port id in the callback, this works nicely: +If you want to stop/destroy the port, simply C it: - my $port; $port = port { - snd $otherport, reply => $port; + my $port = port { + my @msg = @_; + ... + kil $SELF; }; =cut sub rcv($@); +sub _kilme { + die "received message on port without callback"; +} + sub port(;&) { my $id = "$UNIQ." . $ID++; my $port = "$NODE#$id"; - if (@_) { - rcv $port, shift; - } else { - $PORT{$id} = sub { }; # nop - } + rcv $port, shift || \&_kilme; $port } -=item reg $port, $name - -Registers the given port under the name C<$name>. If the name already -exists it is replaced. - -A port can only be registered under one well known name. - -A port automatically becomes unregistered when it is killed. - -=cut - -sub reg(@) { - my ($port, $name) = @_; +=item rcv $local_port, $callback->(@msg) - $REG{$name} = $port; -} +Replaces the default callback on the specified port. There is no way to +remove the default callback: use C to disable it, or better +C the port when it is no longer needed. -=item rcv $port, $callback->(@msg) +The global C<$SELF> (exported by this module) contains C<$port> while +executing the callback. Runtime errors during callback execution will +result in the port being Ced. -Replaces the callback on the specified miniport (after converting it to -one if required). +The default callback received all messages not matched by a more specific +C match. -=item rcv $port, tagstring => $callback->(@msg), ... +=item rcv $local_port, tag => $callback->(@msg_without_tag), ... -=item rcv $port, $smartmatch => $callback->(@msg), ... +Register (or replace) callbacks to be called on messages starting with the +given tag on the given port (and return the port), or unregister it (when +C<$callback> is C<$undef> or missing). There can only be one callback +registered for each tag. -=item rcv $port, [$smartmatch...] => $callback->(@msg), ... +The original message will be passed to the callback, after the first +element (the tag) has been removed. The callback will use the same +environment as the default callback (see above). -Register callbacks to be called on matching messages on the given full -port (after converting it to one if required). +Example: create a port and bind receivers on it in one go. -The callback has to return a true value when its work is done, after -which is will be removed, or a false value in which case it will stay -registered. + my $port = rcv port, + msg1 => sub { ... }, + msg2 => sub { ... }, + ; -The global C<$SELF> (exported by this module) contains C<$port> while -executing the callback. +Example: create a port, bind receivers and send it in a message elsewhere +in one go: -Runtime errors wdurign callback execution will result in the port being -Ced. + snd $otherport, reply => + rcv port, + msg1 => sub { ... }, + ... + ; -If the match is an array reference, then it will be matched against the -first elements of the message, otherwise only the first element is being -matched. +Example: temporarily register a rcv callback for a tag matching some port +(e.g. for a rpc reply) and unregister it after a message was received. -Any element in the match that is specified as C<_any_> (a function -exported by this module) matches any single element of the message. + rcv $port, $otherport => sub { + my @reply = @_; -While not required, it is highly recommended that the first matching -element is a string identifying the message. The one-string-only match is -also the most efficient match (by far). + rcv $SELF, $otherport; + }; =cut @@ -355,68 +354,50 @@ my $port = shift; my ($noderef, $portid) = split /#/, $port, 2; - ($NODE{$noderef} || add_node $noderef) == $NODE{""} + $NODE{$noderef} == $NODE{""} or Carp::croak "$port: rcv can only be called on local ports, caught"; - if (@_ == 1) { - my $cb = shift; - delete $PORT_DATA{$portid}; - $PORT{$portid} = sub { - local $SELF = $port; - eval { - &$cb - and kil $port; - }; - _self_die if $@; - }; - } else { - my $self = $PORT_DATA{$portid} ||= do { - my $self = bless { - id => $port, - }, "AnyEvent::MP::Port"; - - $PORT{$portid} = sub { - local $SELF = $port; - - eval { - for (@{ $self->{rc0}{$_[0]} }) { - $_ && &{$_->[0]} - && undef $_; - } - - for (@{ $self->{rcv}{$_[0]} }) { - $_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1] - && &{$_->[0]} - && undef $_; - } + while (@_) { + if (ref $_[0]) { + if (my $self = $PORT_DATA{$portid}) { + "AnyEvent::MP::Port" eq ref $self + or Carp::croak "$port: rcv can only be called on message matching ports, caught"; - for (@{ $self->{any} }) { - $_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1] - && &{$_->[0]} - && undef $_; + $self->[2] = shift; + } else { + my $cb = shift; + $PORT{$portid} = sub { + local $SELF = $port; + eval { &$cb }; _self_die if $@; + }; + } + } elsif (defined $_[0]) { + my $self = $PORT_DATA{$portid} ||= do { + my $self = bless [$PORT{$port} || sub { }, { }, $port], "AnyEvent::MP::Port"; + + $PORT{$portid} = sub { + local $SELF = $port; + + if (my $cb = $self->[1]{$_[0]}) { + shift; + eval { &$cb }; _self_die if $@; + } else { + &{ $self->[0] }; } }; - _self_die if $@; - }; - $self - }; + $self + }; - "AnyEvent::MP::Port" eq ref $self - or Carp::croak "$port: rcv can only be called on message matching ports, caught"; + "AnyEvent::MP::Port" eq ref $self + or Carp::croak "$port: rcv can only be called on message matching ports, caught"; - while (@_) { - my ($match, $cb) = splice @_, 0, 2; + my ($tag, $cb) = splice @_, 0, 2; - if (!ref $match) { - push @{ $self->{rc0}{$match} }, [$cb]; - } elsif (("ARRAY" eq ref $match && !ref $match->[0])) { - my ($type, @match) = @$match; - @match - ? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match] - : push @{ $self->{rc0}{$match->[0]} }, [$cb]; + if (defined $cb) { + $self->[1]{$tag} = $cb; } else { - push @{ $self->{any} }, [$cb, $match]; + delete $self->[1]{$tag}; } } } @@ -462,24 +443,51 @@ } } -=item $guard = mon $port, $cb->(@reason) +=item $guard = mon $port, $cb->(@reason) # call $cb when $port dies + +=item $guard = mon $port, $rcvport # kill $rcvport when $port dies + +=item $guard = mon $port # kill $SELF when $port dies -=item $guard = mon $port, $otherport +=item $guard = mon $port, $rcvport, @msg # send a message when $port dies -=item $guard = mon $port, $otherport, @msg +Monitor the given port and do something when the port is killed or +messages to it were lost, and optionally return a guard that can be used +to stop monitoring again. -Monitor the given port and do something when the port is killed. +C effectively guarantees that, in the absence of hardware failures, +after starting the monitor, either all messages sent to the port will +arrive, or the monitoring action will be invoked after possible message +loss has been detected. No messages will be lost "in between" (after +the first lost message no further messages will be received by the +port). After the monitoring action was invoked, further messages might get +delivered again. -In the first form, the callback is simply called with any number -of C<@reason> elements (no @reason means that the port was deleted +Note that monitoring-actions are one-shot: once messages are lost (and a +monitoring alert was raised), they are removed and will not trigger again. + +In the first form (callback), the callback is simply called with any +number of C<@reason> elements (no @reason means that the port was deleted "normally"). Note also that I<< the callback B never die >>, so use C if unsure. -In the second form, the other port will be C'ed with C<@reason>, iff -a @reason was specified, i.e. on "normal" kils nothing happens, while -under all other conditions, the other port is killed with the same reason. - -In the last form, a message of the form C<@msg, @reason> will be C. +In the second form (another port given), the other port (C<$rcvport>) +will be C'ed with C<@reason>, iff a @reason was specified, i.e. on +"normal" kils nothing happens, while under all other conditions, the other +port is killed with the same reason. + +The third form (kill self) is the same as the second form, except that +C<$rvport> defaults to C<$SELF>. + +In the last form (message), a message of the form C<@msg, @reason> will be +C. + +As a rule of thumb, monitoring requests should always monitor a port from +a local port (or callback). The reason is that kill messages might get +lost, just like any other message. Another less obvious reason is that +even monitoring requests can get lost (for exmaple, when the connection +to the other node goes down permanently). When monitoring a port locally +these problems do not exist. Example: call a given callback when C<$port> is killed. @@ -487,9 +495,9 @@ Example: kill ourselves when C<$port> is killed abnormally. - mon $port, $self; + mon $port; -Example: send us a restart message another C<$port> is killed. +Example: send us a restart message when another C<$port> is killed. mon $port, $self => "restart"; @@ -500,7 +508,7 @@ my $node = $NODE{$noderef} || add_node $noderef; - my $cb = shift; + my $cb = @_ ? shift : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,'; unless (ref $cb) { if (@_) { @@ -528,10 +536,10 @@ Optionally returns a guard that will stop the monitoring. This function is useful when you create e.g. timers or other watchers and -want to free them when the port gets killed: +want to free them when the port gets killed (note the use of C): $port->rcv (start => sub { - my $timer; $timer = mon_guard $port, AE::timer 1, 1, sub { + my $timer; $timer = mon_guard $port, AE::timer 1, 1, psub { undef $timer if 0.9 < rand; }); }); @@ -541,28 +549,21 @@ sub mon_guard { my ($port, @refs) = @_; + #TODO: mon-less form? + mon $port, sub { 0 && @refs } } -=item lnk $port1, $port2 - -Link two ports. This is simply a shorthand for: - - mon $port1, $port2; - mon $port2, $port1; - -It means that if either one is killed abnormally, the other one gets -killed as well. - =item kil $port[, @reason] Kill the specified port with the given C<@reason>. -If no C<@reason> is specified, then the port is killed "normally" (linked -ports will not be kileld, or even notified). +If no C<@reason> is specified, then the port is killed "normally" (ports +monitoring other ports will not necessarily die because a port dies +"normally"). Otherwise, linked ports get killed with the same reason (second form of -C, see below). +C, see above). Runtime errors while evaluating C callbacks or inside C blocks will be reported as reason C<< die => $@ >>. @@ -570,118 +571,172 @@ Transport/communication errors are reported as C<< transport_error => $message >>. -=back +=cut -=head1 NODE MESSAGES +=item $port = spawn $node, $initfunc[, @initdata] -Nodes understand the following messages sent to them. Many of them take -arguments called C<@reply>, which will simply be used to compose a reply -message - C<$reply[0]> is the port to reply to, C<$reply[1]> the type and -the remaining arguments are simply the message data. +Creates a port on the node C<$node> (which can also be a port ID, in which +case it's the node where that port resides). -While other messages exist, they are not public and subject to change. +The port ID of the newly created port is returned immediately, and it is +possible to immediately start sending messages or to monitor the port. -=over 4 +After the port has been created, the init function is called on the remote +node, in the same context as a C callback. This function must be a +fully-qualified function name (e.g. C). To +specify a function in the main program, use C<::name>. + +If the function doesn't exist, then the node tries to C +the package, then the package above the package and so on (e.g. +C, C, C) until the function +exists or it runs out of package names. + +The init function is then called with the newly-created port as context +object (C<$SELF>) and the C<@initdata> values as arguments. + +A common idiom is to pass a local port, immediately monitor the spawned +port, and in the remote init function, immediately monitor the passed +local port. This two-way monitoring ensures that both ports get cleaned up +when there is a problem. + +Example: spawn a chat server port on C<$othernode>. + + # this node, executed from within a port context: + my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF; + mon $server; + + # init function on C<$othernode> + sub connect { + my ($srcport) = @_; + + mon $srcport; + + rcv $SELF, sub { + ... + }; + } =cut -=item lookup => $name, @reply +sub _spawn { + my $port = shift; + my $init = shift; -Replies with the port ID of the specified well-known port, or C. + local $SELF = "$NODE#$port"; + eval { + &{ load_func $init } + }; + _self_die if $@; +} -=item devnull => ... +sub spawn(@) { + my ($noderef, undef) = split /#/, shift, 2; -Generic data sink/CPU heat conversion. + my $id = "$RUNIQ." . $ID++; -=item relay => $port, @msg + $_[0] =~ /::/ + or Carp::croak "spawn init function must be a fully-qualified name, caught"; -Simply forwards the message to the given port. + snd_to_func $noderef, "AnyEvent::MP::_spawn" => $id, @_; -=item eval => $string[ @reply] + "$noderef#$id" +} -Evaluates the given string. If C<@reply> is given, then a message of the -form C<@reply, $@, @evalres> is sent. +=item after $timeout, @msg -Example: crash another node. +=item after $timeout, $callback - snd $othernode, eval => "exit"; +Either sends the given message, or call the given callback, after the +specified number of seconds. -=item time => @reply +This is simply a utility function that comes in handy at times - the +AnyEvent::MP author is not convinced of the wisdom of having it, though, +so it may go away in the future. -Replies the the current node time to C<@reply>. +=cut -Example: tell the current node to send the current time to C<$myport> in a -C message. +sub after($@) { + my ($timeout, @action) = @_; - snd $NODE, time => $myport, timereply => 1, 2; - # => snd $myport, timereply => 1, 2,