ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/AnyEvent-MP/MP.pm

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.31 by root, Wed Aug 5 19:55:58 2009 UTC vs.
Revision 1.132 by root, Sat Mar 10 20:34:11 2012 UTC

1	=head1 NAME	1	=head1 NAME
2		2
3	AnyEvent::MP - multi-processing/message-passing framework	3	AnyEvent::MP - erlang-style multi-processing/message-passing framework
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
		12	$SELF # receiving/own port id in rcv callbacks
		13
		14	# initialise the node so it can send/receive messages
		15	configure;
		16
		17	# ports are message destinations
		18
		19	# sending messages
13	snd $port, type => data...;	20	snd $port, type => data...;
		21	snd $port, @msg;
		22	snd @msg_with_first_element_being_a_port;
14		23
15	$SELF # receiving/own port id in rcv callbacks	24	# creating/using ports, the simple way
		25	my $simple_port = port { my @msg = @_ };
16		26
17	rcv $port, smartmatch => $cb->($port, @msg);	27	# creating/using ports, tagged message matching
18		28	my $port = port;
19	# examples:
20	rcv $port2, ping => sub { snd $_[0], "pong"; 0 };	29	rcv $port, ping => sub { snd $_[0], "pong" };
21	rcv $port1, pong => sub { warn "pong received\n" };	30	rcv $port, pong => sub { warn "pong received\n" };
22	snd $port2, ping => $port1;
23		31
24	# more, smarter, matches (_any_ is exported by this module)	32	# create a port on another node
25	rcv $port, [child_died => $pid] => sub { ...	33	my $port = spawn $node, $initfunc, @initdata;
26	rcv $port, [_any_, _any_, 3] => sub { .. $_[2] is 3	34
		35	# destroy a port again
		36	kil $port; # "normal" kill
		37	kil $port, my_error => "everything is broken"; # error kill
		38
		39	# monitoring
		40	mon $port, $cb->(@msg) # callback is invoked on death
		41	mon $port, $localport # kill localport on abnormal death
		42	mon $port, $localport, @msg # send message on death
		43
		44	# temporarily execute code in port context
		45	peval $port, sub { die "kill the port!" };
		46
		47	# execute callbacks in $SELF port context
		48	my $timer = AE::timer 1, 0, psub {
		49	die "kill the port, delayed";
		50	};
		51
		52	=head1 CURRENT STATUS
		53
		54	bin/aemp - stable.
		55	AnyEvent::MP - stable API, should work.
		56	AnyEvent::MP::Intro - explains most concepts.
		57	AnyEvent::MP::Kernel - mostly stable API.
		58	AnyEvent::MP::Global - stable API.
27		59
28	=head1 DESCRIPTION	60	=head1 DESCRIPTION
29		61
30	This module (-family) implements a simple message passing framework.	62	This module (-family) implements a simple message passing framework.
31		63
32	Despite its simplicity, you can securely message other processes running	64	Despite its simplicity, you can securely message other processes running
33	on the same or other hosts.	65	on the same or other hosts, and you can supervise entities remotely.
34		66
35	For an introduction to this module family, see the L<AnyEvent::MP::Intro>	67	For an introduction to this module family, see the L<AnyEvent::MP::Intro>
36	manual page.	68	manual page and the examples under F<eg/>.
37
38	At the moment, this module family is severly broken and underdocumented,
39	so do not use. This was uploaded mainly to reserve the CPAN namespace -
40	stay tuned! The basic API should be finished, however.
41		69
42	=head1 CONCEPTS	70	=head1 CONCEPTS
43		71
44	=over 4	72	=over 4
45		73
46	=item port	74	=item port
47		75
48	A port is something you can send messages to (with the C<snd> function).	76	Not to be confused with a TCP port, a "port" is something you can send
		77	messages to (with the C<snd> function).
49		78
50	Some ports allow you to register C<rcv> handlers that can match specific	79	Ports allow you to register C<rcv> handlers that can match all or just
51	messages. All C<rcv> handlers will receive messages they match, messages	80	some messages. Messages send to ports will not be queued, regardless of
52	will not be queued.	81	anything was listening for them or not.
53		82
		83	Ports are represented by (printable) strings called "port IDs".
		84
54	=item port id - C<noderef#portname>	85	=item port ID - C<nodeid#portname>
55		86
56	A port id is normaly the concatenation of a noderef, a hash-mark (C<#>) as	87	A port ID is the concatenation of a node ID, a hash-mark (C<#>)
57	separator, and a port name (a printable string of unspecified format). An	88	as separator, and a port name (a printable string of unspecified
58	exception is the the node port, whose ID is identical to its node	89	format created by AnyEvent::MP).
59	reference.
60		90
61	=item node	91	=item node
62		92
63	A node is a single process containing at least one port - the node	93	A node is a single process containing at least one port - the node port,
64	port. You can send messages to node ports to find existing ports or to	94	which enables nodes to manage each other remotely, and to create new
65	create new ports, among other things.	95	ports.
66		96
67	Nodes are either private (single-process only), slaves (connected to a	97	Nodes are either public (have one or more listening ports) or private
68	master node only) or public nodes (connectable from unrelated nodes).	98	(no listening ports). Private nodes cannot talk to other private nodes
		99	currently, but all nodes can talk to public nodes.
69		100
70	=item noderef - C<host:port,host:port...>, C<id@noderef>, C<id>	101	Nodes is represented by (printable) strings called "node IDs".
71		102
72	A node reference is a string that either simply identifies the node (for	103	=item node ID - C<[A-Za-z0-9_\-.:]*>
73	private and slave nodes), or contains a recipe on how to reach a given
74	node (for public nodes).
75		104
76	This recipe is simply a comma-separated list of C<address:port> pairs (for	105	A node ID is a string that uniquely identifies the node within a
77	TCP/IP, other protocols might look different).	106	network. Depending on the configuration used, node IDs can look like a
		107	hostname, a hostname and a port, or a random string. AnyEvent::MP itself
		108	doesn't interpret node IDs in any way except to uniquely identify a node.
78		109
79	Node references come in two flavours: resolved (containing only numerical	110	=item binds - C<ip:port>
80	addresses) or unresolved (where hostnames are used instead of addresses).
81		111
82	Before using an unresolved node reference in a message you first have to	112	Nodes can only talk to each other by creating some kind of connection to
83	resolve it.	113	each other. To do this, nodes should listen on one or more local transport
		114	endpoints - binds.
		115
		116	Currently, only standard C<ip:port> specifications can be used, which
		117	specify TCP ports to listen on. So a bind is basically just a tcp socket
		118	in listening mode thta accepts conenctions form other nodes.
		119
		120	=item seed nodes
		121
		122	When a node starts, it knows nothing about the network it is in - it
		123	needs to connect to at least one other node that is already in the
		124	network. These other nodes are called "seed nodes".
		125
		126	Seed nodes themselves are not special - they are seed nodes only because
		127	some other node I<uses> them as such, but any node can be used as seed
		128	node for other nodes, and eahc node cna use a different set of seed nodes.
		129
		130	In addition to discovering the network, seed nodes are also used to
		131	maintain the network - all nodes using the same seed node form are part of
		132	the same network. If a network is split into multiple subnets because e.g.
		133	the network link between the parts goes down, then using the same seed
		134	nodes for all nodes ensures that eventually the subnets get merged again.
		135
		136	Seed nodes are expected to be long-running, and at least one seed node
		137	should always be available. They should also be relatively responsive - a
		138	seed node that blocks for long periods will slow down everybody else.
		139
		140	For small networks, it's best if every node uses the same set of seed
		141	nodes. For large networks, it can be useful to specify "regional" seed
		142	nodes for most nodes in an area, and use all seed nodes as seed nodes for
		143	each other. What's important is that all seed nodes connections form a
		144	complete graph, so that the network cannot split into separate subnets
		145	forever.
		146
		147	Seed nodes are represented by seed IDs.
		148
		149	=item seed IDs - C<host:port>
		150
		151	Seed IDs are transport endpoint(s) (usually a hostname/IP address and a
		152	TCP port) of nodes that should be used as seed nodes.
		153
		154	=item global nodes
		155
		156	An AEMP network needs a discovery service - nodes need to know how to
		157	connect to other nodes they only know by name. In addition, AEMP offers a
		158	distributed "group database", which maps group names to a list of strings
		159	- for example, to register worker ports.
		160
		161	A network needs at least one global node to work, and allows every node to
		162	be a global node.
		163
		164	Any node that loads the L<AnyEvent::MP::Global> module becomes a global
		165	node and tries to keep connections to all other nodes. So while it can
		166	make sense to make every node "global" in small networks, it usually makes
		167	sense to only make seed nodes into global nodes in large networks (nodes
		168	keep connections to seed nodes and global nodes, so makign them the same
		169	reduces overhead).
84		170
85	=back	171	=back
86		172
87	=head1 VARIABLES/FUNCTIONS	173	=head1 VARIABLES/FUNCTIONS
88		174
…		…
90		176
91	=cut	177	=cut
92		178
93	package AnyEvent::MP;	179	package AnyEvent::MP;
94		180
		181	use AnyEvent::MP::Config ();
95	use AnyEvent::MP::Base;	182	use AnyEvent::MP::Kernel;
		183	use AnyEvent::MP::Kernel qw(%NODE %PORT %PORT_DATA $UNIQ $RUNIQ $ID);
96		184
97	use common::sense;	185	use common::sense;
98		186
99	use Carp ();	187	use Carp ();
100		188
101	use AE ();	189	use AE ();
		190	use Guard ();
102		191
103	use base "Exporter";	192	use base "Exporter";
104		193
105	our $VERSION = '0.1';	194	our $VERSION = $AnyEvent::MP::Config::VERSION;
		195
106	our @EXPORT = qw(	196	our @EXPORT = qw(
107	NODE $NODE *SELF node_of _any_	197	NODE $NODE *SELF node_of after
108	resolve_node initialise_node	198	configure
109	snd rcv mon kil reg psub	199	snd rcv mon mon_guard kil psub peval spawn cal
110	port	200	port
		201	db_set db_del db_reg
		202	db_mon db_family db_keys db_values
111	);	203	);
112		204
113	our $SELF;	205	our $SELF;
114		206
115	sub _self_die() {	207	sub _self_die() {
…		…
118	kil $SELF, die => $msg;	210	kil $SELF, die => $msg;
119	}	211	}
120		212
121	=item $thisnode = NODE / $NODE	213	=item $thisnode = NODE / $NODE
122		214
123	The C<NODE> function returns, and the C<$NODE> variable contains	215	The C<NODE> function returns, and the C<$NODE> variable contains, the node
124	the noderef of the local node. The value is initialised by a call	216	ID of the node running in the current process. This value is initialised by
125	to C<become_public> or C<become_slave>, after which all local port	217	a call to C<configure>.
126	identifiers become invalid.
127		218
128	=item $noderef = node_of $portid	219	=item $nodeid = node_of $port
129		220
130	Extracts and returns the noderef from a portid or a noderef.	221	Extracts and returns the node ID from a port ID or a node ID.
131		222
132	=item $cv = resolve_node $noderef	223	=item configure $profile, key => value...
133		224
134	Takes an unresolved node reference that may contain hostnames and	225	=item configure key => value...
135	abbreviated IDs, resolves all of them and returns a resolved node
136	reference.
137		226
138	In addition to C<address:port> pairs allowed in resolved noderefs, the	227	Before a node can talk to other nodes on the network (i.e. enter
139	following forms are supported:	228	"distributed mode") it has to configure itself - the minimum a node needs
		229	to know is its own name, and optionally it should know the addresses of
		230	some other nodes in the network to discover other nodes.
		231
		232	This function configures a node - it must be called exactly once (or
		233	never) before calling other AnyEvent::MP functions.
		234
		235	The key/value pairs are basically the same ones as documented for the
		236	F<aemp> command line utility (sans the set/del prefix), with these additions:
140		237
141	=over 4	238	=over 4
142		239
143	=item the empty string	240	=item norc => $boolean (default false)
144		241
145	An empty-string component gets resolved as if the default port (4040) was	242	If true, then the rc file (e.g. F<~/.perl-anyevent-mp>) will I<not>
146	specified.	243	be consulted - all configuraiton options must be specified in the
		244	C<configure> call.
147		245
148	=item naked port numbers (e.g. C<1234>)	246	=item force => $boolean (default false)
149		247
150	These are resolved by prepending the local nodename and a colon, to be	248	IF true, then the values specified in the C<configure> will take
151	further resolved.	249	precedence over any values configured via the rc file. The default is for
		250	the rc file to override any options specified in the program.
152		251
153	=item hostnames (e.g. C<localhost:1234>, C<localhost>)	252	=item secure => $pass->($nodeid)
154		253
155	These are resolved by using AnyEvent::DNS to resolve them, optionally	254	In addition to specifying a boolean, you can specify a code reference that
156	looking up SRV records for the C<aemp=4040> port, if no port was	255	is called for every remote execution attempt - the execution request is
157	specified.	256	granted iff the callback returns a true value.
		257
		258	See F<semp setsecure> for more info.
158		259
159	=back	260	=back
		261
		262	=over 4
		263
		264	=item step 1, gathering configuration from profiles
		265
		266	The function first looks up a profile in the aemp configuration (see the
		267	L<aemp> commandline utility). The profile name can be specified via the
		268	named C<profile> parameter or can simply be the first parameter). If it is
		269	missing, then the nodename (F<uname -n>) will be used as profile name.
		270
		271	The profile data is then gathered as follows:
		272
		273	First, all remaining key => value pairs (all of which are conveniently
		274	undocumented at the moment) will be interpreted as configuration
		275	data. Then they will be overwritten by any values specified in the global
		276	default configuration (see the F<aemp> utility), then the chain of
		277	profiles chosen by the profile name (and any C<parent> attributes).
		278
		279	That means that the values specified in the profile have highest priority
		280	and the values specified directly via C<configure> have lowest priority,
		281	and can only be used to specify defaults.
		282
		283	If the profile specifies a node ID, then this will become the node ID of
		284	this process. If not, then the profile name will be used as node ID, with
		285	a unique randoms tring (C</%u>) appended.
		286
		287	The node ID can contain some C<%> sequences that are expanded: C<%n>
		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>.
		292
		293	=item step 2, bind listener sockets
		294
		295	The next step is to look up the binds in the profile, followed by binding
		296	aemp protocol listeners on all binds specified (it is possible and valid
		297	to have no binds, meaning that the node cannot be contacted form the
		298	outside. This means the node cannot talk to other nodes that also have no
		299	binds, but it can still talk to all "normal" nodes).
		300
		301	If the profile does not specify a binds list, then a default of C<*> is
		302	used, meaning the node will bind on a dynamically-assigned port on every
		303	local IP address it finds.
		304
		305	=item step 3, connect to seed nodes
		306
		307	As the last step, the seed ID list from the profile is passed to the
		308	L<AnyEvent::MP::Global> module, which will then use it to keep
		309	connectivity with at least one node at any point in time.
		310
		311	=back
		312
		313	Example: become a distributed node using the local node name as profile.
		314	This should be the most common form of invocation for "daemon"-type nodes.
		315
		316	configure
		317
		318	Example: become a semi-anonymous node. This form is often used for
		319	commandline clients.
		320
		321	configure nodeid => "myscript/%n/%u";
		322
		323	Example: configure a node using a profile called seed, which is suitable
		324	for a seed node as it binds on all local addresses on a fixed port (4040,
		325	customary for aemp).
		326
		327	# use the aemp commandline utility
		328	# aemp profile seed binds '*:4040'
		329
		330	# then use it
		331	configure profile => "seed";
		332
		333	# or simply use aemp from the shell again:
		334	# aemp run profile seed
		335
		336	# or provide a nicer-to-remember nodeid
		337	# aemp run profile seed nodeid "$(hostname)"
160		338
161	=item $SELF	339	=item $SELF
162		340
163	Contains the current port id while executing C<rcv> callbacks or C<psub>	341	Contains the current port id while executing C<rcv> callbacks or C<psub>
164	blocks.	342	blocks.
165		343
166	=item SELF, %SELF, @SELF...	344	=item *SELF, SELF, %SELF, @SELF...
167		345
168	Due to some quirks in how perl exports variables, it is impossible to	346	Due to some quirks in how perl exports variables, it is impossible to
169	just export C<$SELF>, all the symbols called C<SELF> are exported by this	347	just export C<$SELF>, all the symbols named C<SELF> are exported by this
170	module, but only C<$SELF> is currently used.	348	module, but only C<$SELF> is currently used.
171		349
172	=item snd $portid, type => @data	350	=item snd $port, type => @data
173		351
174	=item snd $portid, @msg	352	=item snd $port, @msg
175		353
176	Send the given message to the given port ID, which can identify either	354	Send the given message to the given port, which can identify either a
177	a local or a remote port, and can be either a string or soemthignt hat	355	local or a remote port, and must be a port ID.
178	stringifies a sa port ID (such as a port object :).
179		356
180	While the message can be about anything, it is highly recommended to use a	357	While the message can be almost anything, it is highly recommended to
181	string as first element (a portid, or some word that indicates a request	358	use a string as first element (a port ID, or some word that indicates a
182	type etc.).	359	request type etc.) and to consist if only simple perl values (scalars,
		360	arrays, hashes) - if you think you need to pass an object, think again.
183		361
184	The message data effectively becomes read-only after a call to this	362	The message data logically becomes read-only after a call to this
185	function: modifying any argument is not allowed and can cause many	363	function: modifying any argument (or values referenced by them) is
186	problems.	364	forbidden, as there can be considerable time between the call to C<snd>
		365	and the time the message is actually being serialised - in fact, it might
		366	never be copied as within the same process it is simply handed to the
		367	receiving port.
187		368
188	The type of data you can transfer depends on the transport protocol: when	369	The type of data you can transfer depends on the transport protocol: when
189	JSON is used, then only strings, numbers and arrays and hashes consisting	370	JSON is used, then only strings, numbers and arrays and hashes consisting
190	of those are allowed (no objects). When Storable is used, then anything	371	of those are allowed (no objects). When Storable is used, then anything
191	that Storable can serialise and deserialise is allowed, and for the local	372	that Storable can serialise and deserialise is allowed, and for the local
192	node, anything can be passed.	373	node, anything can be passed. Best rely only on the common denominator of
		374	these.
193		375
194	=item kil $portid[, @reason]	376	=item $local_port = port
195		377
196	Kill the specified port with the given C<@reason>.	378	Create a new local port object and returns its port ID. Initially it has
		379	no callbacks set and will throw an error when it receives messages.
197		380
198	If no C<@reason> is specified, then the port is killed "normally" (linked	381	=item $local_port = port { my @msg = @_ }
199	ports will not be kileld, or even notified).
200		382
201	Otherwise, linked ports get killed with the same reason (second form of	383	Creates a new local port, and returns its ID. Semantically the same as
202	C<mon>, see below).	384	creating a port and calling C<rcv $port, $callback> on it.
203		385
204	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks	386	The block will be called for every message received on the port, with the
205	will be reported as reason C<< die => $@ >>.	387	global variable C<$SELF> set to the port ID. Runtime errors will cause the
		388	port to be C<kil>ed. The message will be passed as-is, no extra argument
		389	(i.e. no port ID) will be passed to the callback.
206		390
207	Transport/communication errors are reported as C<< transport_error =>	391	If you want to stop/destroy the port, simply C<kil> it:
208	$message >>.
209		392
210	=item $guard = mon $portid, $cb->(@reason)	393	my $port = port {
		394	my @msg = @_;
		395	...
		396	kil $SELF;
		397	};
211		398
212	=item $guard = mon $portid, $otherport	399	=cut
213		400
214	=item $guard = mon $portid, $otherport, @msg	401	sub rcv($@);
215		402
		403	my $KILME = sub {
		404	die "received message on port without callback";
		405	};
		406
		407	sub port(;&) {
		408	my $id = $UNIQ . ++$ID;
		409	my $port = "$NODE#$id";
		410
		411	rcv $port, shift || $KILME;
		412
		413	$port
		414	}
		415
		416	=item rcv $local_port, $callback->(@msg)
		417
		418	Replaces the default callback on the specified port. There is no way to
		419	remove the default callback: use C<sub { }> to disable it, or better
		420	C<kil> the port when it is no longer needed.
		421
		422	The global C<$SELF> (exported by this module) contains C<$port> while
		423	executing the callback. Runtime errors during callback execution will
		424	result in the port being C<kil>ed.
		425
		426	The default callback received all messages not matched by a more specific
		427	C<tag> match.
		428
		429	=item rcv $local_port, tag => $callback->(@msg_without_tag), ...
		430
		431	Register (or replace) callbacks to be called on messages starting with the
		432	given tag on the given port (and return the port), or unregister it (when
		433	C<$callback> is C<$undef> or missing). There can only be one callback
		434	registered for each tag.
		435
		436	The original message will be passed to the callback, after the first
		437	element (the tag) has been removed. The callback will use the same
		438	environment as the default callback (see above).
		439
		440	Example: create a port and bind receivers on it in one go.
		441
		442	my $port = rcv port,
		443	msg1 => sub { ... },
		444	msg2 => sub { ... },
		445	;
		446
		447	Example: create a port, bind receivers and send it in a message elsewhere
		448	in one go:
		449
		450	snd $otherport, reply =>
		451	rcv port,
		452	msg1 => sub { ... },
		453	...
		454	;
		455
		456	Example: temporarily register a rcv callback for a tag matching some port
		457	(e.g. for an rpc reply) and unregister it after a message was received.
		458
		459	rcv $port, $otherport => sub {
		460	my @reply = @_;
		461
		462	rcv $SELF, $otherport;
		463	};
		464
		465	=cut
		466
		467	sub rcv($@) {
		468	my $port = shift;
		469	my ($nodeid, $portid) = split /#/, $port, 2;
		470
		471	$NODE{$nodeid} == $NODE{""}
		472	or Carp::croak "$port: rcv can only be called on local ports, caught";
		473
		474	while (@_) {
		475	if (ref $_[0]) {
		476	if (my $self = $PORT_DATA{$portid}) {
		477	"AnyEvent::MP::Port" eq ref $self
		478	or Carp::croak "$port: rcv can only be called on message matching ports, caught";
		479
		480	$self->[0] = shift;
		481	} else {
		482	my $cb = shift;
		483	$PORT{$portid} = sub {
		484	local $SELF = $port;
		485	eval { &$cb }; _self_die if $@;
		486	};
		487	}
		488	} elsif (defined $_[0]) {
		489	my $self = $PORT_DATA{$portid} ||= do {
		490	my $self = bless [$PORT{$portid} || sub { }, { }, $port], "AnyEvent::MP::Port";
		491
		492	$PORT{$portid} = sub {
		493	local $SELF = $port;
		494
		495	if (my $cb = $self->[1]{$_[0]}) {
		496	shift;
		497	eval { &$cb }; _self_die if $@;
		498	} else {
		499	&{ $self->[0] };
		500	}
		501	};
		502
		503	$self
		504	};
		505
		506	"AnyEvent::MP::Port" eq ref $self
		507	or Carp::croak "$port: rcv can only be called on message matching ports, caught";
		508
		509	my ($tag, $cb) = splice @_, 0, 2;
		510
		511	if (defined $cb) {
		512	$self->[1]{$tag} = $cb;
		513	} else {
		514	delete $self->[1]{$tag};
		515	}
		516	}
		517	}
		518
		519	$port
		520	}
		521
		522	=item peval $port, $coderef[, @args]
		523
		524	Evaluates the given C<$codref> within the contetx of C<$port>, that is,
		525	when the code throews an exception the C<$port> will be killed.
		526
		527	Any remaining args will be passed to the callback. Any return values will
		528	be returned to the caller.
		529
		530	This is useful when you temporarily want to execute code in the context of
		531	a port.
		532
		533	Example: create a port and run some initialisation code in it's context.
		534
		535	my $port = port { ... };
		536
		537	peval $port, sub {
		538	init
		539	or die "unable to init";
		540	};
		541
		542	=cut
		543
		544	sub peval($$) {
		545	local $SELF = shift;
		546	my $cb = shift;
		547
		548	if (wantarray) {
		549	my @res = eval { &$cb };
		550	_self_die if $@;
		551	@res
		552	} else {
		553	my $res = eval { &$cb };
		554	_self_die if $@;
		555	$res
		556	}
		557	}
		558
		559	=item $closure = psub { BLOCK }
		560
		561	Remembers C<$SELF> and creates a closure out of the BLOCK. When the
		562	closure is executed, sets up the environment in the same way as in C<rcv>
		563	callbacks, i.e. runtime errors will cause the port to get C<kil>ed.
		564
		565	The effect is basically as if it returned C<< sub { peval $SELF, sub {
		566	BLOCK }, @_ } >>.
		567
		568	This is useful when you register callbacks from C<rcv> callbacks:
		569
		570	rcv delayed_reply => sub {
		571	my ($delay, @reply) = @_;
		572	my $timer = AE::timer $delay, 0, psub {
		573	snd @reply, $SELF;
		574	};
		575	};
		576
		577	=cut
		578
		579	sub psub(&) {
		580	my $cb = shift;
		581
		582	my $port = $SELF
		583	or Carp::croak "psub can only be called from within rcv or psub callbacks, not";
		584
		585	sub {
		586	local $SELF = $port;
		587
		588	if (wantarray) {
		589	my @res = eval { &$cb };
		590	_self_die if $@;
		591	@res
		592	} else {
		593	my $res = eval { &$cb };
		594	_self_die if $@;
		595	$res
		596	}
		597	}
		598	}
		599
		600	=item $guard = mon $port, $cb->(@reason) # call $cb when $port dies
		601
		602	=item $guard = mon $port, $rcvport # kill $rcvport when $port dies
		603
		604	=item $guard = mon $port # kill $SELF when $port dies
		605
		606	=item $guard = mon $port, $rcvport, @msg # send a message when $port dies
		607
216	Monitor the given port and do something when the port is killed.	608	Monitor the given port and do something when the port is killed or
		609	messages to it were lost, and optionally return a guard that can be used
		610	to stop monitoring again.
217		611
218	In the first form, the callback is simply called with any number	612	In the first form (callback), the callback is simply called with any
219	of C<@reason> elements (no @reason means that the port was deleted	613	number of C<@reason> elements (no @reason means that the port was deleted
220	"normally"). Note also that I<< the callback B<must> never die >>, so use	614	"normally"). Note also that I<< the callback B<must> never die >>, so use
221	C<eval> if unsure.	615	C<eval> if unsure.
222		616
223	In the second form, the other port will be C<kil>'ed with C<@reason>, iff	617	In the second form (another port given), the other port (C<$rcvport>)
224	a @reason was specified, i.e. on "normal" kils nothing happens, while	618	will be C<kil>'ed with C<@reason>, if a @reason was specified, i.e. on
225	under all other conditions, the other port is killed with the same reason.	619	"normal" kils nothing happens, while under all other conditions, the other
		620	port is killed with the same reason.
226		621
		622	The third form (kill self) is the same as the second form, except that
		623	C<$rvport> defaults to C<$SELF>.
		624
227	In the last form, a message of the form C<@msg, @reason> will be C<snd>.	625	In the last form (message), a message of the form C<@msg, @reason> will be
		626	C<snd>.
		627
		628	Monitoring-actions are one-shot: once messages are lost (and a monitoring
		629	alert was raised), they are removed and will not trigger again.
		630
		631	As a rule of thumb, monitoring requests should always monitor a port from
		632	a local port (or callback). The reason is that kill messages might get
		633	lost, just like any other message. Another less obvious reason is that
		634	even monitoring requests can get lost (for example, when the connection
		635	to the other node goes down permanently). When monitoring a port locally
		636	these problems do not exist.
		637
		638	C<mon> effectively guarantees that, in the absence of hardware failures,
		639	after starting the monitor, either all messages sent to the port will
		640	arrive, or the monitoring action will be invoked after possible message
		641	loss has been detected. No messages will be lost "in between" (after
		642	the first lost message no further messages will be received by the
		643	port). After the monitoring action was invoked, further messages might get
		644	delivered again.
		645
		646	Inter-host-connection timeouts and monitoring depend on the transport
		647	used. The only transport currently implemented is TCP, and AnyEvent::MP
		648	relies on TCP to detect node-downs (this can take 10-15 minutes on a
		649	non-idle connection, and usually around two hours for idle connections).
		650
		651	This means that monitoring is good for program errors and cleaning up
		652	stuff eventually, but they are no replacement for a timeout when you need
		653	to ensure some maximum latency.
228		654
229	Example: call a given callback when C<$port> is killed.	655	Example: call a given callback when C<$port> is killed.
230		656
231	mon $port, sub { warn "port died because of <@_>\n" };	657	mon $port, sub { warn "port died because of <@_>\n" };
232		658
233	Example: kill ourselves when C<$port> is killed abnormally.	659	Example: kill ourselves when C<$port> is killed abnormally.
234		660
235	mon $port, $self;	661	mon $port;
236		662
237	Example: send us a restart message another C<$port> is killed.	663	Example: send us a restart message when another C<$port> is killed.
238		664
239	mon $port, $self => "restart";	665	mon $port, $self => "restart";
240		666
241	=cut	667	=cut
242		668
243	sub mon {	669	sub mon {
244	my ($noderef, $port) = split /#/, shift, 2;	670	my ($nodeid, $port) = split /#/, shift, 2;
245		671
246	my $node = $NODE{$noderef} || add_node $noderef;	672	my $node = $NODE{$nodeid} || add_node $nodeid;
247		673
248	my $cb = shift;	674	my $cb = @_ ? shift : $SELF || Carp::croak 'mon: called with one argument only, but $SELF not set,';
249		675
250	unless (ref $cb) {	676	unless (ref $cb) {
251	if (@_) {	677	if (@_) {
252	# send a kill info message	678	# send a kill info message
253	my (@msg) = ($cb, @_);	679	my (@msg) = ($cb, @_);
…		…
260	}	686	}
261		687
262	$node->monitor ($port, $cb);	688	$node->monitor ($port, $cb);
263		689
264	defined wantarray	690	defined wantarray
265	and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }	691	and ($cb += 0, Guard::guard { $node->unmonitor ($port, $cb) })
266	}	692	}
267		693
268	=item $guard = mon_guard $port, $ref, $ref...	694	=item $guard = mon_guard $port, $ref, $ref...
269		695
270	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
271	is killed, the references will be freed.	697	is killed, the references will be freed.
272		698
273	Optionally returns a guard that will stop the monitoring.	699	Optionally returns a guard that will stop the monitoring.
274		700
275	This function is useful when you create e.g. timers or other watchers and	701	This function is useful when you create e.g. timers or other watchers and
276	want to free them when the port gets killed:	702	want to free them when the port gets killed (note the use of C<psub>):
277		703
278	$port->rcv (start => sub {	704	$port->rcv (start => sub {
279	my $timer; $timer = mon_guard $port, AE::timer 1, 1, sub {	705	my $timer; $timer = mon_guard $port, AE::timer 1, 1, psub {
280	undef $timer if 0.9 < rand;	706	undef $timer if 0.9 < rand;
281	});	707	});
282	});	708	});
283		709
284	=cut	710	=cut
285		711
286	sub mon_guard {	712	sub mon_guard {
287	my ($port, @refs) = @_;	713	my ($port, @refs) = @_;
288		714
		715	#TODO: mon-less form?
		716
289	mon $port, sub { 0 && @refs }	717	mon $port, sub { 0 && @refs }
290	}	718	}
291		719
292	=item lnk $port1, $port2	720	=item kil $port[, @reason]
293		721
294	Link two ports. This is simply a shorthand for:	722	Kill the specified port with the given C<@reason>.
295		723
296	mon $port1, $port2;	724	If no C<@reason> is specified, then the port is killed "normally" -
297	mon $port2, $port1;	725	monitor callback will be invoked, but the kil will not cause linked ports
		726	(C<mon $mport, $lport> form) to get killed.
298		727
299	It means that if either one is killed abnormally, the other one gets	728	If a C<@reason> is specified, then linked ports (C<mon $mport, $lport>
300	killed as well.	729	form) get killed with the same reason.
301		730
302	=item $local_port = port	731	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
		732	will be reported as reason C<< die => $@ >>.
303		733
304	Create a new local port object that can be used either as a pattern	734	Transport/communication errors are reported as C<< transport_error =>
305	matching port ("full port") or a single-callback port ("miniport"),	735	$message >>.
306	depending on how C<rcv> callbacks are bound to the object.
307		736
308	=item $portid = port { my @msg = @_; $finished }	737	=cut
309		738
310	Creates a "mini port", that is, a very lightweight port without any	739	=item $port = spawn $node, $initfunc[, @initdata]
311	pattern matching behind it, and returns its ID.
312		740
313	The block will be called for every message received on the port. When the	741	Creates a port on the node C<$node> (which can also be a port ID, in which
314	callback returns a true value its job is considered "done" and the port	742	case it's the node where that port resides).
315	will be destroyed. Otherwise it will stay alive.
316		743
317	The message will be passed as-is, no extra argument (i.e. no port id) will	744	The port ID of the newly created port is returned immediately, and it is
318	be passed to the callback.	745	possible to immediately start sending messages or to monitor the port.
319		746
320	If you need the local port id in the callback, this works nicely:	747	After the port has been created, the init function is called on the remote
		748	node, in the same context as a C<rcv> callback. This function must be a
		749	fully-qualified function name (e.g. C<MyApp::Chat::Server::init>). To
		750	specify a function in the main program, use C<::name>.
321		751
322	my $port; $port = port {	752	If the function doesn't exist, then the node tries to C<require>
323	snd $otherport, reply => $port;	753	the package, then the package above the package and so on (e.g.
		754	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
		755	exists or it runs out of package names.
		756
		757	The init function is then called with the newly-created port as context
		758	object (C<$SELF>) and the C<@initdata> values as arguments. It I<must>
		759	call one of the C<rcv> functions to set callbacks on C<$SELF>, otherwise
		760	the port might not get created.
		761
		762	A common idiom is to pass a local port, immediately monitor the spawned
		763	port, and in the remote init function, immediately monitor the passed
		764	local port. This two-way monitoring ensures that both ports get cleaned up
		765	when there is a problem.
		766
		767	C<spawn> guarantees that the C<$initfunc> has no visible effects on the
		768	caller before C<spawn> returns (by delaying invocation when spawn is
		769	called for the local node).
		770
		771	Example: spawn a chat server port on C<$othernode>.
		772
		773	# this node, executed from within a port context:
		774	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;
		775	mon $server;
		776
		777	# init function on C<$othernode>
		778	sub connect {
		779	my ($srcport) = @_;
		780
		781	mon $srcport;
		782
		783	rcv $SELF, sub {
		784	...
		785	};
		786	}
		787
		788	=cut
		789
		790	sub _spawn {
		791	my $port = shift;
		792	my $init = shift;
		793
		794	# rcv will create the actual port
		795	local $SELF = "$NODE#$port";
		796	eval {
		797	&{ load_func $init }
324	};	798	};
		799	_self_die if $@;
		800	}
		801
		802	sub spawn(@) {
		803	my ($nodeid, undef) = split /#/, shift, 2;
		804
		805	my $id = $RUNIQ . ++$ID;
		806
		807	$_[0] =~ /::/
		808	or Carp::croak "spawn init function must be a fully-qualified name, caught";
		809
		810	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;
		811
		812	"$nodeid#$id"
		813	}
		814
		815
		816	=item after $timeout, @msg
		817
		818	=item after $timeout, $callback
		819
		820	Either sends the given message, or call the given callback, after the
		821	specified number of seconds.
		822
		823	This is simply a utility function that comes in handy at times - the
		824	AnyEvent::MP author is not convinced of the wisdom of having it, though,
		825	so it may go away in the future.
325		826
326	=cut	827	=cut
327		828
328	sub port(;&) {	829	sub after($@) {
329	my $id = "$UNIQ." . $ID++;	830	my ($timeout, @action) = @_;
330	my $port = "$NODE#$id";
331		831
332	if (@_) {	832	my $t; $t = AE::timer $timeout, 0, sub {
333	my $cb = shift;	833	undef $t;
334	$PORT{$id} = sub {	834	ref $action[0]
335	local $SELF = $port;	835	? $action[0]()
336	eval {	836	: snd @action;
337	&$cb	837	};
338	and kil $id;	838	}
339	};	839
340	_self_die if $@;	840	#=item $cb2 = timeout $seconds, $cb[, @args]
		841
		842	=item cal $port, @msg, $callback[, $timeout]
		843
		844	A simple form of RPC - sends a message to the given C<$port> with the
		845	given contents (C<@msg>), but adds a reply port to the message.
		846
		847	The reply port is created temporarily just for the purpose of receiving
		848	the reply, and will be C<kil>ed when no longer needed.
		849
		850	A reply message sent to the port is passed to the C<$callback> as-is.
		851
		852	If an optional time-out (in seconds) is given and it is not C<undef>,
		853	then the callback will be called without any arguments after the time-out
		854	elapsed and the port is C<kil>ed.
		855
		856	If no time-out is given (or it is C<undef>), then the local port will
		857	monitor the remote port instead, so it eventually gets cleaned-up.
		858
		859	Currently this function returns the temporary port, but this "feature"
		860	might go in future versions unless you can make a convincing case that
		861	this is indeed useful for something.
		862
		863	=cut
		864
		865	sub cal(@) {
		866	my $timeout = ref $_[-1] ? undef : pop;
		867	my $cb = pop;
		868
		869	my $port = port {
		870	undef $timeout;
		871	kil $SELF;
		872	&$cb;
		873	};
		874
		875	if (defined $timeout) {
		876	$timeout = AE::timer $timeout, 0, sub {
		877	undef $timeout;
		878	kil $port;
		879	$cb->();
341	};	880	};
342	} else {	881	} else {
343	my $self = bless {	882	mon $_[0], sub {
344	id => "$NODE#$id",	883	kil $port;
345	}, "AnyEvent::MP::Port";	884	$cb->();
346
347	$PORT_DATA{$id} = $self;
348	$PORT{$id} = sub {
349	local $SELF = $port;
350
351	eval {
352	for (@{ $self->{rc0}{$_[0]} }) {
353	$_ && &{$_->[0]}
354	&& undef $_;
355	}
356
357	for (@{ $self->{rcv}{$_[0]} }) {
358	$_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1]
359	&& &{$_->[0]}
360	&& undef $_;
361	}
362
363	for (@{ $self->{any} }) {
364	$_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1]
365	&& &{$_->[0]}
366	&& undef $_;
367	}
368	};
369	_self_die if $@;
370	};	885	};
371	}	886	}
372		887
		888	push @_, $port;
		889	&snd;
		890
373	$port	891	$port
374	}	892	}
375		893
376	=item reg $portid, $name	894	=back
377		895
378	Registers the given port under the name C<$name>. If the name already	896	=head1 DISTRIBUTED DATABASE
379	exists it is replaced.
380		897
381	A port can only be registered under one well known name.	898	AnyEvent::MP comes with a simple distributed database. The database will
		899	be mirrored asynchronously on all global nodes. Other nodes bind to one
		900	of the global nodes for their needs. Every node has a "local database"
		901	which contains all the values that are set locally. All local databases
		902	are merged together to form the global database, which can be queried.
382		903
383	A port automatically becomes unregistered when it is killed.	904	The database structure is that of a two-level hash - the database hash
		905	contains hashes which contain values, similarly to a perl hash of hashes,
		906	i.e.:
		907
		908	$DATABASE{$family}{$subkey} = $value
		909
		910	The top level hash key is called "family", and the second-level hash key
		911	is called "subkey" or simply "key".
		912
		913	The family must be alphanumeric, i.e. start with a letter and consist
		914	of letters, digits, underscores and colons (C<[A-Za-z][A-Za-z0-9_:]*>,
		915	pretty much like Perl module names.
		916
		917	As the family namespace is global, it is recommended to prefix family names
		918	with the name of the application or module using it.
		919
		920	The subkeys must be non-empty strings, with no further restrictions.
		921
		922	The values should preferably be strings, but other perl scalars should
		923	work as well (such as C<undef>, arrays and hashes).
		924
		925	Every database entry is owned by one node - adding the same family/subkey
		926	combination on multiple nodes will not cause discomfort for AnyEvent::MP,
		927	but the result might be nondeterministic, i.e. the key might have
		928	different values on different nodes.
		929
		930	Different subkeys in the same family can be owned by different nodes
		931	without problems, and in fact, this is the common method to create worker
		932	pools. For example, a worker port for image scaling might do this:
		933
		934	db_set my_image_scalers => $port;
		935
		936	And clients looking for an image scaler will want to get the
		937	C<my_image_scalers> keys from time to time:
		938
		939	db_keys my_image_scalers => sub {
		940	@ports = @{ $_[0] };
		941	};
		942
		943	Or better yet, they want to monitor the database family, so they always
		944	have a reasonable up-to-date copy:
		945
		946	db_mon my_image_scalers => sub {
		947	@ports = keys %{ $_[0] };
		948	};
		949
		950	In general, you can set or delete single subkeys, but query and monitor
		951	whole families only.
		952
		953	If you feel the need to monitor or query a single subkey, try giving it
		954	it's own family.
		955
		956	=over
		957
		958	=item db_set $family => $subkey [=> $value]
		959
		960	Sets (or replaces) a key to the database - if C<$value> is omitted,
		961	C<undef> is used instead.
		962
		963	=item db_del $family => $subkey...
		964
		965	Deletes one or more subkeys from the database family.
		966
		967	=item $guard = db_reg $family => $subkey [=> $value]
		968
		969	Sets the key on the database and returns a guard. When the guard is
		970	destroyed, the key is deleted from the database. If C<$value> is missing,
		971	then C<undef> is used.
		972
		973	=item db_family $family => $cb->(\%familyhash)
		974
		975	Queries the named database C<$family> and call the callback with the
		976	family represented as a hash. You can keep and freely modify the hash.
		977
		978	=item db_keys $family => $cb->(\@keys)
		979
		980	Same as C<db_family>, except it only queries the family I<subkeys> and passes
		981	them as array reference to the callback.
		982
		983	=item db_values $family => $cb->(\@values)
		984
		985	Same as C<db_family>, except it only queries the family I<values> and passes them
		986	as array reference to the callback.
		987
		988	=item $guard = db_mon $family => $cb->($familyhash, \@added, \@changed, \@deleted)
		989
		990	Creates a monitor on the given database family. Each time a key is set
		991	or or is deleted the callback is called with a hash containing the
		992	database family and three lists of added, changed and deleted subkeys,
		993	respectively. If no keys have changed then the array reference might be
		994	C<undef> or even missing.
		995
		996	If not called in void context, a guard object is returned that, when
		997	destroyed, stops the monitor.
		998
		999	The family hash reference and the key arrays belong to AnyEvent::MP and
		1000	B<must not be modified or stored> by the callback. When in doubt, make a
		1001	copy.
		1002
		1003	As soon as possible after the monitoring starts, the callback will be
		1004	called with the intiial contents of the family, even if it is empty,
		1005	i.e. there will always be a timely call to the callback with the current
		1006	contents.
		1007
		1008	It is possible that the callback is called with a change event even though
		1009	the subkey is already present and the value has not changed.
		1010
		1011	The monitoring stops when the guard object is destroyed.
		1012
		1013	Example: on every change to the family "mygroup", print out all keys.
		1014
		1015	my $guard = db_mon mygroup => sub {
		1016	my ($family, $a, $c, $d) = @_;
		1017	print "mygroup members: ", (join " ", keys %$family), "\n";
		1018	};
		1019
		1020	Exmaple: wait until the family "My::Module::workers" is non-empty.
		1021
		1022	my $guard; $guard = db_mon My::Module::workers => sub {
		1023	my ($family, $a, $c, $d) = @_;
		1024	return unless %$family;
		1025	undef $guard;
		1026	print "My::Module::workers now nonempty\n";
		1027	};
		1028
		1029	Example: print all changes to the family "AnyRvent::Fantasy::Module".
		1030
		1031	my $guard = db_mon AnyRvent::Fantasy::Module => sub {
		1032	my ($family, $a, $c, $d) = @_;
		1033
		1034	print "+$_=$family->{$_}\n" for @$a;
		1035	print "*$_=$family->{$_}\n" for @$c;
		1036	print "-$_=$family->{$_}\n" for @$d;
		1037	};
384		1038
385	=cut	1039	=cut
386		1040
387	sub reg(@) {
388	my ($portid, $name) = @_;
389
390	$REG{$name} = $portid;
391	}
392
393	=item rcv $portid, $callback->(@msg)
394
395	Replaces the callback on the specified miniport (or newly created port
396	object, see C<port>). Full ports are configured with the following calls:
397
398	=item rcv $portid, tagstring => $callback->(@msg), ...
399
400	=item rcv $portid, $smartmatch => $callback->(@msg), ...
401
402	=item rcv $portid, [$smartmatch...] => $callback->(@msg), ...
403
404	Register callbacks to be called on matching messages on the given port.
405
406	The callback has to return a true value when its work is done, after
407	which is will be removed, or a false value in which case it will stay
408	registered.
409
410	The global C<$SELF> (exported by this module) contains C<$portid> while
411	executing the callback.
412
413	Runtime errors wdurign callback execution will result in the port being
414	C<kil>ed.
415
416	If the match is an array reference, then it will be matched against the
417	first elements of the message, otherwise only the first element is being
418	matched.
419
420	Any element in the match that is specified as C<_any_> (a function
421	exported by this module) matches any single element of the message.
422
423	While not required, it is highly recommended that the first matching
424	element is a string identifying the message. The one-string-only match is
425	also the most efficient match (by far).
426
427	=cut
428
429	sub rcv($@) {
430	my $portid = shift;
431	my ($noderef, $port) = split /#/, $port, 2;
432
433	($NODE{$noderef} || add_node $noderef) == $NODE{""}
434	or Carp::croak "$noderef#$port: rcv can only be called on local ports, caught";
435
436	my $self = $PORT_DATA{$port}
437	or Carp::croak "$noderef#$port: rcv can only be called on message matching ports, caught";
438
439	"AnyEvent::MP::Port" eq ref $self
440	or Carp::croak "$noderef#$port: rcv can only be called on message matching ports, caught";
441
442	while (@_) {
443	my ($match, $cb) = splice @_, 0, 2;
444
445	if (!ref $match) {
446	push @{ $self->{rc0}{$match} }, [$cb];
447	} elsif (("ARRAY" eq ref $match && !ref $match->[0])) {
448	my ($type, @match) = @$match;
449	@match
450	? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match]
451	: push @{ $self->{rc0}{$match->[0]} }, [$cb];
452	} else {
453	push @{ $self->{any} }, [$cb, $match];
454	}
455	}
456
457	$portid
458	}
459
460	=item $closure = psub { BLOCK }
461
462	Remembers C<$SELF> and creates a closure out of the BLOCK. When the
463	closure is executed, sets up the environment in the same way as in C<rcv>
464	callbacks, i.e. runtime errors will cause the port to get C<kil>ed.
465
466	This is useful when you register callbacks from C<rcv> callbacks:
467
468	rcv delayed_reply => sub {
469	my ($delay, @reply) = @_;
470	my $timer = AE::timer $delay, 0, psub {
471	snd @reply, $SELF;
472	};
473	};
474
475	=cut
476
477	sub psub(&) {
478	my $cb = shift;
479
480	my $port = $SELF
481	or Carp::croak "psub can only be called from within rcv or psub callbacks, not";
482
483	sub {
484	local $SELF = $port;
485
486	if (wantarray) {
487	my @res = eval { &$cb };
488	_self_die if $@;
489	@res
490	} else {
491	my $res = eval { &$cb };
492	_self_die if $@;
493	$res
494	}
495	}
496	}
497
498	=back	1041	=back
499		1042
500	=head1 FUNCTIONS FOR NODES
501
502	=over 4
503
504	=item become_public $noderef
505
506	Tells the node to become a public node, i.e. reachable from other nodes.
507
508	The first argument is the (unresolved) node reference of the local node
509	(if missing then the empty string is used).
510
511	It is quite common to not specify anything, in which case the local node
512	tries to listen on the default port, or to only specify a port number, in
513	which case AnyEvent::MP tries to guess the local addresses.
514
515	=cut
516
517	=back
518
519	=head1 NODE MESSAGES
520
521	Nodes understand the following messages sent to them. Many of them take
522	arguments called C<@reply>, which will simply be used to compose a reply
523	message - C<$reply[0]> is the port to reply to, C<$reply[1]> the type and
524	the remaining arguments are simply the message data.
525
526	While other messages exist, they are not public and subject to change.
527
528	=over 4
529
530	=cut
531
532	=item lookup => $name, @reply
533
534	Replies with the port ID of the specified well-known port, or C<undef>.
535
536	=item devnull => ...
537
538	Generic data sink/CPU heat conversion.
539
540	=item relay => $port, @msg
541
542	Simply forwards the message to the given port.
543
544	=item eval => $string[ @reply]
545
546	Evaluates the given string. If C<@reply> is given, then a message of the
547	form C<@reply, $@, @evalres> is sent.
548
549	Example: crash another node.
550
551	snd $othernode, eval => "exit";
552
553	=item time => @reply
554
555	Replies the the current node time to C<@reply>.
556
557	Example: tell the current node to send the current time to C<$myport> in a
558	C<timereply> message.
559
560	snd $NODE, time => $myport, timereply => 1, 2;
561	# => snd $myport, timereply => 1, 2, <time>
562
563	=back
564
565	=head1 AnyEvent::MP vs. Distributed Erlang	1043	=head1 AnyEvent::MP vs. Distributed Erlang
566		1044
567	AnyEvent::MP got lots of its ideas from distributed erlang (erlang node	1045	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
568	== aemp node, erlang process == aemp port), so many of the documents and	1046	== aemp node, Erlang process == aemp port), so many of the documents and
569	programming techniques employed by erlang apply to AnyEvent::MP. Here is a	1047	programming techniques employed by Erlang apply to AnyEvent::MP. Here is a
570	sample:	1048	sample:
571		1049
572	http://www.erlang.se/doc/programming_rules.shtml	1050	http://www.erlang.se/doc/programming_rules.shtml
573	http://erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4	1051	http://erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4
574	http://erlang.org/download/erlang-book-part1.pdf # chapters 5 and 6	1052	http://erlang.org/download/erlang-book-part1.pdf # chapters 5 and 6
…		…
576		1054
577	Despite the similarities, there are also some important differences:	1055	Despite the similarities, there are also some important differences:
578		1056
579	=over 4	1057	=over 4
580		1058
581	=item * Node references contain the recipe on how to contact them.	1059	=item * Node IDs are arbitrary strings in AEMP.
582		1060
583	Erlang relies on special naming and DNS to work everywhere in the	1061	Erlang relies on special naming and DNS to work everywhere in the same
584	same way. AEMP relies on each node knowing it's own address(es), with	1062	way. AEMP relies on each node somehow knowing its own address(es) (e.g. by
585	convenience functionality.	1063	configuration or DNS), and possibly the addresses of some seed nodes, but
		1064	will otherwise discover other nodes (and their IDs) itself.
586		1065
587	This means that AEMP requires a less tightly controlled environment at the	1066	=item * Erlang has a "remote ports are like local ports" philosophy, AEMP
588	cost of longer node references and a slightly higher management overhead.	1067	uses "local ports are like remote ports".
		1068
		1069	The failure modes for local ports are quite different (runtime errors
		1070	only) then for remote ports - when a local port dies, you I<know> it dies,
		1071	when a connection to another node dies, you know nothing about the other
		1072	port.
		1073
		1074	Erlang pretends remote ports are as reliable as local ports, even when
		1075	they are not.
		1076
		1077	AEMP encourages a "treat remote ports differently" philosophy, with local
		1078	ports being the special case/exception, where transport errors cannot
		1079	occur.
589		1080
590	=item * Erlang uses processes and a mailbox, AEMP does not queue.	1081	=item * Erlang uses processes and a mailbox, AEMP does not queue.
591		1082
592	Erlang uses processes that selctively receive messages, and therefore	1083	Erlang uses processes that selectively receive messages out of order, and
593	needs a queue. AEMP is event based, queuing messages would serve no useful	1084	therefore needs a queue. AEMP is event based, queuing messages would serve
594	purpose.	1085	no useful purpose. For the same reason the pattern-matching abilities
		1086	of AnyEvent::MP are more limited, as there is little need to be able to
		1087	filter messages without dequeuing them.
