| … | |
… | |
| 185 | use common::sense; |
185 | use common::sense; |
| 186 | |
186 | |
| 187 | use Carp (); |
187 | use Carp (); |
| 188 | |
188 | |
| 189 | use AE (); |
189 | use AE (); |
|
|
190 | use Guard (); |
| 190 | |
191 | |
| 191 | use base "Exporter"; |
192 | use base "Exporter"; |
| 192 | |
193 | |
| 193 | our $VERSION = $AnyEvent::MP::Config::VERSION; |
194 | our $VERSION = $AnyEvent::MP::Config::VERSION; |
| 194 | |
195 | |
| 195 | our @EXPORT = qw( |
196 | our @EXPORT = qw( |
| 196 | NODE $NODE *SELF node_of after |
197 | NODE $NODE *SELF node_of after |
| 197 | configure |
198 | configure |
| 198 | snd rcv mon mon_guard kil psub peval spawn cal |
199 | snd rcv mon mon_guard kil psub peval spawn cal |
| 199 | port |
200 | port |
|
|
201 | db_set db_del db_reg |
|
|
202 | db_mon db_family db_keys db_values |
| 200 | ); |
203 | ); |
| 201 | |
204 | |
| 202 | our $SELF; |
205 | our $SELF; |
| 203 | |
206 | |
| 204 | sub _self_die() { |
207 | sub _self_die() { |
| … | |
… | |
| 228 | |
231 | |
| 229 | This function configures a node - it must be called exactly once (or |
232 | This function configures a node - it must be called exactly once (or |
| 230 | never) before calling other AnyEvent::MP functions. |
233 | never) before calling other AnyEvent::MP functions. |
| 231 | |
234 | |
| 232 | The key/value pairs are basically the same ones as documented for the |
235 | The key/value pairs are basically the same ones as documented for the |
| 233 | F<aemp> command line utility (sans the set/del prefix), with two additions: |
236 | F<aemp> command line utility (sans the set/del prefix), with these additions: |
| 234 | |
237 | |
| 235 | =over 4 |
238 | =over 4 |
| 236 | |
239 | |
| 237 | =item norc => $boolean (default false) |
240 | =item norc => $boolean (default false) |
| 238 | |
241 | |
| … | |
… | |
| 243 | =item force => $boolean (default false) |
246 | =item force => $boolean (default false) |
| 244 | |
247 | |
| 245 | IF true, then the values specified in the C<configure> will take |
248 | IF true, then the values specified in the C<configure> will take |
| 246 | precedence over any values configured via the rc file. The default is for |
249 | precedence over any values configured via the rc file. The default is for |
| 247 | the rc file to override any options specified in the program. |
250 | the rc file to override any options specified in the program. |
|
|
251 | |
|
|
252 | =item secure => $pass->($nodeid) |
|
|
253 | |
|
|
254 | In addition to specifying a boolean, you can specify a code reference that |
|
|
255 | is called for every remote execution attempt - the execution request is |
|
|
256 | granted iff the callback returns a true value. |
|
|
257 | |
|
|
258 | See F<semp setsecure> for more info. |
| 248 | |
259 | |
| 249 | =back |
260 | =back |
| 250 | |
261 | |
| 251 | =over 4 |
262 | =over 4 |
| 252 | |
263 | |
| … | |
… | |
| 269 | and the values specified directly via C<configure> have lowest priority, |
280 | and the values specified directly via C<configure> have lowest priority, |
| 270 | and can only be used to specify defaults. |
281 | and can only be used to specify defaults. |
| 271 | |
282 | |
| 272 | If the profile specifies a node ID, then this will become the node ID of |
283 | If the profile specifies a node ID, then this will become the node ID of |
| 273 | this process. If not, then the profile name will be used as node ID, with |
284 | this process. If not, then the profile name will be used as node ID, with |
| 274 | a slash (C</>) attached. |
285 | a unique randoms tring (C</%u>) appended. |
| 275 | |
286 | |
| 276 | If the node ID (or profile name) ends with a slash (C</>), then a random |
287 | The node ID can contain some C<%> sequences that are expanded: C<%n> |
| 277 | string is appended to make it unique. |
288 | is expanded to the local nodename, C<%u> is replaced by a random |
|
|
289 | strign to make the node unique. For example, the F<aemp> commandline |
|
|
290 | utility uses C<aemp/%n/%u> as nodename, which might expand to |
|
|
291 | C<aemp/cerebro/ZQDGSIkRhEZQDGSIkRhE>. |
| 278 | |
292 | |
| 279 | =item step 2, bind listener sockets |
293 | =item step 2, bind listener sockets |
| 280 | |
294 | |
| 281 | The next step is to look up the binds in the profile, followed by binding |
295 | The next step is to look up the binds in the profile, followed by binding |
| 282 | aemp protocol listeners on all binds specified (it is possible and valid |
296 | aemp protocol listeners on all binds specified (it is possible and valid |
| … | |
… | |
| 299 | Example: become a distributed node using the local node name as profile. |
313 | Example: become a distributed node using the local node name as profile. |
| 300 | This should be the most common form of invocation for "daemon"-type nodes. |
314 | This should be the most common form of invocation for "daemon"-type nodes. |
| 301 | |
315 | |
| 302 | configure |
316 | configure |
| 303 | |
317 | |
| 304 | Example: become an anonymous node. This form is often used for commandline |
318 | Example: become a semi-anonymous node. This form is often used for |
| 305 | clients. |
319 | commandline clients. |
| 306 | |
320 | |
| 307 | configure nodeid => "anon/"; |
321 | configure nodeid => "myscript/%n/%u"; |
| 308 | |
322 | |
| 309 | Example: configure a node using a profile called seed, which is suitable |
323 | Example: configure a node using a profile called seed, which is suitable |
| 310 | for a seed node as it binds on all local addresses on a fixed port (4040, |
324 | for a seed node as it binds on all local addresses on a fixed port (4040, |
| 311 | customary for aemp). |
325 | customary for aemp). |
| 312 | |
326 | |
| … | |
… | |
| 672 | } |
686 | } |
| 673 | |
687 | |
| 674 | $node->monitor ($port, $cb); |
688 | $node->monitor ($port, $cb); |
| 675 | |
689 | |
| 676 | defined wantarray |
690 | defined wantarray |
| 677 | and ($cb += 0, AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }) |
691 | and ($cb += 0, Guard::guard { $node->unmonitor ($port, $cb) }) |
| 678 | } |
692 | } |
| 679 | |
693 | |
| 680 | =item $guard = mon_guard $port, $ref, $ref... |
694 | =item $guard = mon_guard $port, $ref, $ref... |
| 681 | |
695 | |
| 682 | Monitors the given C<$port> and keeps the passed references. When the port |
696 | Monitors the given C<$port> and keeps the passed references. When the port |
| … | |
… | |
| 875 | $port |
889 | $port |
| 876 | } |
890 | } |
| 877 | |
891 | |
| 878 | =back |
892 | =back |
| 879 | |
893 | |
|
|
894 | =head1 DISTRIBUTED DATABASE |
|
|
895 | |
|
|
896 | AnyEvent::MP comes with a simple distributed database. The database will |
|
|
897 | be mirrored asynchronously at all global nodes. Other nodes bind to one of |
|
|
898 | the global nodes for their needs. |
|
|
899 | |
|
|
900 | The database consists of a two-level hash - a hash contains a hash which |
|
|
901 | contains values. |
|
|
902 | |
|
|
903 | The top level hash key is called "family", and the second-level hash key |
|
|
904 | is called "subkey" or simply "key". |
|
|
905 | |
|
|
906 | The family must be alphanumeric, i.e. start with a letter and consist |
|
|
907 | of letters, digits, underscores and colons (C<[A-Za-z][A-Za-z0-9_:]*>, |
|
|
908 | pretty much like Perl module names. |
|
|
909 | |
|
|
910 | As the family namespace is global, it is recommended to prefix family names |
|
|
911 | with the name of the application or module using it. |
|
|
912 | |
|
|
913 | The subkeys must be non-empty strings, with no further restrictions. |
|
|
914 | |
|
|
915 | The values should preferably be strings, but other perl scalars should |
|
|
916 | work as well (such as undef, arrays and hashes). |
|
|
917 | |
|
|
918 | Every database entry is owned by one node - adding the same family/subkey |
|
|
919 | combination on multiple nodes will not cause discomfort for AnyEvent::MP, |
|
|
920 | but the result might be nondeterministic, i.e. the key might have |
|
|
921 | different values on different nodes. |
|
|
922 | |
|
|
923 | Different subkeys in the same family can be owned by different nodes |
|
|
924 | without problems, and in fact, this is the common method to create worker |
|
|
925 | pools. For example, a worker port for image scaling might do this: |
|
|
926 | |
|
|
927 | db_set my_image_scalers => $port; |
|
|
928 | |
|
|
929 | And clients looking for an image scaler will want to get the |
|
|
930 | C<my_image_scalers> keys: |
|
|
931 | |
|
|
932 | db_keys "my_image_scalers" => 60 => sub { |
|
|
933 | #d##TODO# |
|
|
934 | |
|
|
935 | =over |
|
|
936 | |
|
|
937 | =item db_set $family => $subkey [=> $value] |
|
|
938 | |
|
|
939 | Sets (or replaces) a key to the database - if C<$value> is omitted, |
|
|
940 | C<undef> is used instead. |
|
|
941 | |
|
|
942 | =item db_del $family => $subkey |
|
|
943 | |
|
|
944 | Deletes a key from the database. |
|
|
945 | |
|
|
946 | =item $guard = db_reg $family => $subkey [=> $value] |
|
|
947 | |
|
|
948 | Sets the key on the database and returns a guard. When the guard is |
|
|
949 | destroyed, the key is deleted from the database. If C<$value> is missing, |
|
|
950 | then C<undef> is used. |
|
|
951 | |
|
|
952 | =item $guard = db_mon $family => $cb->($familyhash, \@subkeys...) |
|
|
953 | |
|
|
954 | Creates a monitor on the given database family. Each time a key is set or |
|
|
955 | or is deleted the callback is called with a hash containing the database |
|
|
956 | family and an arrayref with subkeys that have changed. |
|
|
957 | |
|
|
958 | Specifically, if one of the passed subkeys exists in the $familyhash, then |
|
|
959 | it is currently set to the value in the $familyhash. Otherwise, it has |
|
|
960 | been deleted. |
|
|
961 | |
|
|
962 | The first call will be with the current contents of the family and all |
|
|
963 | keys, as if they were just added. |
|
|
964 | |
|
|
965 | It is possible that the callback is called with a change event even though |
|
|
966 | the subkey is already present and the value has not changed. |
|
|
967 | |
|
|
968 | The monitoring stops when the guard object is destroyed. |
|
|
969 | |
|
|
970 | Example: on every change to the family "mygroup", print out all keys. |
|
|
971 | |
|
|
972 | my $guard = db_mon mygroup => sub { |
|
|
973 | my ($family, $keys) = @_; |
|
|
974 | print "mygroup members: ", (join " ", keys %$family), "\n"; |
|
|
975 | }; |
|
|
976 | |
|
|
977 | Exmaple: wait until the family "My::Module::workers" is non-empty. |
|
|
978 | |
|
|
979 | my $guard; $guard = db_mon My::Module::workers => sub { |
|
|
980 | my ($family, $keys) = @_; |
|
|
981 | return unless %$family; |
|
|
982 | undef $guard; |
|
|
983 | print "My::Module::workers now nonempty\n"; |
|
|
984 | }; |
|
|
985 | |
|
|
986 | Example: print all changes to the family "AnyRvent::Fantasy::Module". |
|
|
987 | |
|
|
988 | my $guard = db_mon AnyRvent::Fantasy::Module => sub { |
|
|
989 | my ($family, $keys) = @_; |
|
|
990 | |
|
|
991 | for (@$keys) { |
|
|
992 | print "$_: ", |
|
|
993 | (exists $family->{$_} |
|
|
994 | ? $family->{$_} |
|
|
995 | : "(deleted)"), |
|
|
996 | "\n"; |
|
|
997 | } |
|
|
998 | }; |
|
|
999 | |
|
|
1000 | =cut |
|
|
1001 | |
|
|
1002 | =back |
|
|
1003 | |
| 880 | =head1 AnyEvent::MP vs. Distributed Erlang |
1004 | =head1 AnyEvent::MP vs. Distributed Erlang |
| 881 | |
1005 | |
| 882 | AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node |
1006 | AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node |
| 883 | == aemp node, Erlang process == aemp port), so many of the documents and |
1007 | == aemp node, Erlang process == aemp port), so many of the documents and |
| 884 | programming techniques employed by Erlang apply to AnyEvent::MP. Here is a |
1008 | programming techniques employed by Erlang apply to AnyEvent::MP. Here is a |
