[ViewVC] Diff of: cvs/cvsroot/AnyEvent-MP/MP.pm

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

Diff Legend

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

Comparing cvsroot/AnyEvent-MP/MP.pm (file contents): Revision 1.48 by root, Thu Aug 13 02:59:42 2009 UTC vs. Revision 1.121 by root, Tue Feb 28 18:37:24 2012 UTC

Diff Legend

Comparing cvsroot/AnyEvent-MP/MP.pm (file contents):
Revision 1.48 by root, Thu Aug 13 02:59:42 2009 UTC vs.
Revision 1.121 by root, Tue Feb 28 18:37:24 2012 UTC