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.40 by root, Sat Aug 8 00:22:16 2009 UTC vs.
Revision 1.64 by root, Fri Aug 28 00:58:44 2009 UTC

9 $NODE # contains this node's noderef 9 $NODE # contains this node's noderef
10 NODE # returns this node's noderef 10 NODE # returns this node's noderef
11 NODE $port # returns the noderef of the port 11 NODE $port # returns the noderef of the port
12 12
13 $SELF # receiving/own port id in rcv callbacks 13 $SELF # receiving/own port id in rcv callbacks
14
15 # initialise the node so it can send/receive messages
16 initialise_node;
14 17
15 # ports are message endpoints 18 # ports are message endpoints
16 19
17 # sending messages 20 # sending messages
18 snd $port, type => data...; 21 snd $port, type => data...;
19 snd $port, @msg; 22 snd $port, @msg;
20 snd @msg_with_first_element_being_a_port; 23 snd @msg_with_first_element_being_a_port;
21 24
22 # miniports 25 # creating/using ports, the simple way
23 my $miniport = port { my @msg = @_; 0 }; 26 my $simple_port = port { my @msg = @_; 0 };
24 27
25 # full ports 28 # creating/using ports, tagged message matching
26 my $port = port; 29 my $port = port;
27 rcv $port, smartmatch => $cb->(@msg);
28 rcv $port, ping => sub { snd $_[0], "pong"; 0 }; 30 rcv $port, ping => sub { snd $_[0], "pong"; 0 };
29 rcv $port, pong => sub { warn "pong received\n"; 0 }; 31 rcv $port, pong => sub { warn "pong received\n"; 0 };
30 32
31 # remote ports 33 # create a port on another node
32 my $port = spawn $node, $initfunc, @initdata; 34 my $port = spawn $node, $initfunc, @initdata;
33
34 # more, smarter, matches (_any_ is exported by this module)
35 rcv $port, [child_died => $pid] => sub { ...
36 rcv $port, [_any_, _any_, 3] => sub { .. $_[2] is 3
37 35
38 # monitoring 36 # monitoring
39 mon $port, $cb->(@msg) # callback is invoked on death 37 mon $port, $cb->(@msg) # callback is invoked on death
40 mon $port, $otherport # kill otherport on abnormal death 38 mon $port, $otherport # kill otherport on abnormal death
41 mon $port, $otherport, @msg # send message on death 39 mon $port, $otherport, @msg # send message on death
42 40
41=head1 CURRENT STATUS
42
43 AnyEvent::MP - stable API, should work
44 AnyEvent::MP::Intro - outdated
45 AnyEvent::MP::Kernel - WIP
46 AnyEvent::MP::Transport - mostly stable
47
48 stay tuned.
49
43=head1 DESCRIPTION 50=head1 DESCRIPTION
44 51
45This module (-family) implements a simple message passing framework. 52This module (-family) implements a simple message passing framework.
46 53
47Despite its simplicity, you can securely message other processes running 54Despite its simplicity, you can securely message other processes running
50For an introduction to this module family, see the L<AnyEvent::MP::Intro> 57For an introduction to this module family, see the L<AnyEvent::MP::Intro>
51manual page. 58manual page.
52 59
53At the moment, this module family is severly broken and underdocumented, 60At the moment, this module family is severly broken and underdocumented,
54so do not use. This was uploaded mainly to reserve the CPAN namespace - 61so do not use. This was uploaded mainly to reserve the CPAN namespace -
55stay tuned! The basic API should be finished, however. 62stay tuned!
56 63
57=head1 CONCEPTS 64=head1 CONCEPTS
58 65
59=over 4 66=over 4
60 67
61=item port 68=item port
62 69
63A port is something you can send messages to (with the C<snd> function). 70A port is something you can send messages to (with the C<snd> function).
64 71
65Some ports allow you to register C<rcv> handlers that can match specific 72Ports allow you to register C<rcv> handlers that can match all or just
66messages. All C<rcv> handlers will receive messages they match, messages 73some messages. Messages send to ports will not be queued, regardless of
67will not be queued. 74anything was listening for them or not.
68 75
69=item port id - C<noderef#portname> 76=item port ID - C<noderef#portname>
70 77
71A port id is normaly the concatenation of a noderef, a hash-mark (C<#>) as 78A port ID is the concatenation of a noderef, a hash-mark (C<#>) as
72separator, and a port name (a printable string of unspecified format). An 79separator, and a port name (a printable string of unspecified format). An
73exception is the the node port, whose ID is identical to its node 80exception is the the node port, whose ID is identical to its node
74reference. 81reference.
75 82
76=item node 83=item node
77 84
78A node is a single process containing at least one port - the node 85A node is a single process containing at least one port - the node port,
79port. You can send messages to node ports to find existing ports or to 86which provides nodes to manage each other remotely, and to create new
80create new ports, among other things. 87ports.
81 88
82Nodes are either private (single-process only), slaves (connected to a 89Nodes are either private (single-process only), slaves (can only talk to
83master node only) or public nodes (connectable from unrelated nodes). 90public nodes, but do not need an open port) or public nodes (connectable
91from any other node).
84 92
85=item noderef - C<host:port,host:port...>, C<id@noderef>, C<id> 93=item node ID - C<[a-za-Z0-9_\-.:]+>
86 94
87A node reference is a string that either simply identifies the node (for 95A node ID is a string that uniquely identifies the node within a
88private and slave nodes), or contains a recipe on how to reach a given 96network. Depending on the configuration used, node IDs can look like a
89node (for public nodes). 97hostname, a hostname and a port, or a random string. AnyEvent::MP itself
98doesn't interpret node IDs in any way.
90 99
91This recipe is simply a comma-separated list of C<address:port> pairs (for 100=item binds - C<ip:port>
92TCP/IP, other protocols might look different).
93 101
94Node references come in two flavours: resolved (containing only numerical 102Nodes can only talk to each other by creating some kind of connection to
95addresses) or unresolved (where hostnames are used instead of addresses). 103each other. To do this, nodes should listen on one or more local transport
104endpoints - binds. Currently, only standard C<ip:port> specifications can
105be used, which specify TCP ports to listen on.
96 106
97Before using an unresolved node reference in a message you first have to 107=item seeds - C<host:port>
98resolve it. 108
109When a node starts, it knows nothing about the network. To teach the node
110about the network it first has to contact some other node within the
111network. This node is called a seed.
112
113Seeds are transport endpoint(s) of as many nodes as one wants. Those nodes
114are expected to be long-running, and at least one of those should always
115be available. When nodes run out of connections (e.g. due to a network
116error), they try to re-establish connections to some seednodes again to
117join the network.
99 118
100=back 119=back
101 120
102=head1 VARIABLES/FUNCTIONS 121=head1 VARIABLES/FUNCTIONS
103 122
105 124
106=cut 125=cut
107 126
108package AnyEvent::MP; 127package AnyEvent::MP;
109 128
110use AnyEvent::MP::Base; 129use AnyEvent::MP::Kernel;
111 130
112use common::sense; 131use common::sense;
113 132
114use Carp (); 133use Carp ();
115 134
116use AE (); 135use AE ();
117 136
118use base "Exporter"; 137use base "Exporter";
119 138
120our $VERSION = '0.1'; 139our $VERSION = $AnyEvent::MP::Kernel::VERSION;
140
121our @EXPORT = qw( 141our @EXPORT = qw(
122 NODE $NODE *SELF node_of _any_ 142 NODE $NODE *SELF node_of after
123 resolve_node initialise_node 143 resolve_node initialise_node
124 snd rcv mon kil reg psub spawn 144 snd rcv mon mon_guard kil reg psub spawn
125 port 145 port
126); 146);
127 147
128our $SELF; 148our $SELF;
129 149
133 kil $SELF, die => $msg; 153 kil $SELF, die => $msg;
134} 154}
135 155
136=item $thisnode = NODE / $NODE 156=item $thisnode = NODE / $NODE
137 157
138The C<NODE> function returns, and the C<$NODE> variable contains 158The C<NODE> function returns, and the C<$NODE> variable contains the node
139the noderef of the local node. The value is initialised by a call 159ID of the node running in the current process. This value is initialised by
140to C<become_public> or C<become_slave>, after which all local port 160a call to C<initialise_node>.
141identifiers become invalid.
142 161
143=item $noderef = node_of $port 162=item $nodeid = node_of $port
144 163
145Extracts and returns the noderef from a portid or a noderef. 164Extracts and returns the node ID part from a port ID or a node ID.
146 165
147=item initialise_node $noderef, $seednode, $seednode... 166=item initialise_node $profile_name
148 167
149=item initialise_node "slave/", $master, $master...
150
151Before a node can talk to other nodes on the network it has to initialise 168Before a node can talk to other nodes on the network (i.e. enter
152itself - the minimum a node needs to know is it's own name, and optionally 169"distributed mode") it has to initialise itself - the minimum a node needs
153it should know the noderefs of some other nodes in the network. 170to know is its own name, and optionally it should know the addresses of
171some other nodes in the network to discover other nodes.
154 172
155This function initialises a node - it must be called exactly once (or 173This function initialises a node - it must be called exactly once (or
156never) before calling other AnyEvent::MP functions. 174never) before calling other AnyEvent::MP functions.
157 175
158All arguments are noderefs, which can be either resolved or unresolved. 176The first argument is a profile name. If it is C<undef> or missing, then
177the current nodename will be used instead (i.e. F<uname -n>).
159 178
160There are two types of networked nodes, public nodes and slave nodes: 179The function then looks up the profile in the aemp configuration (see the
180L<aemp> commandline utility).
161 181
162=over 4 182If the profile specifies a node ID, then this will become the node ID of
183this process. If not, then the profile name will be used as node ID. The
184special node ID of C<anon/> will be replaced by a random node ID.
163 185
164=item public nodes 186The next step is to look up the binds in the profile, followed by binding
187aemp protocol listeners on all binds specified (it is possible and valid
188to have no binds, meaning that the node cannot be contacted form the
189outside. This means the node cannot talk to other nodes that also have no
190binds, but it can still talk to all "normal" nodes).
165 191
166For public nodes, C<$noderef> must either be a (possibly unresolved) 192If the profile does not specify a binds list, then the node ID will be
167noderef, in which case it will be resolved, or C<undef> (or missing), in 193treated as if it were of the form C<host:port>, which will be resolved and
168which case the noderef will be guessed. 194used as binds list.
169 195
170Afterwards, the node will bind itself on all endpoints and try to connect 196Lastly, the seeds list from the profile is passed to the
171to all additional C<$seednodes> that are specified. Seednodes are optional 197L<AnyEvent::MP::Global> module, which will then use it to keep
172and can be used to quickly bootstrap the node into an existing network. 198connectivity with at least on of those seed nodes at any point in time.
173 199
174=item slave nodes 200Example: become a distributed node listening on the guessed noderef, or
175 201the one specified via C<aemp> for the current node. This should be the
176When the C<$noderef> is the special string C<slave/>, then the node will 202most common form of invocation for "daemon"-type nodes.
177become a slave node. Slave nodes cannot be contacted from outside and will
178route most of their traffic to the master node that they attach to.
179
180At least one additional noderef is required: The node will try to connect
181to all of them and will become a slave attached to the first node it can
182successfully connect to.
183
184=back
185
186This function will block until all nodes have been resolved and, for slave
187nodes, until it has successfully established a connection to a master
188server.
189
190Example: become a public node listening on the default node.
191 203
192 initialise_node; 204 initialise_node;
193 205
194Example: become a public node, and try to contact some well-known master 206Example: become an anonymous node. This form is often used for commandline
195servers to become part of the network. 207clients.
196 208
197 initialise_node undef, "master1", "master2";
198
199Example: become a public node listening on port C<4041>.
200
201 initialise_node 4041; 209 initialise_node "anon/";
202 210
203Example: become a public node, only visible on localhost port 4044. 211Example: become a distributed node. If there is no profile of the given
212name, or no binds list was specified, resolve C<localhost:4044> and bind
213on the resulting addresses.
204 214
205 initialise_node "locahost:4044"; 215 initialise_node "localhost:4044";
206
207Example: become a slave node to any of the specified master servers.
208
209 initialise_node "slave/", "master1", "192.168.13.17", "mp.example.net";
210
211=item $cv = resolve_node $noderef
212
213Takes an unresolved node reference that may contain hostnames and
214abbreviated IDs, resolves all of them and returns a resolved node
215reference.
216
217In addition to C<address:port> pairs allowed in resolved noderefs, the
218following forms are supported:
219
220=over 4
221
222=item the empty string
223
224An empty-string component gets resolved as if the default port (4040) was
225specified.
226
227=item naked port numbers (e.g. C<1234>)
228
229These are resolved by prepending the local nodename and a colon, to be
230further resolved.
231
232=item hostnames (e.g. C<localhost:1234>, C<localhost>)
233
234These are resolved by using AnyEvent::DNS to resolve them, optionally
235looking up SRV records for the C<aemp=4040> port, if no port was
236specified.
237
238=back
239 216
240=item $SELF 217=item $SELF
241 218
242Contains the current port id while executing C<rcv> callbacks or C<psub> 219Contains the current port id while executing C<rcv> callbacks or C<psub>
243blocks. 220blocks.
251=item snd $port, type => @data 228=item snd $port, type => @data
252 229
253=item snd $port, @msg 230=item snd $port, @msg
254 231
255Send the given message to the given port ID, which can identify either 232Send the given message to the given port ID, which can identify either
256a local or a remote port, and can be either a string or soemthignt hat 233a local or a remote port, and must be a port ID.
257stringifies a sa port ID (such as a port object :).
258 234
259While the message can be about anything, it is highly recommended to use a 235While the message can be about anything, it is highly recommended to use a
260string as first element (a portid, or some word that indicates a request 236string as first element (a port ID, or some word that indicates a request
261type etc.). 237type etc.).
262 238
263The message data effectively becomes read-only after a call to this 239The message data effectively becomes read-only after a call to this
264function: modifying any argument is not allowed and can cause many 240function: modifying any argument is not allowed and can cause many
265problems. 241problems.
270that Storable can serialise and deserialise is allowed, and for the local 246that Storable can serialise and deserialise is allowed, and for the local
271node, anything can be passed. 247node, anything can be passed.
272 248
273=item $local_port = port 249=item $local_port = port
274 250
275Create a new local port object that can be used either as a pattern 251Create a new local port object and returns its port ID. Initially it has
276matching port ("full port") or a single-callback port ("miniport"), 252no callbacks set and will throw an error when it receives messages.
277depending on how C<rcv> callbacks are bound to the object.
278 253
279=item $port = port { my @msg = @_; $finished } 254=item $local_port = port { my @msg = @_ }
280 255
281Creates a "miniport", that is, a very lightweight port without any pattern 256Creates a new local port, and returns its ID. Semantically the same as
282matching behind it, and returns its ID. Semantically the same as creating
283a port and calling C<rcv $port, $callback> on it. 257creating a port and calling C<rcv $port, $callback> on it.
284 258
285The block will be called for every message received on the port. When the 259The block will be called for every message received on the port, with the
286callback returns a true value its job is considered "done" and the port 260global variable C<$SELF> set to the port ID. Runtime errors will cause the
287will be destroyed. Otherwise it will stay alive. 261port to be C<kil>ed. The message will be passed as-is, no extra argument
262(i.e. no port ID) will be passed to the callback.
288 263
289The message will be passed as-is, no extra argument (i.e. no port id) will 264If you want to stop/destroy the port, simply C<kil> it:
290be passed to the callback.
291 265
292If you need the local port id in the callback, this works nicely: 266 my $port = port {
293 267 my @msg = @_;
294 my $port; $port = port { 268 ...
295 snd $otherport, reply => $port; 269 kil $SELF;
296 }; 270 };
297 271
298=cut 272=cut
299 273
300sub rcv($@); 274sub rcv($@);
275
276sub _kilme {
277 die "received message on port without callback";
278}
301 279
302sub port(;&) { 280sub port(;&) {
303 my $id = "$UNIQ." . $ID++; 281 my $id = "$UNIQ." . $ID++;
304 my $port = "$NODE#$id"; 282 my $port = "$NODE#$id";
305 283
306 if (@_) { 284 rcv $port, shift || \&_kilme;
307 rcv $port, shift;
308 } else {
309 $PORT{$id} = sub { }; # nop
310 }
311 285
312 $port 286 $port
313} 287}
314 288
315=item reg $port, $name
316
317=item reg $name
318
319Registers the given port (or C<$SELF><<< if missing) under the name
320C<$name>. If the name already exists it is replaced.
321
322A port can only be registered under one well known name.
323
324A port automatically becomes unregistered when it is killed.
325
326=cut
327
328sub reg(@) {
329 my $port = @_ > 1 ? shift : $SELF || Carp::croak 'reg: called with one argument only, but $SELF not set,';
330
331 $REG{$_[0]} = $port;
332}
333
334=item rcv $port, $callback->(@msg) 289=item rcv $local_port, $callback->(@msg)
335 290
336Replaces the callback on the specified miniport (after converting it to 291Replaces the default callback on the specified port. There is no way to
337one if required). 292remove the default callback: use C<sub { }> to disable it, or better
338 293C<kil> the port when it is no longer needed.
339=item rcv $port, tagstring => $callback->(@msg), ...
340
341=item rcv $port, $smartmatch => $callback->(@msg), ...
342
343=item rcv $port, [$smartmatch...] => $callback->(@msg), ...
344
345Register callbacks to be called on matching messages on the given full
346port (after converting it to one if required) and return the port.
347
348The callback has to return a true value when its work is done, after
349which is will be removed, or a false value in which case it will stay
350registered.
351 294
352The global C<$SELF> (exported by this module) contains C<$port> while 295The global C<$SELF> (exported by this module) contains C<$port> while
353executing the callback. 296executing the callback. Runtime errors during callback execution will
297result in the port being C<kil>ed.
354 298
355Runtime errors during callback execution will result in the port being 299The default callback received all messages not matched by a more specific
356C<kil>ed. 300C<tag> match.
357 301
358If the match is an array reference, then it will be matched against the 302=item rcv $local_port, tag => $callback->(@msg_without_tag), ...
359first elements of the message, otherwise only the first element is being
360matched.
361 303
362Any element in the match that is specified as C<_any_> (a function 304Register (or replace) callbacks to be called on messages starting with the
363exported by this module) matches any single element of the message. 305given tag on the given port (and return the port), or unregister it (when
306C<$callback> is C<$undef> or missing). There can only be one callback
307registered for each tag.
364 308
365While not required, it is highly recommended that the first matching 309The original message will be passed to the callback, after the first
366element is a string identifying the message. The one-string-only match is 310element (the tag) has been removed. The callback will use the same
367also the most efficient match (by far). 311environment as the default callback (see above).
368 312
369Example: create a port and bind receivers on it in one go. 313Example: create a port and bind receivers on it in one go.
370 314
371 my $port = rcv port, 315 my $port = rcv port,
372 msg1 => sub { ...; 0 }, 316 msg1 => sub { ... },
373 msg2 => sub { ...; 0 }, 317 msg2 => sub { ... },
374 ; 318 ;
375 319
376Example: create a port, bind receivers and send it in a message elsewhere 320Example: create a port, bind receivers and send it in a message elsewhere
377in one go: 321in one go:
378 322
379 snd $otherport, reply => 323 snd $otherport, reply =>
380 rcv port, 324 rcv port,
381 msg1 => sub { ...; 0 }, 325 msg1 => sub { ... },
382 ... 326 ...
383 ; 327 ;
328
329Example: temporarily register a rcv callback for a tag matching some port
330(e.g. for a rpc reply) and unregister it after a message was received.
331
332 rcv $port, $otherport => sub {
333 my @reply = @_;
334
335 rcv $SELF, $otherport;
336 };
384 337
385=cut 338=cut
386 339
387sub rcv($@) { 340sub rcv($@) {
388 my $port = shift; 341 my $port = shift;
389 my ($noderef, $portid) = split /#/, $port, 2; 342 my ($noderef, $portid) = split /#/, $port, 2;
390 343
391 ($NODE{$noderef} || add_node $noderef) == $NODE{""} 344 $NODE{$noderef} == $NODE{""}
392 or Carp::croak "$port: rcv can only be called on local ports, caught"; 345 or Carp::croak "$port: rcv can only be called on local ports, caught";
393 346
394 if (@_ == 1) { 347 while (@_) {
348 if (ref $_[0]) {
349 if (my $self = $PORT_DATA{$portid}) {
350 "AnyEvent::MP::Port" eq ref $self
351 or Carp::croak "$port: rcv can only be called on message matching ports, caught";
352
353 $self->[2] = shift;
354 } else {
395 my $cb = shift; 355 my $cb = shift;
396 delete $PORT_DATA{$portid};
397 $PORT{$portid} = sub { 356 $PORT{$portid} = sub {
398 local $SELF = $port; 357 local $SELF = $port;
399 eval { 358 eval { &$cb }; _self_die if $@;
400 &$cb 359 };
401 and kil $port;
402 }; 360 }
403 _self_die if $@; 361 } elsif (defined $_[0]) {
404 };
405 } else {
406 my $self = $PORT_DATA{$portid} ||= do { 362 my $self = $PORT_DATA{$portid} ||= do {
407 my $self = bless { 363 my $self = bless [$PORT{$port} || sub { }, { }, $port], "AnyEvent::MP::Port";
408 id => $port,
409 }, "AnyEvent::MP::Port";
410 364
411 $PORT{$portid} = sub { 365 $PORT{$portid} = sub {
412 local $SELF = $port; 366 local $SELF = $port;
413 367
414 eval {
415 for (@{ $self->{rc0}{$_[0]} }) { 368 if (my $cb = $self->[1]{$_[0]}) {
416 $_ && &{$_->[0]} 369 shift;
417 && undef $_; 370 eval { &$cb }; _self_die if $@;
418 } 371 } else {
419
420 for (@{ $self->{rcv}{$_[0]} }) {
421 $_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1]
422 && &{$_->[0]} 372 &{ $self->[0] };
423 && undef $_;
424 }
425
426 for (@{ $self->{any} }) {
427 $_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1]
428 && &{$_->[0]}
429 && undef $_;
430 } 373 }
431 }; 374 };
432 _self_die if $@; 375
376 $self
433 }; 377 };
434 378
435 $self
436 };
437
438 "AnyEvent::MP::Port" eq ref $self 379 "AnyEvent::MP::Port" eq ref $self
439 or Carp::croak "$port: rcv can only be called on message matching ports, caught"; 380 or Carp::croak "$port: rcv can only be called on message matching ports, caught";
440 381
441 while (@_) {
442 my ($match, $cb) = splice @_, 0, 2; 382 my ($tag, $cb) = splice @_, 0, 2;
443 383
444 if (!ref $match) { 384 if (defined $cb) {
445 push @{ $self->{rc0}{$match} }, [$cb]; 385 $self->[1]{$tag} = $cb;
446 } elsif (("ARRAY" eq ref $match && !ref $match->[0])) {
447 my ($type, @match) = @$match;
448 @match
449 ? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match]
450 : push @{ $self->{rc0}{$match->[0]} }, [$cb];
451 } else { 386 } else {
452 push @{ $self->{any} }, [$cb, $match]; 387 delete $self->[1]{$tag};
453 } 388 }
454 } 389 }
455 } 390 }
456 391
457 $port 392 $port
501 436
502=item $guard = mon $port 437=item $guard = mon $port
503 438
504=item $guard = mon $port, $rcvport, @msg 439=item $guard = mon $port, $rcvport, @msg
505 440
506Monitor the given port and do something when the port is killed, and 441Monitor the given port and do something when the port is killed or
507optionally return a guard that can be used to stop monitoring again. 442messages to it were lost, and optionally return a guard that can be used
443to stop monitoring again.
444
445C<mon> effectively guarantees that, in the absence of hardware failures,
446that after starting the monitor, either all messages sent to the port
447will arrive, or the monitoring action will be invoked after possible
448message loss has been detected. No messages will be lost "in between"
449(after the first lost message no further messages will be received by the
450port). After the monitoring action was invoked, further messages might get
451delivered again.
452
453Note that monitoring-actions are one-shot: once released, they are removed
454and will not trigger again.
508 455
509In the first form (callback), the callback is simply called with any 456In the first form (callback), the callback is simply called with any
510number of C<@reason> elements (no @reason means that the port was deleted 457number of C<@reason> elements (no @reason means that the port was deleted
511"normally"). Note also that I<< the callback B<must> never die >>, so use 458"normally"). Note also that I<< the callback B<must> never die >>, so use
512C<eval> if unsure. 459C<eval> if unsure.
513 460
514In the second form (another port given), the other port (C<$rcvport) 461In the second form (another port given), the other port (C<$rcvport>)
515will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on 462will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on
516"normal" kils nothing happens, while under all other conditions, the other 463"normal" kils nothing happens, while under all other conditions, the other
517port is killed with the same reason. 464port is killed with the same reason.
518 465
519The third form (kill self) is the same as the second form, except that 466The third form (kill self) is the same as the second form, except that
546sub mon { 493sub mon {
547 my ($noderef, $port) = split /#/, shift, 2; 494 my ($noderef, $port) = split /#/, shift, 2;
548 495
549 my $node = $NODE{$noderef} || add_node $noderef; 496 my $node = $NODE{$noderef} || add_node $noderef;
550 497
551 my $cb = @_ ? $_[0] : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,'; 498 my $cb = @_ ? shift : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,';
552 499
553 unless (ref $cb) { 500 unless (ref $cb) {
554 if (@_) { 501 if (@_) {
555 # send a kill info message 502 # send a kill info message
556 my (@msg) = @_; 503 my (@msg) = ($cb, @_);
557 $cb = sub { snd @msg, @_ }; 504 $cb = sub { snd @msg, @_ };
558 } else { 505 } else {
559 # simply kill other port 506 # simply kill other port
560 my $port = $cb; 507 my $port = $cb;
561 $cb = sub { kil $port, @_ if @_ }; 508 $cb = sub { kil $port, @_ if @_ };
673 my $id = "$RUNIQ." . $ID++; 620 my $id = "$RUNIQ." . $ID++;
674 621
675 $_[0] =~ /::/ 622 $_[0] =~ /::/
676 or Carp::croak "spawn init function must be a fully-qualified name, caught"; 623 or Carp::croak "spawn init function must be a fully-qualified name, caught";
677 624
678 ($NODE{$noderef} || add_node $noderef) 625 snd_to_func $noderef, "AnyEvent::MP::_spawn" => $id, @_;
679 ->send (["", "AnyEvent::MP::_spawn" => $id, @_]);
680 626
681 "$noderef#$id" 627 "$noderef#$id"
682} 628}
683 629
684=back 630=item after $timeout, @msg
685 631
686=head1 NODE MESSAGES 632=item after $timeout, $callback
687 633
688Nodes understand the following messages sent to them. Many of them take 634Either sends the given message, or call the given callback, after the
689arguments called C<@reply>, which will simply be used to compose a reply 635specified number of seconds.
690message - C<$reply[0]> is the port to reply to, C<$reply[1]> the type and
691the remaining arguments are simply the message data.
692 636
693While other messages exist, they are not public and subject to change. 637This is simply a utility function that come sin handy at times.
694 638
695=over 4
696
697=cut 639=cut
698 640
699=item lookup => $name, @reply 641sub after($@) {
642 my ($timeout, @action) = @_;
700 643
701Replies with the port ID of the specified well-known port, or C<undef>. 644 my $t; $t = AE::timer $timeout, 0, sub {
702 645 undef $t;
703=item devnull => ... 646 ref $action[0]
704 647 ? $action[0]()
705Generic data sink/CPU heat conversion. 648 : snd @action;
706 649 };
707=item relay => $port, @msg 650}
708
709Simply forwards the message to the given port.
710
711=item eval => $string[ @reply]
712
713Evaluates the given string. If C<@reply> is given, then a message of the
714form C<@reply, $@, @evalres> is sent.
715
716Example: crash another node.
717
718 snd $othernode, eval => "exit";
719
720=item time => @reply
721
722Replies the the current node time to C<@reply>.
723
724Example: tell the current node to send the current time to C<$myport> in a
725C<timereply> message.
726
727 snd $NODE, time => $myport, timereply => 1, 2;
728 # => snd $myport, timereply => 1, 2, <time>
729 651
730=back 652=back
731 653
732=head1 AnyEvent::MP vs. Distributed Erlang 654=head1 AnyEvent::MP vs. Distributed Erlang
733 655
752convenience functionality. 674convenience functionality.
753 675
754This means that AEMP requires a less tightly controlled environment at the 676This means that AEMP requires a less tightly controlled environment at the
755cost of longer node references and a slightly higher management overhead. 677cost of longer node references and a slightly higher management overhead.
756 678
679=item * Erlang has a "remote ports are like local ports" philosophy, AEMP
680uses "local ports are like remote ports".
681
682The failure modes for local ports are quite different (runtime errors
683only) then for remote ports - when a local port dies, you I<know> it dies,
684when a connection to another node dies, you know nothing about the other
685port.
686
687Erlang pretends remote ports are as reliable as local ports, even when
688they are not.
689
690AEMP encourages a "treat remote ports differently" philosophy, with local
691ports being the special case/exception, where transport errors cannot
692occur.
693
757=item * Erlang uses processes and a mailbox, AEMP does not queue. 694=item * Erlang uses processes and a mailbox, AEMP does not queue.
758 695
759Erlang uses processes that selctively receive messages, and therefore 696Erlang uses processes that selectively receive messages, and therefore
760needs a queue. AEMP is event based, queuing messages would serve no useful 697needs a queue. AEMP is event based, queuing messages would serve no
761purpose. 698useful purpose. For the same reason the pattern-matching abilities of
699AnyEvent::MP are more limited, as there is little need to be able to
700filter messages without dequeing them.
762 701
763(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP). 702(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).
764 703
765=item * Erlang sends are synchronous, AEMP sends are asynchronous. 704=item * Erlang sends are synchronous, AEMP sends are asynchronous.
766 705
767Sending messages in Erlang is synchronous and blocks the process. AEMP 706Sending messages in Erlang is synchronous and blocks the process (and
768sends are immediate, connection establishment is handled in the 707so does not need a queue that can overflow). AEMP sends are immediate,
769background. 708connection establishment is handled in the background.
770 709
771=item * Erlang can silently lose messages, AEMP cannot. 710=item * Erlang suffers from silent message loss, AEMP does not.
772 711
773Erlang makes few guarantees on messages delivery - messages can get lost 712Erlang makes few guarantees on messages delivery - messages can get lost
774without any of the processes realising it (i.e. you send messages a, b, 713without any of the processes realising it (i.e. you send messages a, b,
775and c, and the other side only receives messages a and c). 714and c, and the other side only receives messages a and c).
776 715
788eventually be killed - it cannot happen that a node detects a port as dead 727eventually be killed - it cannot happen that a node detects a port as dead
789and then later sends messages to it, finding it is still alive. 728and then later sends messages to it, finding it is still alive.
790 729
791=item * Erlang can send messages to the wrong port, AEMP does not. 730=item * Erlang can send messages to the wrong port, AEMP does not.
792 731
793In Erlang it is quite possible that a node that restarts reuses a process 732In Erlang it is quite likely that a node that restarts reuses a process ID
794ID known to other nodes for a completely different process, causing 733known to other nodes for a completely different process, causing messages
795messages destined for that process to end up in an unrelated process. 734destined for that process to end up in an unrelated process.
796 735
797AEMP never reuses port IDs, so old messages or old port IDs floating 736AEMP never reuses port IDs, so old messages or old port IDs floating
798around in the network will not be sent to an unrelated port. 737around in the network will not be sent to an unrelated port.
799 738
800=item * Erlang uses unprotected connections, AEMP uses secure 739=item * Erlang uses unprotected connections, AEMP uses secure
836This also saves round-trips and avoids sending messages to the wrong port 775This also saves round-trips and avoids sending messages to the wrong port
837(hard to do in Erlang). 776(hard to do in Erlang).
838 777
839=back 778=back
840 779
780=head1 RATIONALE
781
782=over 4
783
784=item Why strings for ports and noderefs, why not objects?
785
786We considered "objects", but found that the actual number of methods
787thatc an be called are very low. Since port IDs and noderefs travel over
788the network frequently, the serialising/deserialising would add lots of
789overhead, as well as having to keep a proxy object.
790
791Strings can easily be printed, easily serialised etc. and need no special
792procedures to be "valid".
793
794And a a miniport consists of a single closure stored in a global hash - it
795can't become much cheaper.
796
797=item Why favour JSON, why not real serialising format such as Storable?
798
799In fact, any AnyEvent::MP node will happily accept Storable as framing
800format, but currently there is no way to make a node use Storable by
801default.
802
803The default framing protocol is JSON because a) JSON::XS is many times
804faster for small messages and b) most importantly, after years of
805experience we found that object serialisation is causing more problems
806than it gains: Just like function calls, objects simply do not travel
807easily over the network, mostly because they will always be a copy, so you
808always have to re-think your design.
809
810Keeping your messages simple, concentrating on data structures rather than
811objects, will keep your messages clean, tidy and efficient.
812
813=back
814
841=head1 SEE ALSO 815=head1 SEE ALSO
842 816
843L<AnyEvent>. 817L<AnyEvent>.
844 818
845=head1 AUTHOR 819=head1 AUTHOR

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines