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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.33 by root, Wed Aug 5 22:40:51 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
		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 $localport, $cb->(@msg) # callback is invoked on death
		41	mon $localport, $otherport # kill otherport on abnormal 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	};
		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<#>) as
57	separator, and a port name (a printable string of unspecified format). An	88	separator, and a port name (a printable string of unspecified format).
58	exception is the the node port, whose ID is identical to its node
59	reference.
60		89
61	=item node	90	=item node
62		91
63	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,
64	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
65	create new ports, among other things.	94	ports.
66		95
67	Nodes are either private (single-process only), slaves (connected to a	96	Nodes are either public (have one or more listening ports) or private
68	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.
69		99
70	=item noderef - C<host:port,host:port...>, C<id@noderef>, C<id>	100	Nodes is represented by (printable) strings called "node IDs".
71		101
72	A node reference is a string that either simply identifies the node (for	102	=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		103
76	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
77	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.
78		108
79	Node references come in two flavours: resolved (containing only numerical	109	=item binds - C<ip:port>
80	addresses) or unresolved (where hostnames are used instead of addresses).
81		110
82	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
83	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).
84		169
85	=back	170	=back
86		171
87	=head1 VARIABLES/FUNCTIONS	172	=head1 VARIABLES/FUNCTIONS
88		173
90		175
91	=cut	176	=cut
92		177
93	package AnyEvent::MP;	178	package AnyEvent::MP;
94		179
		180	use AnyEvent::MP::Config ();
95	use AnyEvent::MP::Base;	181	use AnyEvent::MP::Kernel;
		182	use AnyEvent::MP::Kernel qw(%NODE %PORT %PORT_DATA $UNIQ $RUNIQ $ID);
96		183
97	use common::sense;	184	use common::sense;
98		185
99	use Carp ();	186	use Carp ();
100		187
101	use AE ();	188	use AE ();
102		189
103	use base "Exporter";	190	use base "Exporter";
104		191
105	our $VERSION = '0.1';	192	our $VERSION = $AnyEvent::MP::Config::VERSION;
		193
106	our @EXPORT = qw(	194	our @EXPORT = qw(
107	NODE $NODE *SELF node_of _any_	195	NODE $NODE *SELF node_of after
108	resolve_node initialise_node	196	configure
109	snd rcv mon kil reg psub	197	snd rcv mon mon_guard kil psub peval spawn cal
110	port	198	port
111	);	199	);
112		200
113	our $SELF;	201	our $SELF;
114		202
…		…
118	kil $SELF, die => $msg;	206	kil $SELF, die => $msg;
119	}	207	}
120		208
121	=item $thisnode = NODE / $NODE	209	=item $thisnode = NODE / $NODE
122		210
123	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
124	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
125	to C<become_public> or C<become_slave>, after which all local port	213	a call to C<configure>.
126	identifiers become invalid.
127		214
128	=item $noderef = node_of $port	215	=item $nodeid = node_of $port
129		216
130	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.
131		218
132	=item $cv = resolve_node $noderef	219	=item configure $profile, key => value...
133		220
134	Takes an unresolved node reference that may contain hostnames and	221	=item configure key => value...
135	abbreviated IDs, resolves all of them and returns a resolved node
136	reference.
137		222
138	In addition to C<address:port> pairs allowed in resolved noderefs, the	223	Before a node can talk to other nodes on the network (i.e. enter
139	following forms are supported:	224	"distributed mode") it has to configure itself - the minimum a node needs
		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.
		227
		228	This function configures a node - it must be called exactly once (or
		229	never) before calling other AnyEvent::MP functions.
		230
		231	The key/value pairs are basically the same ones as documented for the
		232	F<aemp> command line utility (sans the set/del prefix), with two additions:
140		233
141	=over 4	234	=over 4
142		235
143	=item the empty string	236	=item norc => $boolean (default false)
144		237
145	An empty-string component gets resolved as if the default port (4040) was	238	If true, then the rc file (e.g. F<~/.perl-anyevent-mp>) will I<not>
146	specified.	239	be consulted - all configuraiton options must be specified in the
		240	C<configure> call.
147		241
148	=item naked port numbers (e.g. C<1234>)	242	=item force => $boolean (default false)
149		243
150	These are resolved by prepending the local nodename and a colon, to be	244	IF true, then the values specified in the C<configure> will take
151	further resolved.	245	precedence over any values configured via the rc file. The default is for
152		246	the rc file to override any options specified in the program.
153	=item hostnames (e.g. C<localhost:1234>, C<localhost>)
154
155	These are resolved by using AnyEvent::DNS to resolve them, optionally
156	looking up SRV records for the C<aemp=4040> port, if no port was
157	specified.
158		247
159	=back	248	=back
		249
		250	=over 4
		251
		252	=item step 1, gathering configuration from profiles
		253
		254	The function first looks up a profile in the aemp configuration (see the
		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.
		258
		259	The profile data is then gathered as follows:
		260
		261	First, all remaining key => value pairs (all of which are conveniently
		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).
		266
		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.
		270
		271	If the profile specifies a node ID, then this will become the node ID of
		272	this process. If not, then the profile name will be used as node ID. The
		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.
		292
		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)"
160		320
161	=item $SELF	321	=item $SELF
162		322
163	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>
164	blocks.	324	blocks.
165		325
166	=item SELF, %SELF, @SELF...	326	=item *SELF, SELF, %SELF, @SELF...
167		327
168	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
169	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
170	module, but only C<$SELF> is currently used.	330	module, but only C<$SELF> is currently used.
171		331
172	=item snd $port, type => @data	332	=item snd $port, type => @data
173		333
174	=item snd $port, @msg	334	=item snd $port, @msg
175		335
176	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
177	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.
178	stringifies a sa port ID (such as a port object :).
179		338
180	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
181	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
182	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.
183		343
184	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
185	function: modifying any argument is not allowed and can cause many	345	function: modifying any argument (or values referenced by them) is
186	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.
187		350
188	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
189	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
190	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
191	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
192	node, anything can be passed.	355	node, anything can be passed. Best rely only on the common denominator of
		356	these.
193		357
194	=item $local_port = port	358	=item $local_port = port
195		359
196	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
197	matching port ("full port") or a single-callback port ("miniport"),	361	no callbacks set and will throw an error when it receives messages.
198	depending on how C<rcv> callbacks are bound to the object.
199		362
200	=item $port = port { my @msg = @_; $finished }	363	=item $local_port = port { my @msg = @_ }
201		364
202	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
203	matching behind it, and returns its ID. Semantically the same as creating
204	a port and calling C<rcv $port, $callback> on it.	366	creating a port and calling C<rcv $port, $callback> on it.
205		367
206	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
207	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
208	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.
209		372
210	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:
211	be passed to the callback.
212		374
213	If you need the local port id in the callback, this works nicely:	375	my $port = port {
214		376	my @msg = @_;
215	my $port; $port = port {	377	...
216	snd $otherport, reply => $port;	378	kil $SELF;
217	};	379	};
218		380
219	=cut	381	=cut
220		382
221	sub rcv($@);	383	sub rcv($@);
222		384
		385	sub _kilme {
		386	die "received message on port without callback";
		387	}
		388
223	sub port(;&) {	389	sub port(;&) {
224	my $id = "$UNIQ." . $ID++;	390	my $id = "$UNIQ." . ++$ID;
225	my $port = "$NODE#$id";	391	my $port = "$NODE#$id";
226		392
227	if (@_) {	393	rcv $port, shift \|\| \&_kilme;
228	rcv $port, shift;
229	} else {
230	$PORT{$id} = sub { }; # nop
231	}
232		394
233	$port	395	$port
234	}	396	}
235		397
236	=item reg $port, $name
237
238	Registers the given port under the name C<$name>. If the name already
239	exists it is replaced.
240
241	A port can only be registered under one well known name.
242
243	A port automatically becomes unregistered when it is killed.
244
245	=cut
246
247	sub reg(@) {
248	my ($port, $name) = @_;
249
250	$REG{$name} = $port;
251	}
252
253	=item rcv $port, $callback->(@msg)	398	=item rcv $local_port, $callback->(@msg)
254		399
255	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
256	one if required).	401	remove the default callback: use C<sub { }> to disable it, or better
257		402	C<kil> the port when it is no longer needed.
258	=item rcv $port, tagstring => $callback->(@msg), ...
259
260	=item rcv $port, $smartmatch => $callback->(@msg), ...
261
262	=item rcv $port, [$smartmatch...] => $callback->(@msg), ...
263
264	Register callbacks to be called on matching messages on the given full
265	port (after converting it to one if required).
266
267	The callback has to return a true value when its work is done, after
268	which is will be removed, or a false value in which case it will stay
269	registered.
270		403
271	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
272	executing the callback.	405	executing the callback. Runtime errors during callback execution will
		406	result in the port being C<kil>ed.
273		407
274	Runtime errors wdurign callback execution will result in the port being	408	The default callback received all messages not matched by a more specific
275	C<kil>ed.	409	C<tag> match.
276		410
277	If the match is an array reference, then it will be matched against the	411	=item rcv $local_port, tag => $callback->(@msg_without_tag), ...
278	first elements of the message, otherwise only the first element is being
279	matched.
280		412
281	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
282	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.
283		417
284	While not required, it is highly recommended that the first matching	418	The original message will be passed to the callback, after the first
285	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
286	also the most efficient match (by far).	420	environment as the default callback (see above).
		421
		422	Example: create a port and bind receivers on it in one go.
		423
		424	my $port = rcv port,
		425	msg1 => sub { ... },
		426	msg2 => sub { ... },
		427	;
		428
		429	Example: create a port, bind receivers and send it in a message elsewhere
		430	in one go:
		431
		432	snd $otherport, reply =>
		433	rcv port,
		434	msg1 => sub { ... },
		435	...
		436	;
		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	};
287		446
288	=cut	447	=cut
289		448
290	sub rcv($@) {	449	sub rcv($@) {
291	my $port = shift;	450	my $port = shift;
292	my ($noderef, $portid) = split /#/, $port, 2;	451	my ($nodeid, $portid) = split /#/, $port, 2;
293		452
294	($NODE{$noderef} \|\| add_node $noderef) == $NODE{""}	453	$NODE{$nodeid} == $NODE{""}
295	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";
296		455
297	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 {
298	my $cb = shift;	464	my $cb = shift;
299	delete $PORT_DATA{$portid};
300	$PORT{$portid} = sub {	465	$PORT{$portid} = sub {
301	local $SELF = $port;	466	local $SELF = $port;
302	eval {	467	eval { &$cb }; _self_die if $@;
303	&$cb	468	};
304	and kil $port;
305	};	469	}
306	_self_die if $@;	470	} elsif (defined $_[0]) {
307	};
308	} else {
309	my $self = $PORT_DATA{$portid} \|\|= do {	471	my $self = $PORT_DATA{$portid} \|\|= do {
310	my $self = bless {	472	my $self = bless [$PORT{$portid} \|\| sub { }, { }, $port], "AnyEvent::MP::Port";
311	id => $port,
312	}, "AnyEvent::MP::Port";
313		473
314	$PORT{$portid} = sub {	474	$PORT{$portid} = sub {
315	local $SELF = $port;	475	local $SELF = $port;
316		476
317	eval {
318	for (@{ $self->{rc0}{$_[0]} }) {	477	if (my $cb = $self->[1]{$_[0]}) {
319	$_ && &{$_->[0]}	478	shift;
320	&& undef $_;	479	eval { &$cb }; _self_die if $@;
321	}	480	} else {
322
323	for (@{ $self->{rcv}{$_[0]} }) {
324	$_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1]
325	&& &{$_->[0]}	481	&{ $self->[0] };
326	&& undef $_;
327	}
328
329	for (@{ $self->{any} }) {
330	$_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1]
331	&& &{$_->[0]}
332	&& undef $_;
333	}	482	}
334	};	483	};
335	_self_die if $@;	484
		485	$self
336	};	486	};
337		487
338	$self
339	};
340
341	"AnyEvent::MP::Port" eq ref $self	488	"AnyEvent::MP::Port" eq ref $self
342	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";
343		490
344	while (@_) {
345	my ($match, $cb) = splice @_, 0, 2;	491	my ($tag, $cb) = splice @_, 0, 2;
346		492
347	if (!ref $match) {	493	if (defined $cb) {
348	push @{ $self->{rc0}{$match} }, [$cb];	494	$self->[1]{$tag} = $cb;
349	} elsif (("ARRAY" eq ref $match && !ref $match->[0])) {
350	my ($type, @match) = @$match;
351	@match
352	? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match]
353	: push @{ $self->{rc0}{$match->[0]} }, [$cb];
354	} else {	495	} else {
355	push @{ $self->{any} }, [$cb, $match];	496	delete $self->[1]{$tag};
356	}	497	}
357	}	498	}
358	}	499	}
359		500
360	$port	501	$port
361	}	502	}
362		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
363	=item $closure = psub { BLOCK }	541	=item $closure = psub { BLOCK }
364		542
365	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
366	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>
367	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 }, @_ } >>.
368		549
369	This is useful when you register callbacks from C<rcv> callbacks:	550	This is useful when you register callbacks from C<rcv> callbacks:
370		551
371	rcv delayed_reply => sub {	552	rcv delayed_reply => sub {
372	my ($delay, @reply) = @_;	553	my ($delay, @reply) = @_;
…		…
396	$res	577	$res
397	}	578	}
398	}	579	}
399	}	580	}
400		581
401	=item $guard = mon $port, $cb->(@reason)	582	=item $guard = mon $port, $cb->(@reason) # call $cb when $port dies
402		583
403	=item $guard = mon $port, $otherport	584	=item $guard = mon $port, $rcvport # kill $rcvport when $port dies
404		585
405	=item $guard = mon $port, $otherport, @msg	586	=item $guard = mon $port # kill $SELF when $port dies
406		587
		588	=item $guard = mon $port, $rcvport, @msg # send a message when $port dies
		589
407	Monitor the given port and do something when the port is killed.	590	Monitor the given port and do something when the port is killed or
		591	messages to it were lost, and optionally return a guard that can be used
		592	to stop monitoring again.
408		593
409	In the first form, the callback is simply called with any number	594	In the first form (callback), the callback is simply called with any
410	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
411	"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
412	C<eval> if unsure.	597	C<eval> if unsure.
413		598
414	In the second form, the other port will be C<kil>'ed with C<@reason>, iff	599	In the second form (another port given), the other port (C<$rcvport>)
415	a @reason was specified, i.e. on "normal" kils nothing happens, while	600	will be C<kil>'ed with C<@reason>, if a @reason was specified, i.e. on
416	under all other conditions, the other port is killed with the same reason.	601	"normal" kils nothing happens, while under all other conditions, the other
		602	port is killed with the same reason.
417		603
		604	The third form (kill self) is the same as the second form, except that
		605	C<$rvport> defaults to C<$SELF>.
		606
418	In the last form, a message of the form C<@msg, @reason> will be C<snd>.	607	In the last form (message), a message of the form C<@msg, @reason> will be
		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.
		612
		613	As a rule of thumb, monitoring requests should always monitor a port from
		614	a local port (or callback). The reason is that kill messages might get
		615	lost, just like any other message. Another less obvious reason is that
		616	even monitoring requests can get lost (for example, when the connection
		617	to the other node goes down permanently). When monitoring a port locally
		618	these problems do not exist.
		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.
419		636
420	Example: call a given callback when C<$port> is killed.	637	Example: call a given callback when C<$port> is killed.
421		638
422	mon $port, sub { warn "port died because of <@_>\n" };	639	mon $port, sub { warn "port died because of <@_>\n" };
423		640
424	Example: kill ourselves when C<$port> is killed abnormally.	641	Example: kill ourselves when C<$port> is killed abnormally.
425		642
426	mon $port, $self;	643	mon $port;
427		644
428	Example: send us a restart message another C<$port> is killed.	645	Example: send us a restart message when another C<$port> is killed.
429		646
430	mon $port, $self => "restart";	647	mon $port, $self => "restart";
431		648
432	=cut	649	=cut
433		650
434	sub mon {	651	sub mon {
435	my ($noderef, $port) = split /#/, shift, 2;	652	my ($nodeid, $port) = split /#/, shift, 2;
436		653
437	my $node = $NODE{$noderef} \|\| add_node $noderef;	654	my $node = $NODE{$nodeid} \|\| add_node $nodeid;
438		655
439	my $cb = shift;	656	my $cb = @_ ? shift : $SELF \|\| Carp::croak 'mon: called with one argument only, but $SELF not set,';
440		657
441	unless (ref $cb) {	658	unless (ref $cb) {
442	if (@_) {	659	if (@_) {
443	# send a kill info message	660	# send a kill info message
444	my (@msg) = ($cb, @_);	661	my (@msg) = ($cb, @_);
…		…
451	}	668	}
452		669
453	$node->monitor ($port, $cb);	670	$node->monitor ($port, $cb);
454		671
455	defined wantarray	672	defined wantarray
456	and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }	673	and ($cb += 0, AnyEvent::Util::guard { $node->unmonitor ($port, $cb) })
457	}	674	}
458		675
459	=item $guard = mon_guard $port, $ref, $ref...	676	=item $guard = mon_guard $port, $ref, $ref...
460		677
461	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
462	is killed, the references will be freed.	679	is killed, the references will be freed.
463		680
464	Optionally returns a guard that will stop the monitoring.	681	Optionally returns a guard that will stop the monitoring.
465		682
466	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
467	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>):
468		685
469	$port->rcv (start => sub {	686	$port->rcv (start => sub {
470	my $timer; $timer = mon_guard $port, AE::timer 1, 1, sub {	687	my $timer; $timer = mon_guard $port, AE::timer 1, 1, psub {
471	undef $timer if 0.9 < rand;	688	undef $timer if 0.9 < rand;
472	});	689	});
473	});	690	});
474		691
475	=cut	692	=cut
476		693
477	sub mon_guard {	694	sub mon_guard {
478	my ($port, @refs) = @_;	695	my ($port, @refs) = @_;
479		696
		697	#TODO: mon-less form?
		698
480	mon $port, sub { 0 && @refs }	699	mon $port, sub { 0 && @refs }
481	}	700	}
482		701
483	=item lnk $port1, $port2
484
485	Link two ports. This is simply a shorthand for:
486
487	mon $port1, $port2;
488	mon $port2, $port1;
489
490	It means that if either one is killed abnormally, the other one gets
491	killed as well.
492
493	=item kil $port[, @reason]	702	=item kil $port[, @reason]
494		703
495	Kill the specified port with the given C<@reason>.	704	Kill the specified port with the given C<@reason>.
496		705
497	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" -
498	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.
499		709
500	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>
501	C<mon>, see below).	711	form) get killed with the same reason.
502		712
503	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
504	will be reported as reason C<< die => $@ >>.	714	will be reported as reason C<< die => $@ >>.
505		715
506	Transport/communication errors are reported as C<< transport_error =>	716	Transport/communication errors are reported as C<< transport_error =>
507	$message >>.	717	$message >>.
508		718
		719	=cut
		720
		721	=item $port = spawn $node, $initfunc[, @initdata]
		722
		723	Creates a port on the node C<$node> (which can also be a port ID, in which
		724	case it's the node where that port resides).
		725
		726	The port ID of the newly created port is returned immediately, and it is
		727	possible to immediately start sending messages or to monitor the port.
		728
		729	After the port has been created, the init function is called on the remote
		730	node, in the same context as a C<rcv> callback. This function must be a
		731	fully-qualified function name (e.g. C<MyApp::Chat::Server::init>). To
		732	specify a function in the main program, use C<::name>.
		733
		734	If the function doesn't exist, then the node tries to C<require>
		735	the package, then the package above the package and so on (e.g.
		736	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
		737	exists or it runs out of package names.
		738
		739	The init function is then called with the newly-created port as context
		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.
		743
		744	A common idiom is to pass a local port, immediately monitor the spawned
		745	port, and in the remote init function, immediately monitor the passed
		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).
		752
		753	Example: spawn a chat server port on C<$othernode>.
		754
		755	# this node, executed from within a port context:
		756	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;
		757	mon $server;
		758
		759	# init function on C<$othernode>
		760	sub connect {
		761	my ($srcport) = @_;
		762
		763	mon $srcport;
		764
		765	rcv $SELF, sub {
		766	...
		767	};
		768	}
		769
		770	=cut
		771
		772	sub _spawn {
		773	my $port = shift;
		774	my $init = shift;
		775
		776	# rcv will create the actual port
		777	local $SELF = "$NODE#$port";
		778	eval {
		779	&{ load_func $init }
		780	};
		781	_self_die if $@;
		782	}
		783
		784	sub spawn(@) {
		785	my ($nodeid, undef) = split /#/, shift, 2;
		786
		787	my $id = "$RUNIQ." . ++$ID;
		788
		789	$_[0] =~ /::/
		790	or Carp::croak "spawn init function must be a fully-qualified name, caught";
		791
		792	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;
		793
		794	"$nodeid#$id"
		795	}
		796
		797
		798	=item after $timeout, @msg
		799
		800	=item after $timeout, $callback
		801
		802	Either sends the given message, or call the given callback, after the
		803	specified number of seconds.
		804
		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.
		808
		809	=cut
		810
		811	sub after($@) {
		812	my ($timeout, @action) = @_;
		813
		814	my $t; $t = AE::timer $timeout, 0, sub {
		815	undef $t;
		816	ref $action[0]
		817	? $action[0]()
		818	: snd @action;
		819	};
		820	}
		821
		822	=item cal $port, @msg, $callback[, $timeout]
		823
		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.
		826
		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.
		829
		830	A reply message sent to the port is passed to the C<$callback> as-is.
		831
		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.
		835
		836	If no time-out is given (or it is C<undef>), then the local port will
		837	monitor the remote port instead, so it eventually gets cleaned-up.
		838
		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.
		842
		843	=cut
		844
		845	sub cal(@) {
		846	my $timeout = ref $_[-1] ? undef : pop;
		847	my $cb = pop;
		848
		849	my $port = port {
		850	undef $timeout;
		851	kil $SELF;
		852	&$cb;
		853	};
		854
		855	if (defined $timeout) {
		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	}
		867
		868	push @_, $port;
		869	&snd;
		870
		871	$port
		872	}
		873
509	=back	874	=back
510		875
511	=head1 FUNCTIONS FOR NODES
512
513	=over 4
514
515	=item initialise_node $noderef, $seednode, $seednode...
516
517	=item initialise_node "slave/", $master, $master...
518
519	Initialises a node - must be called exactly once before calling other
520	AnyEvent::MP functions when talking to other nodes is required.
521
522	All arguments are noderefs, which can be either resolved or unresolved.
523
524	There are two types of networked nodes, public nodes and slave nodes:
525
526	=over 4
527
528	=item public nodes
529
530	For public nodes, C<$noderef> must either be a (possibly unresolved)
531	noderef, in which case it will be resolved, or C<undef> (or missing), in
532	which case the noderef will be guessed.
533
534	Afterwards, the node will bind itself on all endpoints and try to connect
535	to all additional C<$seednodes> that are specified. Seednodes are optional
536	and can be used to quickly bootstrap the node into an existing network.
537
538	=item slave nodes
539
540	When the C<$noderef> is the special string C<slave/>, then the node will
541	become a slave node. Slave nodes cannot be contacted from outside and will
542	route most of their traffic to the master node that they attach to.
543
544	At least one additional noderef is required: The node will try to connect
545	to all of them and will become a slave attached to the first node it can
546	successfully connect to.
547
548	=back
549
550	This function will block until all nodes have been resolved and, for slave
551	nodes, until it has successfully established a connection to a master
552	server.
553
554	Example: become a public node listening on the default node.
555
556	initialise_node;
557
558	Example: become a public node, and try to contact some well-known master
559	servers to become part of the network.
560
561	initialise_node undef, "master1", "master2";
562
563	Example: become a public node listening on port C<4041>.
564
565	initialise_node 4041;
566
567	Example: become a public node, only visible on localhost port 4044.
568
569	initialise_node "locahost:4044";
570
571	Example: become a slave node to any of the specified master servers.
572
573	initialise_node "slave/", "master1", "192.168.13.17", "mp.example.net";
574
575	=cut
576
577	=back
578
579	=head1 NODE MESSAGES
580
581	Nodes understand the following messages sent to them. Many of them take
582	arguments called C<@reply>, which will simply be used to compose a reply
583	message - C<$reply[0]> is the port to reply to, C<$reply[1]> the type and
584	the remaining arguments are simply the message data.
585
586	While other messages exist, they are not public and subject to change.
587
588	=over 4
589
590	=cut
591
592	=item lookup => $name, @reply
593
594	Replies with the port ID of the specified well-known port, or C<undef>.
595
596	=item devnull => ...
597
598	Generic data sink/CPU heat conversion.
599
600	=item relay => $port, @msg
601
602	Simply forwards the message to the given port.
603
604	=item eval => $string[ @reply]
605
606	Evaluates the given string. If C<@reply> is given, then a message of the
607	form C<@reply, $@, @evalres> is sent.
608
609	Example: crash another node.
610
611	snd $othernode, eval => "exit";
612
613	=item time => @reply
614
615	Replies the the current node time to C<@reply>.
616
617	Example: tell the current node to send the current time to C<$myport> in a
618	C<timereply> message.
619
620	snd $NODE, time => $myport, timereply => 1, 2;
621	# => snd $myport, timereply => 1, 2, <time>
622
623	=back
624
625	=head1 AnyEvent::MP vs. Distributed Erlang	876	=head1 AnyEvent::MP vs. Distributed Erlang
626		877
627	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
628	== 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
629	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
630	sample:	881	sample:
631		882
632	http://www.erlang.se/doc/programming_rules.shtml	883	http://www.erlang.se/doc/programming_rules.shtml
633	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
634	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
…		…
636		887
637	Despite the similarities, there are also some important differences:	888	Despite the similarities, there are also some important differences:
638		889
639	=over 4	890	=over 4
640		891
641	=item * Node references contain the recipe on how to contact them.	892	=item * Node IDs are arbitrary strings in AEMP.
642		893
643	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
644	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
645	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.
646		898
647	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
648	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.
649		913
650	=item * Erlang uses processes and a mailbox, AEMP does not queue.	914	=item * Erlang uses processes and a mailbox, AEMP does not queue.
651		915
652	Erlang uses processes that selctively receive messages, and therefore	916	Erlang uses processes that selectively receive messages out of order, and
653	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
654	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.
655		921
656	(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.
657		927
658	=item * Erlang sends are synchronous, AEMP sends are asynchronous.	928	=item * Erlang sends are synchronous, AEMP sends are asynchronous.
659		929
660	Sending messages in erlang is synchronous and blocks the process. AEMP	930	Sending messages in Erlang is synchronous and blocks the process until
661	sends are immediate, connection establishment is handled in the	931	a conenction has been established and the message sent (and so does not
662	background.	932	need a queue that can overflow). AEMP sends return immediately, connection
		933	establishment is handled in the background.
663		934
664	=item * Erlang can silently lose messages, AEMP cannot.	935	=item * Erlang suffers from silent message loss, AEMP does not.
665		936
666	Erlang makes few guarantees on messages delivery - messages can get lost	937	Erlang implements few guarantees on messages delivery - messages can get
667	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,
668	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).
669		940
670	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
671	holes in the message sequence.	944	no silent "holes" in the message sequence.
672		945
673	=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
674	alive.	947	corrupted and even out-of-order messages in both Erlang and AEMP. AEMP
675		948	simply tries to work better in common error cases, such as when a network
676	In erlang it can happen that a monitored process is declared dead and	949	link goes down.
677	linked processes get killed, but later it turns out that the process is
678	still alive - and can receive messages.
679
680	In AEMP, when port monitoring detects a port as dead, then that port will
681	eventually be killed - it cannot happen that a node detects a port as dead
682	and then later sends messages to it, finding it is still alive.
683		950
684	=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.
685		952
686	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
687	ID known to other nodes for a completely different process, causing	954	process ID known to other nodes for a completely different process,
688	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.
689		957
690	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
691	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.
692		960
693	=item * Erlang uses unprotected connections, AEMP uses secure	961	=item * Erlang uses unprotected connections, AEMP uses secure
694	authentication and can use TLS.	962	authentication and can use TLS.
695		963
696	AEMP can use a proven protocol - SSL/TLS - to protect connections and	964	AEMP can use a proven protocol - TLS - to protect connections and
697	securely authenticate nodes.	965	securely authenticate nodes.
698		966
699	=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
700	communications.	968	communications.
701		969
702	The AEMP protocol, unlike the erlang protocol, supports both	970	The AEMP protocol, unlike the Erlang protocol, supports both programming
703	language-independent text-only protocols (good for debugging) and binary,	971	language independent text-only protocols (good for debugging), and binary,
704	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.
705		974
706	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
707	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
708	protocol simple.	977	protocol simple.
709		978
		979	=item * AEMP has more flexible monitoring options than Erlang.
		980
		981	In Erlang, you can chose to receive I<all> exit signals as messages or
		982	I<none>, there is no in-between, so monitoring single Erlang processes is
		983	difficult to implement.
		984
		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.
		987
		988	=item * Erlang tries to hide remote/local connections, AEMP does not.
		989
		990	Monitoring in Erlang is not an indicator of process death/crashes, in the
		991	same way as linking is (except linking is unreliable in Erlang).
		992
		993	In AEMP, you don't "look up" registered port names or send to named ports
		994	that might or might not be persistent. Instead, you normally spawn a port
		995	on the remote node. The init function monitors you, and you monitor the
		996	remote port. Since both monitors are local to the node, they are much more
		997	reliable (no need for C<spawn_link>).
		998
		999	This also saves round-trips and avoids sending messages to the wrong port
		1000	(hard to do in Erlang).
		1001
710	=back	1002	=back
711		1003
		1004	=head1 RATIONALE
		1005
		1006	=over 4
		1007
		1008	=item Why strings for port and node IDs, why not objects?
		1009
		1010	We considered "objects", but found that the actual number of methods
		1011	that can be called are quite low. Since port and node IDs travel over
		1012	the network frequently, the serialising/deserialising would add lots of
		1013	overhead, as well as having to keep a proxy object everywhere.
		1014
		1015	Strings can easily be printed, easily serialised etc. and need no special
		1016	procedures to be "valid".
		1017
		1018	And as a result, a port with just a default receiver consists of a single
		1019	code reference stored in a global hash - it can't become much cheaper.
		1020
		1021	=item Why favour JSON, why not a real serialising format such as Storable?
		1022
		1023	In fact, any AnyEvent::MP node will happily accept Storable as framing
		1024	format, but currently there is no way to make a node use Storable by
		1025	default (although all nodes will accept it).
		1026
		1027	The default framing protocol is JSON because a) JSON::XS is many times
		1028	faster for small messages and b) most importantly, after years of
		1029	experience we found that object serialisation is causing more problems
		1030	than it solves: Just like function calls, objects simply do not travel
		1031	easily over the network, mostly because they will always be a copy, so you
		1032	always have to re-think your design.
		1033
		1034	Keeping your messages simple, concentrating on data structures rather than
		1035	objects, will keep your messages clean, tidy and efficient.
		1036
		1037	=back
		1038
712	=head1 SEE ALSO	1039	=head1 SEE ALSO
		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.
713		1052
714	L<AnyEvent>.	1053	L<AnyEvent>.
715		1054
716	=head1 AUTHOR	1055	=head1 AUTHOR
717		1056

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.33 by root, Wed Aug 5 22:40:51 2009 UTC vs. Revision 1.121 by root, Tue Feb 28 18:37:24 2012 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.33 by root, Wed Aug 5 22:40:51 2009 UTC vs.
Revision 1.121 by root, Tue Feb 28 18:37:24 2012 UTC