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.153 by root, Sat Nov 2 01:30:49 2019 UTC vs.
Revision 1.156 by root, Sat Oct 23 03:35:49 2021 UTC

… …
76 76
77=over 4 77=over 4
78 78
79=item port 79=item port
80 80
81Not to be confused with a TCP port, a "port" is something you can send 81Not to be confused with TCP ports, a "port" is something you can send
82messages to (with the C<snd> function). 82messages to (with the C<snd> function).
83 83
84Ports allow you to register C<rcv> handlers that can match all or just 84Ports allow you to register C<rcv> handlers that can match all or just
85some messages. Messages send to ports will not be queued, regardless of 85some messages. Messages send to ports will not be queued, regardless of
86anything was listening for them or not. 86whether anything was listening for them or not.
87 87
88Ports are represented by (printable) strings called "port IDs". 88Ports are represented by (printable) strings called "port IDs".
89 89
90=item port ID - C<nodeid#portname> 90=item port ID - C<nodeid#portname>
91 91
… …
302this process. If not, then the profile name will be used as node ID, with 302this process. If not, then the profile name will be used as node ID, with
303a unique randoms tring (C</%u>) appended. 303a unique randoms tring (C</%u>) appended.
304 304
305The node ID can contain some C<%> sequences that are expanded: C<%n> 305The node ID can contain some C<%> sequences that are expanded: C<%n>
306is expanded to the local nodename, C<%u> is replaced by a random 306is expanded to the local nodename, C<%u> is replaced by a random
307strign to make the node unique. For example, the F<aemp> commandline 307string to make the node unique. For example, the F<aemp> commandline
308utility uses C<aemp/%n/%u> as nodename, which might expand to 308utility uses C<aemp/%n/%u> as nodename, which might expand to
309C<aemp/cerebro/ZQDGSIkRhEZQDGSIkRhE>. 309C<aemp/cerebro/ZQDGSIkRhEZQDGSIkRhE>.
310 310
311=item step 2, bind listener sockets 311=item step 2, bind listener sockets
312 312
… …
650In the last form (message), a message of the form C<$rcvport, @msg, 650In the last form (message), a message of the form C<$rcvport, @msg,
651@reason> will be C<snd>. 651@reason> will be C<snd>.
652 652
653Monitoring-actions are one-shot: once messages are lost (and a monitoring 653Monitoring-actions are one-shot: once messages are lost (and a monitoring
654alert was raised), they are removed and will not trigger again, even if it 654alert was raised), they are removed and will not trigger again, even if it
655turns out that the port is still alive. 655turns out that the port is still alive (but monitoring actions added after
656that will again trigger).
656 657
657As a rule of thumb, monitoring requests should always monitor a remote 658As a rule of thumb, monitoring requests should always monitor a remote
658port locally (using a local C<$rcvport> or a callback). The reason is that 659port locally (using a local C<$rcvport> or a callback). The reason is that
659kill messages might get lost, just like any other message. Another less 660kill messages might get lost, just like any other message. Another less
660obvious reason is that even monitoring requests can get lost (for example, 661obvious reason is that even monitoring requests can get lost (for example,
… …
876#=item $cb2 = timeout $seconds, $cb[, @args] 877#=item $cb2 = timeout $seconds, $cb[, @args]
877 878
878=item cal $port, @msg, $callback[, $timeout] 879=item cal $port, @msg, $callback[, $timeout]
879 880
880A simple form of RPC - sends a message to the given C<$port> with the 881A simple form of RPC - sends a message to the given C<$port> with the
881given contents (C<@msg>), but adds a reply port to the message. 882given contents (C<@msg>), but appends a reply port to the message.
882 883
883The reply port is created temporarily just for the purpose of receiving 884The reply port is created temporarily just for the purpose of receiving
884the reply, and will be C<kil>ed when no longer needed. 885the reply, and will be C<kil>ed when no longer needed.
885 886
886A reply message sent to the port is passed to the C<$callback> as-is. 887A reply message sent to the port is passed to the C<$callback> as-is.
… …
965 966
966Different subkeys in the same family can be owned by different nodes 967Different subkeys in the same family can be owned by different nodes
967without problems, and in fact, this is the common method to create worker 968without problems, and in fact, this is the common method to create worker
968pools. For example, a worker port for image scaling might do this: 969pools. For example, a worker port for image scaling might do this:
969 970
970 db_set my_image_scalers => $port; 971 db_set my_image_scalers => $port; # value not used
971 972
972And clients looking for an image scaler will want to get the 973And clients looking for an image scaler will want to get the
973C<my_image_scalers> keys from time to time: 974C<my_image_scalers> keys from time to time:
974 975
975 db_keys my_image_scalers => sub { 976 db_keys my_image_scalers => sub {

Diff Legend

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