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.128 by root, Sun Mar 4 14:28:44 2012 UTC vs.
Revision 1.129 by root, Thu Mar 8 21:37:51 2012 UTC

… …
35 # destroy a port again 35 # destroy a port again
36 kil $port; # "normal" kill 36 kil $port; # "normal" kill
37 kil $port, my_error => "everything is broken"; # error kill 37 kil $port, my_error => "everything is broken"; # error kill
38 38
39 # monitoring 39 # monitoring
40 mon $localport, $cb->(@msg) # callback is invoked on death 40 mon $port, $cb->(@msg) # callback is invoked on death
41 mon $localport, $otherport # kill otherport on abnormal death 41 mon $port, $localport # kill localport on abnormal death
42 mon $localport, $otherport, @msg # send message on death 42 mon $port, $localport, @msg # send message on death
43 43
44 # temporarily execute code in port context 44 # temporarily execute code in port context
45 peval $port, sub { die "kill the port!" }; 45 peval $port, sub { die "kill the port!" };
46 46
47 # execute callbacks in $SELF port context 47 # execute callbacks in $SELF port context
… …
834 ref $action[0] 834 ref $action[0]
835 ? $action[0]() 835 ? $action[0]()
836 : snd @action; 836 : snd @action;
837 }; 837 };
838} 838}
839
840#=item $cb2 = timeout $seconds, $cb[, @args]
839 841
840=item cal $port, @msg, $callback[, $timeout] 842=item cal $port, @msg, $callback[, $timeout]
841 843
842A simple form of RPC - sends a message to the given C<$port> with the 844A simple form of RPC - sends a message to the given C<$port> with the
843given contents (C<@msg>), but adds a reply port to the message. 845given contents (C<@msg>), but adds a reply port to the message.
… …
925pools. For example, a worker port for image scaling might do this: 927pools. For example, a worker port for image scaling might do this:
926 928
927 db_set my_image_scalers => $port; 929 db_set my_image_scalers => $port;
928 930
929And clients looking for an image scaler will want to get the 931And clients looking for an image scaler will want to get the
930C<my_image_scalers> keys: 932C<my_image_scalers> keys from time to time:
931 933
932 db_keys "my_image_scalers" => 60 => sub { 934 db_keys my_image_scalers => sub {
933 #d##TODO# 935 @ports = @{ $_[0] };
936 };
937
938Or better yet, they want to monitor the database family, so they always
939have a reasonable up-to-date copy:
940
941 db_mon my_image_scalers => sub {
942 @ports = keys %{ $_[0] };
943 };
944
945In general, you can set or delete single subkeys, but query and monitor
946whole families only.
947
948If you feel the need to monitor or query a single subkey, try giving it
949it's own family.
934 950
935=over 951=over
936 952
937=item db_set $family => $subkey [=> $value] 953=item db_set $family => $subkey [=> $value]
938 954
… …
947 963
948Sets the key on the database and returns a guard. When the guard is 964Sets the key on the database and returns a guard. When the guard is
949destroyed, the key is deleted from the database. If C<$value> is missing, 965destroyed, the key is deleted from the database. If C<$value> is missing,
950then C<undef> is used. 966then C<undef> is used.
951 967
968=item db_family $family => $cb->(\%familyhash)
969
970Queries the named database C<$family> and call the callback with the
971family represented as a hash. You can keep and freely modify the hash.
972
973=item db_keys $family => $cb->(\@keys)
974
975Same as C<db_family>, except it only queries the family I<subkeys> and passes
976them as array reference to the callback.
977
978=item db_values $family => $cb->(\@values)
979
980Same as C<db_family>, except it only queries the family I<values> and passes them
981as array reference to the callback.
982
952=item $guard = db_mon $family => $cb->($familyhash, \@subkeys...) 983=item $guard = db_mon $family => $cb->($familyhash, \@subkeys...)
953 984
954Creates a monitor on the given database family. Each time a key is set or 985Creates a monitor on the given database family. Each time a key is set or
955or is deleted the callback is called with a hash containing the database 986or is deleted the callback is called with a hash containing the database
956family and an arrayref with subkeys that have changed. 987family and an arrayref with subkeys that have changed.
957 988
958Specifically, if one of the passed subkeys exists in the $familyhash, then 989Specifically, if one of the passed subkeys exists in the $familyhash, then
959it is currently set to the value in the $familyhash. Otherwise, it has 990it is currently set to the value in the $familyhash. Otherwise, it has
960been deleted. 991been deleted.
992
993The family hash reference belongs to AnyEvent::MP and B<must not be
994modified or stored> by the callback. When in doubt, make a copy.
961 995
962The first call will be with the current contents of the family and all 996The first call will be with the current contents of the family and all
963keys, as if they were just added. 997keys, as if they were just added.
964 998
965It is possible that the callback is called with a change event even though 999It is possible that the callback is called with a change event even though

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines