--- AnyEvent-MP/MP.pm 2012/03/22 20:07:31 1.139 +++ AnyEvent-MP/MP.pm 2016/08/17 19:45:18 1.150 @@ -49,13 +49,18 @@ die "kill the port, delayed"; }; -=head1 CURRENT STATUS + # distributed database - modification + db_set $family => $subkey [=> $value] # add a subkey + db_del $family => $subkey... # delete one or more subkeys + db_reg $family => $port [=> $value] # register a port + + # distributed database - queries + db_family $family => $cb->(\%familyhash) + db_keys $family => $cb->(\@keys) + db_values $family => $cb->(\@values) - bin/aemp - stable. - AnyEvent::MP - stable API, should work. - AnyEvent::MP::Intro - explains most concepts. - AnyEvent::MP::Kernel - mostly stable API. - AnyEvent::MP::Global - stable API. + # distributed database - monitoring a family + db_mon $family => $cb->(\%familyhash, \@added, \@changed, \@deleted) =head1 DESCRIPTION @@ -115,7 +120,7 @@ Currently, only standard C specifications can be used, which specify TCP ports to listen on. So a bind is basically just a tcp socket -in listening mode thta accepts conenctions form other nodes. +in listening mode that accepts connections from other nodes. =item seed nodes @@ -125,13 +130,13 @@ Seed nodes themselves are not special - they are seed nodes only because some other node I them as such, but any node can be used as seed -node for other nodes, and eahc node cna use a different set of seed nodes. +node for other nodes, and eahc node can use a different set of seed nodes. In addition to discovering the network, seed nodes are also used to -maintain the network - all nodes using the same seed node form are part of -the same network. If a network is split into multiple subnets because e.g. -the network link between the parts goes down, then using the same seed -nodes for all nodes ensures that eventually the subnets get merged again. +maintain the network - all nodes using the same seed node are part of the +same network. If a network is split into multiple subnets because e.g. the +network link between the parts goes down, then using the same seed nodes +for all nodes ensures that eventually the subnets get merged again. Seed nodes are expected to be long-running, and at least one seed node should always be available. They should also be relatively responsive - a @@ -165,7 +170,7 @@ node and tries to keep connections to all other nodes. So while it can make sense to make every node "global" in small networks, it usually makes sense to only make seed nodes into global nodes in large networks (nodes -keep connections to seed nodes and global nodes, so makign them the same +keep connections to seed nodes and global nodes, so making them the same reduces overhead). =back @@ -180,13 +185,23 @@ use AnyEvent::MP::Config (); use AnyEvent::MP::Kernel; -use AnyEvent::MP::Kernel qw(%NODE %PORT %PORT_DATA $UNIQ $RUNIQ $ID); +use AnyEvent::MP::Kernel qw( + %NODE %PORT %PORT_DATA $UNIQ $RUNIQ $ID + add_node load_func + + NODE $NODE + configure + node_of port_is_local + snd kil + db_set db_del + db_mon db_family db_keys db_values +); use common::sense; use Carp (); -use AE (); +use AnyEvent (); use Guard (); use base "Exporter"; @@ -194,12 +209,20 @@ our $VERSION = $AnyEvent::MP::Config::VERSION; our @EXPORT = qw( - NODE $NODE *SELF node_of after + NODE $NODE configure - snd rcv mon mon_guard kil psub peval spawn cal - port + node_of port_is_local + snd kil + db_set db_del + db_mon db_family db_keys db_values + + *SELF + + port rcv mon mon_guard psub peval spawn cal db_set db_del db_reg db_mon db_family db_keys db_values + + after ); our $SELF; @@ -220,6 +243,10 @@ Extracts and returns the node ID from a port ID or a node ID. +=item $is_local = port_is_local $port + +Returns true iff the port is a local port. + =item configure $profile, key => value... =item configure key => value... @@ -240,7 +267,7 @@ =item norc => $boolean (default false) If true, then the rc file (e.g. F<~/.perl-anyevent-mp>) will I -be consulted - all configuraiton options must be specified in the +be consulted - all configuration options must be specified in the C call. =item force => $boolean (default false) @@ -249,19 +276,6 @@ precedence over any values configured via the rc file. The default is for the rc file to override any options specified in the program. -=item secure => $pass->(@msg) - -In addition to specifying a boolean, you can specify a code reference that -is called for every code execution attempt - the execution request is -granted iff the callback returns a true value. - -Most of the time the callback should look only at -C<$AnyEvent::MP::Kernel::SRCNODE> to make a decision, and not at the -actual message (which can be about anything, and is mostly provided for -diagnostic purposes). - -See F for more info. - =back =over 4 @@ -299,7 +313,7 @@ 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 +to have no binds, meaning that the node cannot be contacted from 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). @@ -406,7 +420,7 @@ sub rcv($@); my $KILME = sub { - (my $tag = substr $_[0], 0, 30) =~ s/([\x20-\x7e])/./g; + (my $tag = substr $_[0], 0, 30) =~ s/([^\x20-\x7e])/./g; kil $SELF, unhandled_message => "no callback found for message '$tag'"; }; @@ -474,7 +488,7 @@ my $port = shift; my ($nodeid, $portid) = split /#/, $port, 2; - $NODE{$nodeid} == $NODE{""} + $nodeid eq $NODE or Carp::croak "$port: rcv can only be called on local ports, caught"; while (@_) { @@ -528,7 +542,7 @@ =item peval $port, $coderef[, @args] Evaluates the given C<$codref> within the contetx of C<$port>, that is, -when the code throews an exception the C<$port> will be killed. +when the code throws an exception the C<$port> will be killed. Any remaining args will be passed to the callback. Any return values will be returned to the caller. @@ -1043,10 +1057,10 @@ Same as C, except it only queries the family I and passes them as array reference to the callback. -=item $guard = db_mon $family => $cb->($familyhash, \@added, \@changed, \@deleted) +=item $guard = db_mon $family => $cb->(\%familyhash, \@added, \@changed, \@deleted) -Creates a monitor on the given database family. Each time a key is set -or or is deleted the callback is called with a hash containing the +Creates a monitor on the given database family. Each time a key is +set or is deleted the callback is called with a hash containing the database family and three lists of added, changed and deleted subkeys, respectively. If no keys have changed then the array reference might be C or even missing. @@ -1084,9 +1098,9 @@ print "My::Module::workers now nonempty\n"; }; -Example: print all changes to the family "AnyRvent::Fantasy::Module". +Example: print all changes to the family "AnyEvent::Fantasy::Module". - my $guard = db_mon AnyRvent::Fantasy::Module => sub { + my $guard = db_mon AnyEvent::Fantasy::Module => sub { my ($family, $a, $c, $d) = @_; print "+$_=$family->{$_}\n" for @$a; @@ -1147,13 +1161,13 @@ This is not a philosophical difference, but simply stems from AnyEvent::MP being event-based, while Erlang is process-based. -You cna have a look at L for a more Erlang-like process model on +You can have a look at L for a more Erlang-like process model on top of AEMP and Coro threads. =item * Erlang sends are synchronous, AEMP sends are asynchronous. Sending messages in Erlang is synchronous and blocks the process until -a conenction has been established and the message sent (and so does not +a connection has been established and the message sent (and so does not need a queue that can overflow). AEMP sends return immediately, connection establishment is handled in the background. @@ -1269,6 +1283,9 @@ =item AnyEvent::MP::Global no longer has group management functions. +At least not officially - the grp_* functions are still exported and might +work, but they will be removed in some later release. + AnyEvent::MP now comes with a distributed database that is more powerful. Its database families map closely to port groups, but the API has changed (the functions are also now exported by AnyEvent::MP). Here is @@ -1299,7 +1316,7 @@ ignored: db_mon $group => sub { - my ($ports, $add, $chg, $lde) = @_; + my ($ports, $add, $chg, $del) = @_; $ports = [keys %$ports]; # now $ports, $add and $del are the same as @@ -1362,7 +1379,7 @@ =head1 LOGGING -AnyEvent::MP does not normally log anything by itself, but sinc eit is the +AnyEvent::MP does not normally log anything by itself, but since it is the root of the contetx hierarchy for AnyEvent::MP modules, it will receive all log messages by submodules.