… | |
… | |
4 | |
4 | |
5 | =head1 SYNOPSIS |
5 | =head1 SYNOPSIS |
6 | |
6 | |
7 | use AnyEvent::MP; |
7 | use AnyEvent::MP; |
8 | |
8 | |
9 | $NODE # contains this node's noderef |
9 | $NODE # contains this node's node ID |
10 | NODE # returns this node's noderef |
10 | NODE # returns this node's node ID |
11 | NODE $port # returns the noderef of the port |
|
|
12 | |
11 | |
13 | $SELF # receiving/own port id in rcv callbacks |
12 | $SELF # receiving/own port id in rcv callbacks |
14 | |
13 | |
15 | # initialise the node so it can send/receive messages |
14 | # initialise the node so it can send/receive messages |
16 | initialise_node; |
15 | configure; |
17 | |
16 | |
18 | # ports are message endpoints |
17 | # ports are message destinations |
19 | |
18 | |
20 | # sending messages |
19 | # sending messages |
21 | snd $port, type => data...; |
20 | snd $port, type => data...; |
22 | snd $port, @msg; |
21 | snd $port, @msg; |
23 | snd @msg_with_first_element_being_a_port; |
22 | snd @msg_with_first_element_being_a_port; |
24 | |
23 | |
25 | # creating/using ports, the simple way |
24 | # creating/using ports, the simple way |
26 | my $simple_port = port { my @msg = @_; 0 }; |
25 | my $simple_port = port { my @msg = @_ }; |
27 | |
26 | |
28 | # creating/using ports, tagged message matching |
27 | # creating/using ports, tagged message matching |
29 | my $port = port; |
28 | my $port = port; |
30 | rcv $port, ping => sub { snd $_[0], "pong"; 0 }; |
29 | rcv $port, ping => sub { snd $_[0], "pong" }; |
31 | rcv $port, pong => sub { warn "pong received\n"; 0 }; |
30 | rcv $port, pong => sub { warn "pong received\n" }; |
32 | |
31 | |
33 | # create a port on another node |
32 | # create a port on another node |
34 | my $port = spawn $node, $initfunc, @initdata; |
33 | my $port = spawn $node, $initfunc, @initdata; |
35 | |
34 | |
36 | # monitoring |
35 | # monitoring |
… | |
… | |
40 | |
39 | |
41 | =head1 CURRENT STATUS |
40 | =head1 CURRENT STATUS |
42 | |
41 | |
43 | bin/aemp - stable. |
42 | bin/aemp - stable. |
44 | AnyEvent::MP - stable API, should work. |
43 | AnyEvent::MP - stable API, should work. |
45 | AnyEvent::MP::Intro - uptodate, but incomplete. |
44 | AnyEvent::MP::Intro - explains most concepts. |
46 | AnyEvent::MP::Kernel - mostly stable. |
45 | AnyEvent::MP::Kernel - mostly stable. |
47 | AnyEvent::MP::Global - stable API, protocol not yet final. |
46 | AnyEvent::MP::Global - stable but incomplete, protocol not yet final. |
48 | |
47 | |
49 | stay tuned. |
48 | stay tuned. |
50 | |
49 | |
51 | =head1 DESCRIPTION |
50 | =head1 DESCRIPTION |
52 | |
51 | |
53 | This module (-family) implements a simple message passing framework. |
52 | This module (-family) implements a simple message passing framework. |
54 | |
53 | |
… | |
… | |
56 | on the same or other hosts, and you can supervise entities remotely. |
55 | on the same or other hosts, and you can supervise entities remotely. |
57 | |
56 | |
58 | For an introduction to this module family, see the L<AnyEvent::MP::Intro> |
57 | For an introduction to this module family, see the L<AnyEvent::MP::Intro> |
59 | manual page and the examples under F<eg/>. |
58 | manual page and the examples under F<eg/>. |
60 | |
59 | |
61 | At the moment, this module family is a bit underdocumented. |
|
|
62 | |
|
|
63 | =head1 CONCEPTS |
60 | =head1 CONCEPTS |
64 | |
61 | |
65 | =over 4 |
62 | =over 4 |
66 | |
63 | |
67 | =item port |
64 | =item port |
68 | |
65 | |
69 | A port is something you can send messages to (with the C<snd> function). |
66 | Not to be confused with a TCP port, a "port" is something you can send |
|
|
67 | messages to (with the C<snd> function). |
70 | |
68 | |
71 | Ports allow you to register C<rcv> handlers that can match all or just |
69 | Ports allow you to register C<rcv> handlers that can match all or just |
72 | some messages. Messages send to ports will not be queued, regardless of |
70 | some messages. Messages send to ports will not be queued, regardless of |
73 | anything was listening for them or not. |
71 | anything was listening for them or not. |
74 | |
72 | |
… | |
… | |
85 | |
83 | |
86 | Nodes are either public (have one or more listening ports) or private |
84 | Nodes are either public (have one or more listening ports) or private |
87 | (no listening ports). Private nodes cannot talk to other private nodes |
85 | (no listening ports). Private nodes cannot talk to other private nodes |
88 | currently. |
86 | currently. |
89 | |
87 | |
90 | =item node ID - C<[a-za-Z0-9_\-.:]+> |
88 | =item node ID - C<[A-Z_][a-zA-Z0-9_\-.:]*> |
91 | |
89 | |
92 | A node ID is a string that uniquely identifies the node within a |
90 | A node ID is a string that uniquely identifies the node within a |
93 | network. Depending on the configuration used, node IDs can look like a |
91 | network. Depending on the configuration used, node IDs can look like a |
94 | hostname, a hostname and a port, or a random string. AnyEvent::MP itself |
92 | hostname, a hostname and a port, or a random string. AnyEvent::MP itself |
95 | doesn't interpret node IDs in any way. |
93 | doesn't interpret node IDs in any way. |
… | |
… | |
99 | Nodes can only talk to each other by creating some kind of connection to |
97 | Nodes can only talk to each other by creating some kind of connection to |
100 | each other. To do this, nodes should listen on one or more local transport |
98 | each other. To do this, nodes should listen on one or more local transport |
101 | endpoints - binds. Currently, only standard C<ip:port> specifications can |
99 | endpoints - binds. Currently, only standard C<ip:port> specifications can |
102 | be used, which specify TCP ports to listen on. |
100 | be used, which specify TCP ports to listen on. |
103 | |
101 | |
104 | =item seeds - C<host:port> |
102 | =item seed nodes |
105 | |
103 | |
106 | When a node starts, it knows nothing about the network. To teach the node |
104 | When a node starts, it knows nothing about the network. To teach the node |
107 | about the network it first has to contact some other node within the |
105 | about the network it first has to contact some other node within the |
108 | network. This node is called a seed. |
106 | network. This node is called a seed. |
109 | |
107 | |
110 | Seeds are transport endpoint(s) of as many nodes as one wants. Those nodes |
108 | Apart from the fact that other nodes know them as seed nodes and they have |
|
|
109 | to have fixed listening addresses, seed nodes are perfectly normal nodes - |
|
|
110 | any node can function as a seed node for others. |
|
|
111 | |
|
|
112 | In addition to discovering the network, seed nodes are also used to |
|
|
113 | maintain the network and to connect nodes that otherwise would have |
|
|
114 | trouble connecting. They form the backbone of the AnyEvent::MP network. |
|
|
115 | |
111 | are expected to be long-running, and at least one of those should always |
116 | Seed nodes are expected to be long-running, and at least one seed node |
112 | be available. When nodes run out of connections (e.g. due to a network |
117 | should always be available. |
113 | error), they try to re-establish connections to some seednodes again to |
|
|
114 | join the network. |
|
|
115 | |
118 | |
116 | Apart from being sued for seeding, seednodes are not special in any way - |
119 | =item seeds - C<host:port> |
117 | every public node can be a seednode. |
120 | |
|
|
121 | Seeds are transport endpoint(s) (usually a hostname/IP address and a |
|
|
122 | TCP port) of nodes thta should be used as seed nodes. |
|
|
123 | |
|
|
124 | The nodes listening on those endpoints are expected to be long-running, |
|
|
125 | and at least one of those should always be available. When nodes run out |
|
|
126 | of connections (e.g. due to a network error), they try to re-establish |
|
|
127 | connections to some seednodes again to join the network. |
118 | |
128 | |
119 | =back |
129 | =back |
120 | |
130 | |
121 | =head1 VARIABLES/FUNCTIONS |
131 | =head1 VARIABLES/FUNCTIONS |
122 | |
132 | |
… | |
… | |
138 | |
148 | |
139 | our $VERSION = $AnyEvent::MP::Kernel::VERSION; |
149 | our $VERSION = $AnyEvent::MP::Kernel::VERSION; |
140 | |
150 | |
141 | our @EXPORT = qw( |
151 | our @EXPORT = qw( |
142 | NODE $NODE *SELF node_of after |
152 | NODE $NODE *SELF node_of after |
143 | initialise_node |
153 | configure |
144 | snd rcv mon mon_guard kil reg psub spawn |
154 | snd rcv mon mon_guard kil reg psub spawn |
145 | port |
155 | port |
146 | ); |
156 | ); |
147 | |
157 | |
148 | our $SELF; |
158 | our $SELF; |
… | |
… | |
155 | |
165 | |
156 | =item $thisnode = NODE / $NODE |
166 | =item $thisnode = NODE / $NODE |
157 | |
167 | |
158 | The C<NODE> function returns, and the C<$NODE> variable contains, the node |
168 | The C<NODE> function returns, and the C<$NODE> variable contains, the node |
159 | ID of the node running in the current process. This value is initialised by |
169 | ID of the node running in the current process. This value is initialised by |
160 | a call to C<initialise_node>. |
170 | a call to C<configure>. |
161 | |
171 | |
162 | =item $nodeid = node_of $port |
172 | =item $nodeid = node_of $port |
163 | |
173 | |
164 | Extracts and returns the node ID from a port ID or a node ID. |
174 | Extracts and returns the node ID from a port ID or a node ID. |
165 | |
175 | |
166 | =item initialise_node $profile_name, key => value... |
176 | =item configure $profile, key => value... |
|
|
177 | |
|
|
178 | =item configure key => value... |
167 | |
179 | |
168 | Before a node can talk to other nodes on the network (i.e. enter |
180 | Before a node can talk to other nodes on the network (i.e. enter |
169 | "distributed mode") it has to initialise itself - the minimum a node needs |
181 | "distributed mode") it has to configure itself - the minimum a node needs |
170 | to know is its own name, and optionally it should know the addresses of |
182 | to know is its own name, and optionally it should know the addresses of |
171 | some other nodes in the network to discover other nodes. |
183 | some other nodes in the network to discover other nodes. |
172 | |
184 | |
173 | This function initialises a node - it must be called exactly once (or |
185 | This function configures a node - it must be called exactly once (or |
174 | never) before calling other AnyEvent::MP functions. |
186 | never) before calling other AnyEvent::MP functions. |
175 | |
187 | |
176 | The first argument is a profile name. If it is C<undef> or missing, then |
188 | =over 4 |
177 | the current nodename will be used instead (i.e. F<uname -n>). |
|
|
178 | |
189 | |
|
|
190 | =item step 1, gathering configuration from profiles |
|
|
191 | |
179 | The function first looks up the profile in the aemp configuration (see the |
192 | The function first looks up a profile in the aemp configuration (see the |
180 | L<aemp> commandline utility). the profile is calculated as follows: |
193 | L<aemp> commandline utility). The profile name can be specified via the |
|
|
194 | named C<profile> parameter or can simply be the first parameter). If it is |
|
|
195 | missing, then the nodename (F<uname -n>) will be used as profile name. |
181 | |
196 | |
|
|
197 | The profile data is then gathered as follows: |
|
|
198 | |
182 | First, all remaining key => value pairs (all of which are conviniently |
199 | First, all remaining key => value pairs (all of which are conveniently |
183 | undocumented at the moment) will be used. Then they will be overwritten by |
200 | undocumented at the moment) will be interpreted as configuration |
184 | any values specified in the global default configuration (see the F<aemp> |
201 | data. Then they will be overwritten by any values specified in the global |
185 | utility), then the chain of profiles selected, if any. That means that |
202 | default configuration (see the F<aemp> utility), then the chain of |
|
|
203 | profiles chosen by the profile name (and any C<parent> attributes). |
|
|
204 | |
186 | the values specified in the profile have highest priority and the values |
205 | That means that the values specified in the profile have highest priority |
187 | specified via C<initialise_node> have lowest priority. |
206 | and the values specified directly via C<configure> have lowest priority, |
|
|
207 | and can only be used to specify defaults. |
188 | |
208 | |
189 | If the profile specifies a node ID, then this will become the node ID of |
209 | If the profile specifies a node ID, then this will become the node ID of |
190 | this process. If not, then the profile name will be used as node ID. The |
210 | this process. If not, then the profile name will be used as node ID. The |
191 | special node ID of C<anon/> will be replaced by a random node ID. |
211 | special node ID of C<anon/> will be replaced by a random node ID. |
|
|
212 | |
|
|
213 | =item step 2, bind listener sockets |
192 | |
214 | |
193 | The next step is to look up the binds in the profile, followed by binding |
215 | The next step is to look up the binds in the profile, followed by binding |
194 | aemp protocol listeners on all binds specified (it is possible and valid |
216 | aemp protocol listeners on all binds specified (it is possible and valid |
195 | to have no binds, meaning that the node cannot be contacted form the |
217 | to have no binds, meaning that the node cannot be contacted form the |
196 | outside. This means the node cannot talk to other nodes that also have no |
218 | outside. This means the node cannot talk to other nodes that also have no |
197 | binds, but it can still talk to all "normal" nodes). |
219 | binds, but it can still talk to all "normal" nodes). |
198 | |
220 | |
199 | If the profile does not specify a binds list, then a default of C<*> is |
221 | If the profile does not specify a binds list, then a default of C<*> is |
200 | used. |
222 | used, meaning the node will bind on a dynamically-assigned port on every |
|
|
223 | local IP address it finds. |
201 | |
224 | |
|
|
225 | =item step 3, connect to seed nodes |
|
|
226 | |
202 | Lastly, the seeds list from the profile is passed to the |
227 | As the last step, the seeds list from the profile is passed to the |
203 | L<AnyEvent::MP::Global> module, which will then use it to keep |
228 | L<AnyEvent::MP::Global> module, which will then use it to keep |
204 | connectivity with at least on of those seed nodes at any point in time. |
229 | connectivity with at least one node at any point in time. |
205 | |
230 | |
206 | Example: become a distributed node listening on the guessed noderef, or |
231 | =back |
207 | the one specified via C<aemp> for the current node. This should be the |
232 | |
|
|
233 | Example: become a distributed node using the locla node name as profile. |
208 | most common form of invocation for "daemon"-type nodes. |
234 | This should be the most common form of invocation for "daemon"-type nodes. |
209 | |
235 | |
210 | initialise_node; |
236 | configure |
211 | |
237 | |
212 | Example: become an anonymous node. This form is often used for commandline |
238 | Example: become an anonymous node. This form is often used for commandline |
213 | clients. |
239 | clients. |
214 | |
240 | |
215 | initialise_node "anon/"; |
241 | configure nodeid => "anon/"; |
216 | |
242 | |
217 | Example: become a distributed node. If there is no profile of the given |
243 | Example: configure a node using a profile called seed, which si suitable |
218 | name, or no binds list was specified, resolve C<localhost:4044> and bind |
244 | for a seed node as it binds on all local addresses on a fixed port (4040, |
219 | on the resulting addresses. |
245 | customary for aemp). |
220 | |
246 | |
221 | initialise_node "localhost:4044"; |
247 | # use the aemp commandline utility |
|
|
248 | # aemp profile seed nodeid anon/ binds '*:4040' |
|
|
249 | |
|
|
250 | # then use it |
|
|
251 | configure profile => "seed"; |
|
|
252 | |
|
|
253 | # or simply use aemp from the shell again: |
|
|
254 | # aemp run profile seed |
|
|
255 | |
|
|
256 | # or provide a nicer-to-remember nodeid |
|
|
257 | # aemp run profile seed nodeid "$(hostname)" |
222 | |
258 | |
223 | =item $SELF |
259 | =item $SELF |
224 | |
260 | |
225 | Contains the current port id while executing C<rcv> callbacks or C<psub> |
261 | Contains the current port id while executing C<rcv> callbacks or C<psub> |
226 | blocks. |
262 | blocks. |
… | |
… | |
348 | |
384 | |
349 | =cut |
385 | =cut |
350 | |
386 | |
351 | sub rcv($@) { |
387 | sub rcv($@) { |
352 | my $port = shift; |
388 | my $port = shift; |
353 | my ($noderef, $portid) = split /#/, $port, 2; |
389 | my ($nodeid, $portid) = split /#/, $port, 2; |
354 | |
390 | |
355 | $NODE{$noderef} == $NODE{""} |
391 | $NODE{$nodeid} == $NODE{""} |
356 | or Carp::croak "$port: rcv can only be called on local ports, caught"; |
392 | or Carp::croak "$port: rcv can only be called on local ports, caught"; |
357 | |
393 | |
358 | while (@_) { |
394 | while (@_) { |
359 | if (ref $_[0]) { |
395 | if (ref $_[0]) { |
360 | if (my $self = $PORT_DATA{$portid}) { |
396 | if (my $self = $PORT_DATA{$portid}) { |
… | |
… | |
451 | |
487 | |
452 | Monitor the given port and do something when the port is killed or |
488 | Monitor the given port and do something when the port is killed or |
453 | messages to it were lost, and optionally return a guard that can be used |
489 | messages to it were lost, and optionally return a guard that can be used |
454 | to stop monitoring again. |
490 | to stop monitoring again. |
455 | |
491 | |
|
|
492 | In the first form (callback), the callback is simply called with any |
|
|
493 | number of C<@reason> elements (no @reason means that the port was deleted |
|
|
494 | "normally"). Note also that I<< the callback B<must> never die >>, so use |
|
|
495 | C<eval> if unsure. |
|
|
496 | |
|
|
497 | In the second form (another port given), the other port (C<$rcvport>) |
|
|
498 | will be C<kil>'ed with C<@reason>, if a @reason was specified, i.e. on |
|
|
499 | "normal" kils nothing happens, while under all other conditions, the other |
|
|
500 | port is killed with the same reason. |
|
|
501 | |
|
|
502 | The third form (kill self) is the same as the second form, except that |
|
|
503 | C<$rvport> defaults to C<$SELF>. |
|
|
504 | |
|
|
505 | In the last form (message), a message of the form C<@msg, @reason> will be |
|
|
506 | C<snd>. |
|
|
507 | |
|
|
508 | Monitoring-actions are one-shot: once messages are lost (and a monitoring |
|
|
509 | alert was raised), they are removed and will not trigger again. |
|
|
510 | |
|
|
511 | As a rule of thumb, monitoring requests should always monitor a port from |
|
|
512 | a local port (or callback). The reason is that kill messages might get |
|
|
513 | lost, just like any other message. Another less obvious reason is that |
|
|
514 | even monitoring requests can get lost (for example, when the connection |
|
|
515 | to the other node goes down permanently). When monitoring a port locally |
|
|
516 | these problems do not exist. |
|
|
517 | |
456 | C<mon> effectively guarantees that, in the absence of hardware failures, |
518 | C<mon> effectively guarantees that, in the absence of hardware failures, |
457 | after starting the monitor, either all messages sent to the port will |
519 | after starting the monitor, either all messages sent to the port will |
458 | arrive, or the monitoring action will be invoked after possible message |
520 | arrive, or the monitoring action will be invoked after possible message |
459 | loss has been detected. No messages will be lost "in between" (after |
521 | loss has been detected. No messages will be lost "in between" (after |
460 | the first lost message no further messages will be received by the |
522 | the first lost message no further messages will be received by the |
461 | port). After the monitoring action was invoked, further messages might get |
523 | port). After the monitoring action was invoked, further messages might get |
462 | delivered again. |
524 | delivered again. |
463 | |
525 | |
464 | Note that monitoring-actions are one-shot: once messages are lost (and a |
526 | Inter-host-connection timeouts and monitoring depend on the transport |
465 | monitoring alert was raised), they are removed and will not trigger again. |
527 | used. The only transport currently implemented is TCP, and AnyEvent::MP |
|
|
528 | relies on TCP to detect node-downs (this can take 10-15 minutes on a |
|
|
529 | non-idle connection, and usually around two hours for idle conenctions). |
466 | |
530 | |
467 | In the first form (callback), the callback is simply called with any |
531 | This means that monitoring is good for program errors and cleaning up |
468 | number of C<@reason> elements (no @reason means that the port was deleted |
532 | stuff eventually, but they are no replacement for a timeout when you need |
469 | "normally"). Note also that I<< the callback B<must> never die >>, so use |
533 | to ensure some maximum latency. |
470 | C<eval> if unsure. |
|
|
471 | |
|
|
472 | In the second form (another port given), the other port (C<$rcvport>) |
|
|
473 | will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on |
|
|
474 | "normal" kils nothing happens, while under all other conditions, the other |
|
|
475 | port is killed with the same reason. |
|
|
476 | |
|
|
477 | The third form (kill self) is the same as the second form, except that |
|
|
478 | C<$rvport> defaults to C<$SELF>. |
|
|
479 | |
|
|
480 | In the last form (message), a message of the form C<@msg, @reason> will be |
|
|
481 | C<snd>. |
|
|
482 | |
|
|
483 | As a rule of thumb, monitoring requests should always monitor a port from |
|
|
484 | a local port (or callback). The reason is that kill messages might get |
|
|
485 | lost, just like any other message. Another less obvious reason is that |
|
|
486 | even monitoring requests can get lost (for exmaple, when the connection |
|
|
487 | to the other node goes down permanently). When monitoring a port locally |
|
|
488 | these problems do not exist. |
|
|
489 | |
534 | |
490 | Example: call a given callback when C<$port> is killed. |
535 | Example: call a given callback when C<$port> is killed. |
491 | |
536 | |
492 | mon $port, sub { warn "port died because of <@_>\n" }; |
537 | mon $port, sub { warn "port died because of <@_>\n" }; |
493 | |
538 | |
… | |
… | |
500 | mon $port, $self => "restart"; |
545 | mon $port, $self => "restart"; |
501 | |
546 | |
502 | =cut |
547 | =cut |
503 | |
548 | |
504 | sub mon { |
549 | sub mon { |
505 | my ($noderef, $port) = split /#/, shift, 2; |
550 | my ($nodeid, $port) = split /#/, shift, 2; |
506 | |
551 | |
507 | my $node = $NODE{$noderef} || add_node $noderef; |
552 | my $node = $NODE{$nodeid} || add_node $nodeid; |
508 | |
553 | |
509 | my $cb = @_ ? shift : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,'; |
554 | my $cb = @_ ? shift : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,'; |
510 | |
555 | |
511 | unless (ref $cb) { |
556 | unless (ref $cb) { |
512 | if (@_) { |
557 | if (@_) { |
… | |
… | |
588 | the package, then the package above the package and so on (e.g. |
633 | the package, then the package above the package and so on (e.g. |
589 | C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function |
634 | C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function |
590 | exists or it runs out of package names. |
635 | exists or it runs out of package names. |
591 | |
636 | |
592 | The init function is then called with the newly-created port as context |
637 | The init function is then called with the newly-created port as context |
593 | object (C<$SELF>) and the C<@initdata> values as arguments. |
638 | object (C<$SELF>) and the C<@initdata> values as arguments. It I<must> |
|
|
639 | call one of the C<rcv> functions to set callbacks on C<$SELF>, otherwise |
|
|
640 | the port might not get created. |
594 | |
641 | |
595 | A common idiom is to pass a local port, immediately monitor the spawned |
642 | A common idiom is to pass a local port, immediately monitor the spawned |
596 | port, and in the remote init function, immediately monitor the passed |
643 | port, and in the remote init function, immediately monitor the passed |
597 | local port. This two-way monitoring ensures that both ports get cleaned up |
644 | local port. This two-way monitoring ensures that both ports get cleaned up |
598 | when there is a problem. |
645 | when there is a problem. |
599 | |
646 | |
|
|
647 | C<spawn> guarantees that the C<$initfunc> has no visible effects on the |
|
|
648 | caller before C<spawn> returns (by delaying invocation when spawn is |
|
|
649 | called for the local node). |
|
|
650 | |
600 | Example: spawn a chat server port on C<$othernode>. |
651 | Example: spawn a chat server port on C<$othernode>. |
601 | |
652 | |
602 | # this node, executed from within a port context: |
653 | # this node, executed from within a port context: |
603 | my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF; |
654 | my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF; |
604 | mon $server; |
655 | mon $server; |
… | |
… | |
618 | |
669 | |
619 | sub _spawn { |
670 | sub _spawn { |
620 | my $port = shift; |
671 | my $port = shift; |
621 | my $init = shift; |
672 | my $init = shift; |
622 | |
673 | |
|
|
674 | # rcv will create the actual port |
623 | local $SELF = "$NODE#$port"; |
675 | local $SELF = "$NODE#$port"; |
624 | eval { |
676 | eval { |
625 | &{ load_func $init } |
677 | &{ load_func $init } |
626 | }; |
678 | }; |
627 | _self_die if $@; |
679 | _self_die if $@; |
628 | } |
680 | } |
629 | |
681 | |
630 | sub spawn(@) { |
682 | sub spawn(@) { |
631 | my ($noderef, undef) = split /#/, shift, 2; |
683 | my ($nodeid, undef) = split /#/, shift, 2; |
632 | |
684 | |
633 | my $id = "$RUNIQ." . $ID++; |
685 | my $id = "$RUNIQ." . $ID++; |
634 | |
686 | |
635 | $_[0] =~ /::/ |
687 | $_[0] =~ /::/ |
636 | or Carp::croak "spawn init function must be a fully-qualified name, caught"; |
688 | or Carp::croak "spawn init function must be a fully-qualified name, caught"; |
637 | |
689 | |
638 | snd_to_func $noderef, "AnyEvent::MP::_spawn" => $id, @_; |
690 | snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_; |
639 | |
691 | |
640 | "$noderef#$id" |
692 | "$nodeid#$id" |
641 | } |
693 | } |
642 | |
694 | |
643 | =item after $timeout, @msg |
695 | =item after $timeout, @msg |
644 | |
696 | |
645 | =item after $timeout, $callback |
697 | =item after $timeout, $callback |
… | |
… | |
684 | |
736 | |
685 | =item * Node IDs are arbitrary strings in AEMP. |
737 | =item * Node IDs are arbitrary strings in AEMP. |
686 | |
738 | |
687 | Erlang relies on special naming and DNS to work everywhere in the same |
739 | Erlang relies on special naming and DNS to work everywhere in the same |
688 | way. AEMP relies on each node somehow knowing its own address(es) (e.g. by |
740 | way. AEMP relies on each node somehow knowing its own address(es) (e.g. by |
689 | configuraiton or DNS), but will otherwise discover other odes itself. |
741 | configuration or DNS), but will otherwise discover other odes itself. |
690 | |
742 | |
691 | =item * Erlang has a "remote ports are like local ports" philosophy, AEMP |
743 | =item * Erlang has a "remote ports are like local ports" philosophy, AEMP |
692 | uses "local ports are like remote ports". |
744 | uses "local ports are like remote ports". |
693 | |
745 | |
694 | The failure modes for local ports are quite different (runtime errors |
746 | The failure modes for local ports are quite different (runtime errors |
… | |
… | |
707 | |
759 | |
708 | Erlang uses processes that selectively receive messages, and therefore |
760 | Erlang uses processes that selectively receive messages, and therefore |
709 | needs a queue. AEMP is event based, queuing messages would serve no |
761 | needs a queue. AEMP is event based, queuing messages would serve no |
710 | useful purpose. For the same reason the pattern-matching abilities of |
762 | useful purpose. For the same reason the pattern-matching abilities of |
711 | AnyEvent::MP are more limited, as there is little need to be able to |
763 | AnyEvent::MP are more limited, as there is little need to be able to |
712 | filter messages without dequeing them. |
764 | filter messages without dequeuing them. |
713 | |
765 | |
714 | (But see L<Coro::MP> for a more Erlang-like process model on top of AEMP). |
766 | (But see L<Coro::MP> for a more Erlang-like process model on top of AEMP). |
715 | |
767 | |
716 | =item * Erlang sends are synchronous, AEMP sends are asynchronous. |
768 | =item * Erlang sends are synchronous, AEMP sends are asynchronous. |
717 | |
769 | |
… | |
… | |
823 | L<AnyEvent::MP::Kernel> - more, lower-level, stuff. |
875 | L<AnyEvent::MP::Kernel> - more, lower-level, stuff. |
824 | |
876 | |
825 | L<AnyEvent::MP::Global> - network maintainance and port groups, to find |
877 | L<AnyEvent::MP::Global> - network maintainance and port groups, to find |
826 | your applications. |
878 | your applications. |
827 | |
879 | |
|
|
880 | L<AnyEvent::MP::LogCatcher> - simple service to display log messages from |
|
|
881 | all nodes. |
|
|
882 | |
828 | L<AnyEvent>. |
883 | L<AnyEvent>. |
829 | |
884 | |
830 | =head1 AUTHOR |
885 | =head1 AUTHOR |
831 | |
886 | |
832 | Marc Lehmann <schmorp@schmorp.de> |
887 | Marc Lehmann <schmorp@schmorp.de> |