595		1088
596	(But see L<Coro::MP> for a more erlang-like process model on top of AEMP).	1089	This is not a philosophical difference, but simply stems from AnyEvent::MP
		1090	being event-based, while Erlang is process-based.
		1091
		1092	You cna have a look at L<Coro::MP> for a more Erlang-like process model on
		1093	top of AEMP and Coro threads.
597		1094
598	=item * Erlang sends are synchronous, AEMP sends are asynchronous.	1095	=item * Erlang sends are synchronous, AEMP sends are asynchronous.
599		1096
600	Sending messages in erlang is synchronous and blocks the process. AEMP	1097	Sending messages in Erlang is synchronous and blocks the process until
601	sends are immediate, connection establishment is handled in the	1098	a conenction has been established and the message sent (and so does not
602	background.	1099	need a queue that can overflow). AEMP sends return immediately, connection
		1100	establishment is handled in the background.
603		1101
604	=item * Erlang can silently lose messages, AEMP cannot.	1102	=item * Erlang suffers from silent message loss, AEMP does not.
605		1103
606	Erlang makes few guarantees on messages delivery - messages can get lost	1104	Erlang implements few guarantees on messages delivery - messages can get
607	without any of the processes realising it (i.e. you send messages a, b,	1105	lost without any of the processes realising it (i.e. you send messages a,
608	and c, and the other side only receives messages a and c).	1106	b, and c, and the other side only receives messages a and c).
609		1107
610	AEMP guarantees correct ordering, and the guarantee that there are no	1108	AEMP guarantees (modulo hardware errors) correct ordering, and the
		1109	guarantee that after one message is lost, all following ones sent to the
		1110	same port are lost as well, until monitoring raises an error, so there are
611	holes in the message sequence.	1111	no silent "holes" in the message sequence.
612		1112
613	=item * In erlang, processes can be declared dead and later be found to be	1113	If you want your software to be very reliable, you have to cope with
614	alive.	1114	corrupted and even out-of-order messages in both Erlang and AEMP. AEMP
615		1115	simply tries to work better in common error cases, such as when a network
616	In erlang it can happen that a monitored process is declared dead and	1116	link goes down.
617	linked processes get killed, but later it turns out that the process is
618	still alive - and can receive messages.
619
620	In AEMP, when port monitoring detects a port as dead, then that port will
621	eventually be killed - it cannot happen that a node detects a port as dead
622	and then later sends messages to it, finding it is still alive.
623		1117
624	=item * Erlang can send messages to the wrong port, AEMP does not.	1118	=item * Erlang can send messages to the wrong port, AEMP does not.
625		1119
626	In erlang it is quite possible that a node that restarts reuses a process	1120	In Erlang it is quite likely that a node that restarts reuses an Erlang
627	ID known to other nodes for a completely different process, causing	1121	process ID known to other nodes for a completely different process,
628	messages destined for that process to end up in an unrelated process.	1122	causing messages destined for that process to end up in an unrelated
		1123	process.
629		1124
630	AEMP never reuses port IDs, so old messages or old port IDs floating	1125	AEMP does not reuse port IDs, so old messages or old port IDs floating
631	around in the network will not be sent to an unrelated port.	1126	around in the network will not be sent to an unrelated port.
632		1127
633	=item * Erlang uses unprotected connections, AEMP uses secure	1128	=item * Erlang uses unprotected connections, AEMP uses secure
634	authentication and can use TLS.	1129	authentication and can use TLS.
635		1130
636	AEMP can use a proven protocol - SSL/TLS - to protect connections and	1131	AEMP can use a proven protocol - TLS - to protect connections and
637	securely authenticate nodes.	1132	securely authenticate nodes.
638		1133
639	=item * The AEMP protocol is optimised for both text-based and binary	1134	=item * The AEMP protocol is optimised for both text-based and binary
640	communications.	1135	communications.
641		1136
642	The AEMP protocol, unlike the erlang protocol, supports both	1137	The AEMP protocol, unlike the Erlang protocol, supports both programming
643	language-independent text-only protocols (good for debugging) and binary,	1138	language independent text-only protocols (good for debugging), and binary,
644	language-specific serialisers (e.g. Storable).	1139	language-specific serialisers (e.g. Storable). By default, unless TLS is
		1140	used, the protocol is actually completely text-based.
645		1141
646	It has also been carefully designed to be implementable in other languages	1142	It has also been carefully designed to be implementable in other languages
647	with a minimum of work while gracefully degrading fucntionality to make the	1143	with a minimum of work while gracefully degrading functionality to make the
648	protocol simple.	1144	protocol simple.
649		1145
		1146	=item * AEMP has more flexible monitoring options than Erlang.
		1147
		1148	In Erlang, you can chose to receive I<all> exit signals as messages or
		1149	I<none>, there is no in-between, so monitoring single Erlang processes is
		1150	difficult to implement.
		1151
		1152	Monitoring in AEMP is more flexible than in Erlang, as one can choose
		1153	between automatic kill, exit message or callback on a per-port basis.
		1154
		1155	=item * Erlang tries to hide remote/local connections, AEMP does not.
		1156
		1157	Monitoring in Erlang is not an indicator of process death/crashes, in the
		1158	same way as linking is (except linking is unreliable in Erlang).
		1159
		1160	In AEMP, you don't "look up" registered port names or send to named ports
		1161	that might or might not be persistent. Instead, you normally spawn a port
		1162	on the remote node. The init function monitors you, and you monitor the
		1163	remote port. Since both monitors are local to the node, they are much more
		1164	reliable (no need for C<spawn_link>).
		1165
		1166	This also saves round-trips and avoids sending messages to the wrong port
		1167	(hard to do in Erlang).
		1168
650	=back	1169	=back
651		1170
		1171	=head1 RATIONALE
		1172
		1173	=over 4
		1174
		1175	=item Why strings for port and node IDs, why not objects?
		1176
		1177	We considered "objects", but found that the actual number of methods
		1178	that can be called are quite low. Since port and node IDs travel over
		1179	the network frequently, the serialising/deserialising would add lots of
		1180	overhead, as well as having to keep a proxy object everywhere.
		1181
		1182	Strings can easily be printed, easily serialised etc. and need no special
		1183	procedures to be "valid".
		1184
		1185	And as a result, a port with just a default receiver consists of a single
		1186	code reference stored in a global hash - it can't become much cheaper.
		1187
		1188	=item Why favour JSON, why not a real serialising format such as Storable?
		1189
		1190	In fact, any AnyEvent::MP node will happily accept Storable as framing
		1191	format, but currently there is no way to make a node use Storable by
		1192	default (although all nodes will accept it).
		1193
		1194	The default framing protocol is JSON because a) JSON::XS is many times
		1195	faster for small messages and b) most importantly, after years of
		1196	experience we found that object serialisation is causing more problems
		1197	than it solves: Just like function calls, objects simply do not travel
		1198	easily over the network, mostly because they will always be a copy, so you
		1199	always have to re-think your design.
		1200
		1201	Keeping your messages simple, concentrating on data structures rather than
		1202	objects, will keep your messages clean, tidy and efficient.
		1203
		1204	=back
		1205
652	=head1 SEE ALSO	1206	=head1 SEE ALSO
		1207
		1208	L<AnyEvent::MP::Intro> - a gentle introduction.
		1209
		1210	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.
		1211
		1212	L<AnyEvent::MP::Global> - network maintenance and port groups, to find
		1213	your applications.
		1214
		1215	L<AnyEvent::MP::DataConn> - establish data connections between nodes.
		1216
		1217	L<AnyEvent::MP::LogCatcher> - simple service to display log messages from
		1218	all nodes.
653		1219
654	L<AnyEvent>.	1220	L<AnyEvent>.
655		1221
656	=head1 AUTHOR	1222	=head1 AUTHOR
657		1223

Diff Legend

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