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.122 by root, Wed Feb 29 18:44:59 2012 UTC vs.
Revision 1.126 by root, Sat Mar 3 19:43:41 2012 UTC

82 82
83Ports are represented by (printable) strings called "port IDs". 83Ports are represented by (printable) strings called "port IDs".
84 84
85=item port ID - C<nodeid#portname> 85=item port ID - C<nodeid#portname>
86 86
87A port ID is the concatenation of a node ID, a hash-mark (C<#>) as 87A port ID is the concatenation of a node ID, a hash-mark (C<#>)
88separator, and a port name (a printable string of unspecified format). 88as separator, and a port name (a printable string of unspecified
89format created by AnyEvent::MP).
89 90
90=item node 91=item node
91 92
92A node is a single process containing at least one port - the node port, 93A node is a single process containing at least one port - the node port,
93which enables nodes to manage each other remotely, and to create new 94which enables nodes to manage each other remotely, and to create new
184use common::sense; 185use common::sense;
185 186
186use Carp (); 187use Carp ();
187 188
188use AE (); 189use AE ();
190use Guard ();
189 191
190use base "Exporter"; 192use base "Exporter";
191 193
192our $VERSION = $AnyEvent::MP::Config::VERSION; 194our $VERSION = $AnyEvent::MP::Config::VERSION;
193 195
194our @EXPORT = qw( 196our @EXPORT = qw(
195 NODE $NODE *SELF node_of after 197 NODE $NODE *SELF node_of after
196 configure 198 configure
197 snd rcv mon mon_guard kil psub peval spawn cal 199 snd rcv mon mon_guard kil psub peval spawn cal
198 port 200 port
201 db_set db_del db_reg
199); 202);
200 203
201our $SELF; 204our $SELF;
202 205
203sub _self_die() { 206sub _self_die() {
268and the values specified directly via C<configure> have lowest priority, 271and the values specified directly via C<configure> have lowest priority,
269and can only be used to specify defaults. 272and can only be used to specify defaults.
270 273
271If the profile specifies a node ID, then this will become the node ID of 274If the profile specifies a node ID, then this will become the node ID of
272this process. If not, then the profile name will be used as node ID, with 275this process. If not, then the profile name will be used as node ID, with
273a slash (C</>) attached. 276a unique randoms tring (C</%u>) appended.
274 277
275If the node ID (or profile name) ends with a slash (C</>), then a random 278The node ID can contain some C<%> sequences that are expanded: C<%n>
276string is appended to make it unique. 279is expanded to the local nodename, C<%u> is replaced by a random
280strign to make the node unique. For example, the F<aemp> commandline
281utility uses C<aemp/%n/%u> as nodename, which might expand to
282C<aemp/cerebro/ZQDGSIkRhEZQDGSIkRhE>.
277 283
278=item step 2, bind listener sockets 284=item step 2, bind listener sockets
279 285
280The next step is to look up the binds in the profile, followed by binding 286The next step is to look up the binds in the profile, followed by binding
281aemp protocol listeners on all binds specified (it is possible and valid 287aemp protocol listeners on all binds specified (it is possible and valid
298Example: become a distributed node using the local node name as profile. 304Example: become a distributed node using the local node name as profile.
299This should be the most common form of invocation for "daemon"-type nodes. 305This should be the most common form of invocation for "daemon"-type nodes.
300 306
301 configure 307 configure
302 308
303Example: become an anonymous node. This form is often used for commandline 309Example: become a semi-anonymous node. This form is often used for
304clients. 310commandline clients.
305 311
306 configure nodeid => "anon/"; 312 configure nodeid => "myscript/%n/%u";
307 313
308Example: configure a node using a profile called seed, which is suitable 314Example: configure a node using a profile called seed, which is suitable
309for a seed node as it binds on all local addresses on a fixed port (4040, 315for a seed node as it binds on all local addresses on a fixed port (4040,
310customary for aemp). 316customary for aemp).
311 317
388sub _kilme { 394sub _kilme {
389 die "received message on port without callback"; 395 die "received message on port without callback";
390} 396}
391 397
392sub port(;&) { 398sub port(;&) {
393 my $id = "$UNIQ." . ++$ID; 399 my $id = $UNIQ . ++$ID;
394 my $port = "$NODE#$id"; 400 my $port = "$NODE#$id";
395 401
396 rcv $port, shift || \&_kilme; 402 rcv $port, shift || \&_kilme;
397 403
398 $port 404 $port
671 } 677 }
672 678
673 $node->monitor ($port, $cb); 679 $node->monitor ($port, $cb);
674 680
675 defined wantarray 681 defined wantarray
676 and ($cb += 0, AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }) 682 and ($cb += 0, Guard::guard { $node->unmonitor ($port, $cb) })
677} 683}
678 684
679=item $guard = mon_guard $port, $ref, $ref... 685=item $guard = mon_guard $port, $ref, $ref...
680 686
681Monitors the given C<$port> and keeps the passed references. When the port 687Monitors the given C<$port> and keeps the passed references. When the port
785} 791}
786 792
787sub spawn(@) { 793sub spawn(@) {
788 my ($nodeid, undef) = split /#/, shift, 2; 794 my ($nodeid, undef) = split /#/, shift, 2;
789 795
790 my $id = "$RUNIQ." . ++$ID; 796 my $id = $RUNIQ . ++$ID;
791 797
792 $_[0] =~ /::/ 798 $_[0] =~ /::/
793 or Carp::croak "spawn init function must be a fully-qualified name, caught"; 799 or Carp::croak "spawn init function must be a fully-qualified name, caught";
794 800
795 snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_; 801 snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;
874 $port 880 $port
875} 881}
876 882
877=back 883=back
878 884
885=head1 DISTRIBUTED DATABASE
886
887AnyEvent::MP comes with a simple distributed database. The database will
888be mirrored asynchronously at all global nodes. Other nodes bind to one of
889the global nodes for their needs.
890
891The database consists of a two-level hash - a hash contains a hash which
892contains values.
893
894The top level hash key is called "family", and the second-level hash key
895is called "subkey" or simply "key".
896
897The family must be alphanumeric, i.e. start with a letter and consist
898of letters, digits, underscores and colons (C<[A-Za-z][A-Za-z0-9_:]*>,
899pretty much like Perl module names.
900
901As the family namespace is global, it is recommended to prefix family names
902with the name of the application or module using it.
903
904The subkeys must be non-empty strings, with no further restrictions.
905
906The values should preferably be strings, but other perl scalars should
907work as well (such as undef, arrays and hashes).
908
909Every database entry is owned by one node - adding the same family/subkey
910combination on multiple nodes will not cause discomfort for AnyEvent::MP,
911but the result might be nondeterministic, i.e. the key might have
912different values on different nodes.
913
914Different subkeys in the same family can be owned by different nodes
915without problems, and in fact, this is the common method to create worker
916pools. For example, a worker port for image scaling might do this:
917
918 db_set my_image_scalers => $port;
919
920And clients looking for an image scaler will want to get the
921C<my_image_scalers> keys:
922
923 db_keys "my_image_scalers" => 60 => sub {
924 #d##TODO#
925
926=over
927
928=item db_set $family => $subkey [=> $value]
929
930Sets (or replaces) a key to the database - if C<$value> is omitted,
931C<undef> is used instead.
932
933=item db_del $family => $subkey
934
935Deletes a key from the database.
936
937=item $guard = db_reg $family => $subkey [=> $value]
938
939Sets the key on the database and returns a guard. When the guard is
940destroyed, the key is deleted from the database. If C<$value> is missing,
941then C<undef> is used.
942
943=cut
944
945=back
946
879=head1 AnyEvent::MP vs. Distributed Erlang 947=head1 AnyEvent::MP vs. Distributed Erlang
880 948
881AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node 949AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
882== aemp node, Erlang process == aemp port), so many of the documents and 950== aemp node, Erlang process == aemp port), so many of the documents and
883programming techniques employed by Erlang apply to AnyEvent::MP. Here is a 951programming techniques employed by Erlang apply to AnyEvent::MP. Here is a

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines