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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.75 by root, Mon Aug 31 13:18:06 2009 UTC vs.
Revision 1.147 by root, Mon Jun 20 16:58:15 2016 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
30	rcv $port, pong => sub { warn "pong received\n" };	30	rcv $port, pong => sub { warn "pong received\n" };
31		31
32	# create a port on another node	32	# create a port on another node
33	my $port = spawn $node, $initfunc, @initdata;	33	my $port = spawn $node, $initfunc, @initdata;
34		34
		35	# destroy a port again
		36	kil $port; # "normal" kill
		37	kil $port, my_error => "everything is broken"; # error kill
		38
35	# monitoring	39	# monitoring
36	mon $port, $cb->(@msg) # callback is invoked on death	40	mon $port, $cb->(@msg) # callback is invoked on death
37	mon $port, $otherport # kill otherport on abnormal death	41	mon $port, $localport # kill localport on abnormal death
38	mon $port, $otherport, @msg # send message on death	42	mon $port, $localport, @msg # send message on death
39		43
40	=head1 CURRENT STATUS	44	# temporarily execute code in port context
		45	peval $port, sub { die "kill the port!" };
41		46
42	bin/aemp - stable.	47	# execute callbacks in $SELF port context
43	AnyEvent::MP - stable API, should work.	48	my $timer = AE::timer 1, 0, psub {
44	AnyEvent::MP::Intro - uptodate, but incomplete.	49	die "kill the port, delayed";
45	AnyEvent::MP::Kernel - mostly stable.	50	};
46	AnyEvent::MP::Global - stable API, protocol not yet final.
47		51
48	stay tuned.	52	# distributed database - modification
		53	db_set $family => $subkey [=> $value] # add a subkey
		54	db_del $family => $subkey... # delete one or more subkeys
		55	db_reg $family => $port [=> $value] # register a port
		56
		57	# distributed database - queries
		58	db_family $family => $cb->(\%familyhash)
		59	db_keys $family => $cb->(\@keys)
		60	db_values $family => $cb->(\@values)
		61
		62	# distributed database - monitoring a family
		63	db_mon $family => $cb->(\%familyhash, \@added, \@changed, \@deleted)
49		64
50	=head1 DESCRIPTION	65	=head1 DESCRIPTION
51		66
52	This module (-family) implements a simple message passing framework.	67	This module (-family) implements a simple message passing framework.
53		68
…		…
55	on the same or other hosts, and you can supervise entities remotely.	70	on the same or other hosts, and you can supervise entities remotely.
56		71
57	For an introduction to this module family, see the L<AnyEvent::MP::Intro>	72	For an introduction to this module family, see the L<AnyEvent::MP::Intro>
58	manual page and the examples under F<eg/>.	73	manual page and the examples under F<eg/>.
59		74
60	At the moment, this module family is a bit underdocumented.
61
62	=head1 CONCEPTS	75	=head1 CONCEPTS
63		76
64	=over 4	77	=over 4
65		78
66	=item port	79	=item port
67		80
68	A port is something you can send messages to (with the C<snd> function).	81	Not to be confused with a TCP port, a "port" is something you can send
		82	messages to (with the C<snd> function).
69		83
70	Ports allow you to register C<rcv> handlers that can match all or just	84	Ports allow you to register C<rcv> handlers that can match all or just
71	some messages. Messages send to ports will not be queued, regardless of	85	some messages. Messages send to ports will not be queued, regardless of
72	anything was listening for them or not.	86	anything was listening for them or not.
73		87
		88	Ports are represented by (printable) strings called "port IDs".
		89
74	=item port ID - C<nodeid#portname>	90	=item port ID - C<nodeid#portname>
75		91
76	A port ID is the concatenation of a node ID, a hash-mark (C<#>) as	92	A port ID is the concatenation of a node ID, a hash-mark (C<#>)
77	separator, and a port name (a printable string of unspecified format).	93	as separator, and a port name (a printable string of unspecified
		94	format created by AnyEvent::MP).
78		95
79	=item node	96	=item node
80		97
81	A node is a single process containing at least one port - the node port,	98	A node is a single process containing at least one port - the node port,
82	which enables nodes to manage each other remotely, and to create new	99	which enables nodes to manage each other remotely, and to create new
83	ports.	100	ports.
84		101
85	Nodes are either public (have one or more listening ports) or private	102	Nodes are either public (have one or more listening ports) or private
86	(no listening ports). Private nodes cannot talk to other private nodes	103	(no listening ports). Private nodes cannot talk to other private nodes
87	currently.	104	currently, but all nodes can talk to public nodes.
88		105
		106	Nodes is represented by (printable) strings called "node IDs".
		107
89	=item node ID - C<[a-za-Z0-9_\-.:]+>	108	=item node ID - C<[A-Za-z0-9_\-.:]*>
90		109
91	A node ID is a string that uniquely identifies the node within a	110	A node ID is a string that uniquely identifies the node within a
92	network. Depending on the configuration used, node IDs can look like a	111	network. Depending on the configuration used, node IDs can look like a
93	hostname, a hostname and a port, or a random string. AnyEvent::MP itself	112	hostname, a hostname and a port, or a random string. AnyEvent::MP itself
94	doesn't interpret node IDs in any way.	113	doesn't interpret node IDs in any way except to uniquely identify a node.
95		114
96	=item binds - C<ip:port>	115	=item binds - C<ip:port>
97		116
98	Nodes can only talk to each other by creating some kind of connection to	117	Nodes can only talk to each other by creating some kind of connection to
99	each other. To do this, nodes should listen on one or more local transport	118	each other. To do this, nodes should listen on one or more local transport
		119	endpoints - binds.
		120
100	endpoints - binds. Currently, only standard C<ip:port> specifications can	121	Currently, only standard C<ip:port> specifications can be used, which
101	be used, which specify TCP ports to listen on.	122	specify TCP ports to listen on. So a bind is basically just a tcp socket
		123	in listening mode that accepts connections from other nodes.
102		124
		125	=item seed nodes
		126
		127	When a node starts, it knows nothing about the network it is in - it
		128	needs to connect to at least one other node that is already in the
		129	network. These other nodes are called "seed nodes".
		130
		131	Seed nodes themselves are not special - they are seed nodes only because
		132	some other node I<uses> them as such, but any node can be used as seed
		133	node for other nodes, and eahc node can use a different set of seed nodes.
		134
		135	In addition to discovering the network, seed nodes are also used to
		136	maintain the network - all nodes using the same seed node are part of the
		137	same network. If a network is split into multiple subnets because e.g. the
		138	network link between the parts goes down, then using the same seed nodes
		139	for all nodes ensures that eventually the subnets get merged again.
		140
		141	Seed nodes are expected to be long-running, and at least one seed node
		142	should always be available. They should also be relatively responsive - a
		143	seed node that blocks for long periods will slow down everybody else.
		144
		145	For small networks, it's best if every node uses the same set of seed
		146	nodes. For large networks, it can be useful to specify "regional" seed
		147	nodes for most nodes in an area, and use all seed nodes as seed nodes for
		148	each other. What's important is that all seed nodes connections form a
		149	complete graph, so that the network cannot split into separate subnets
		150	forever.
		151
		152	Seed nodes are represented by seed IDs.
		153
103	=item seeds - C<host:port>	154	=item seed IDs - C<host:port>
104		155
105	When a node starts, it knows nothing about the network. To teach the node	156	Seed IDs are transport endpoint(s) (usually a hostname/IP address and a
106	about the network it first has to contact some other node within the	157	TCP port) of nodes that should be used as seed nodes.
107	network. This node is called a seed.
108		158
109	Seeds are transport endpoint(s) of as many nodes as one wants. Those nodes	159	=item global nodes
110	are expected to be long-running, and at least one of those should always
111	be available. When nodes run out of connections (e.g. due to a network
112	error), they try to re-establish connections to some seednodes again to
113	join the network.
114		160
115	Apart from being sued for seeding, seednodes are not special in any way -	161	An AEMP network needs a discovery service - nodes need to know how to
116	every public node can be a seednode.	162	connect to other nodes they only know by name. In addition, AEMP offers a
		163	distributed "group database", which maps group names to a list of strings
		164	- for example, to register worker ports.
		165
		166	A network needs at least one global node to work, and allows every node to
		167	be a global node.
		168
		169	Any node that loads the L<AnyEvent::MP::Global> module becomes a global
		170	node and tries to keep connections to all other nodes. So while it can
		171	make sense to make every node "global" in small networks, it usually makes
		172	sense to only make seed nodes into global nodes in large networks (nodes
		173	keep connections to seed nodes and global nodes, so making them the same
		174	reduces overhead).
117		175
118	=back	176	=back
119		177
120	=head1 VARIABLES/FUNCTIONS	178	=head1 VARIABLES/FUNCTIONS
121		179
…		…
123		181
124	=cut	182	=cut
125		183
126	package AnyEvent::MP;	184	package AnyEvent::MP;
127		185
		186	use AnyEvent::MP::Config ();
128	use AnyEvent::MP::Kernel;	187	use AnyEvent::MP::Kernel;
		188	use AnyEvent::MP::Kernel qw(
		189	%NODE %PORT %PORT_DATA $UNIQ $RUNIQ $ID
		190	add_node load_func
		191
		192	NODE $NODE
		193	configure
		194	node_of port_is_local
		195	snd kil
		196	db_set db_del
		197	db_mon db_family db_keys db_values
		198	);
129		199
130	use common::sense;	200	use common::sense;
131		201
132	use Carp ();	202	use Carp ();
133		203
134	use AE ();	204	use AnyEvent ();
		205	use Guard ();
135		206
136	use base "Exporter";	207	use base "Exporter";
137		208
138	our $VERSION = $AnyEvent::MP::Kernel::VERSION;	209	our $VERSION = $AnyEvent::MP::Config::VERSION;
139		210
140	our @EXPORT = qw(	211	our @EXPORT = qw(
141	NODE $NODE *SELF node_of after	212	NODE $NODE
142	configure	213	configure
143	snd rcv mon mon_guard kil reg psub spawn	214	node_of port_is_local
144	port	215	snd kil
		216	db_set db_del
		217	db_mon db_family db_keys db_values
		218
		219	*SELF
		220
		221	port rcv mon mon_guard psub peval spawn cal
		222	db_set db_del db_reg
		223	db_mon db_family db_keys db_values
		224
		225	after
145	);	226	);
146		227
147	our $SELF;	228	our $SELF;
148		229
149	sub _self_die() {	230	sub _self_die() {
…		…
160		241
161	=item $nodeid = node_of $port	242	=item $nodeid = node_of $port
162		243
163	Extracts and returns the node ID from a port ID or a node ID.	244	Extracts and returns the node ID from a port ID or a node ID.
164		245
		246	=item $is_local = port_is_local $port
		247
		248	Returns true iff the port is a local port.
		249
		250	=item configure $profile, key => value...
		251
165	=item configure key => value...	252	=item configure key => value...
166		253
167	Before a node can talk to other nodes on the network (i.e. enter	254	Before a node can talk to other nodes on the network (i.e. enter
168	"distributed mode") it has to configure itself - the minimum a node needs	255	"distributed mode") it has to configure itself - the minimum a node needs
169	to know is its own name, and optionally it should know the addresses of	256	to know is its own name, and optionally it should know the addresses of
170	some other nodes in the network to discover other nodes.	257	some other nodes in the network to discover other nodes.
171		258
172	This function configures a node - it must be called exactly once (or	259	This function configures a node - it must be called exactly once (or
173	never) before calling other AnyEvent::MP functions.	260	never) before calling other AnyEvent::MP functions.
174		261
		262	The key/value pairs are basically the same ones as documented for the
		263	F<aemp> command line utility (sans the set/del prefix), with these additions:
		264
		265	=over 4
		266
		267	=item norc => $boolean (default false)
		268
		269	If true, then the rc file (e.g. F<~/.perl-anyevent-mp>) will I<not>
		270	be consulted - all configuration options must be specified in the
		271	C<configure> call.
		272
		273	=item force => $boolean (default false)
		274
		275	IF true, then the values specified in the C<configure> will take
		276	precedence over any values configured via the rc file. The default is for
		277	the rc file to override any options specified in the program.
		278
		279	=back
		280
175	=over 4	281	=over 4
176		282
177	=item step 1, gathering configuration from profiles	283	=item step 1, gathering configuration from profiles
178		284
179	The function first looks up a profile in the aemp configuration (see the	285	The function first looks up a profile in the aemp configuration (see the
180	L<aemp> commandline utility). The profile name can be specified via the	286	L<aemp> commandline utility). The profile name can be specified via the
181	named C<profile> parameter. If it is missing, then the nodename (F<uname	287	named C<profile> parameter or can simply be the first parameter). If it is
182	-n>) will be used as profile name.	288	missing, then the nodename (F<uname -n>) will be used as profile name.
183		289
184	The profile data is then gathered as follows:	290	The profile data is then gathered as follows:
185		291
186	First, all remaining key => value pairs (all of which are conviniently	292	First, all remaining key => value pairs (all of which are conveniently
187	undocumented at the moment) will be interpreted as configuration	293	undocumented at the moment) will be interpreted as configuration
188	data. Then they will be overwritten by any values specified in the global	294	data. Then they will be overwritten by any values specified in the global
189	default configuration (see the F<aemp> utility), then the chain of	295	default configuration (see the F<aemp> utility), then the chain of
190	profiles chosen by the profile name (and any C<parent> attributes).	296	profiles chosen by the profile name (and any C<parent> attributes).
191		297
192	That means that the values specified in the profile have highest priority	298	That means that the values specified in the profile have highest priority
193	and the values specified directly via C<configure> have lowest priority,	299	and the values specified directly via C<configure> have lowest priority,
194	and can only be used to specify defaults.	300	and can only be used to specify defaults.
195		301
196	If the profile specifies a node ID, then this will become the node ID of	302	If the profile specifies a node ID, then this will become the node ID of
197	this process. If not, then the profile name will be used as node ID. The	303	this process. If not, then the profile name will be used as node ID, with
198	special node ID of C<anon/> will be replaced by a random node ID.	304	a unique randoms tring (C</%u>) appended.
		305
		306	The node ID can contain some C<%> sequences that are expanded: C<%n>
		307	is expanded to the local nodename, C<%u> is replaced by a random
		308	strign to make the node unique. For example, the F<aemp> commandline
		309	utility uses C<aemp/%n/%u> as nodename, which might expand to
		310	C<aemp/cerebro/ZQDGSIkRhEZQDGSIkRhE>.
199		311
200	=item step 2, bind listener sockets	312	=item step 2, bind listener sockets
201		313
202	The next step is to look up the binds in the profile, followed by binding	314	The next step is to look up the binds in the profile, followed by binding
203	aemp protocol listeners on all binds specified (it is possible and valid	315	aemp protocol listeners on all binds specified (it is possible and valid
…		…
209	used, meaning the node will bind on a dynamically-assigned port on every	321	used, meaning the node will bind on a dynamically-assigned port on every
210	local IP address it finds.	322	local IP address it finds.
211		323
212	=item step 3, connect to seed nodes	324	=item step 3, connect to seed nodes
213		325
214	As the last step, the seeds list from the profile is passed to the	326	As the last step, the seed ID list from the profile is passed to the
215	L<AnyEvent::MP::Global> module, which will then use it to keep	327	L<AnyEvent::MP::Global> module, which will then use it to keep
216	connectivity with at least one node at any point in time.	328	connectivity with at least one node at any point in time.
217		329
218	=back	330	=back
219		331
220	Example: become a distributed node using the locla node name as profile.	332	Example: become a distributed node using the local node name as profile.
221	This should be the most common form of invocation for "daemon"-type nodes.	333	This should be the most common form of invocation for "daemon"-type nodes.
222		334
223	configure	335	configure
224		336
225	Example: become an anonymous node. This form is often used for commandline	337	Example: become a semi-anonymous node. This form is often used for
226	clients.	338	commandline clients.
227		339
228	configure nodeid => "anon/";	340	configure nodeid => "myscript/%n/%u";
229		341
230	Example: configure a node using a profile called seed, which si suitable	342	Example: configure a node using a profile called seed, which is suitable
231	for a seed node as it binds on all local addresses on a fixed port (4040,	343	for a seed node as it binds on all local addresses on a fixed port (4040,
232	customary for aemp).	344	customary for aemp).
233		345
234	# use the aemp commandline utility	346	# use the aemp commandline utility
235	# aemp profile seed nodeid anon/ binds '*:4040'	347	# aemp profile seed binds '*:4040'
236		348
237	# then use it	349	# then use it
238	configure profile => "seed";	350	configure profile => "seed";
239		351
240	# or simply use aemp from the shell again:	352	# or simply use aemp from the shell again:
…		…
305		417
306	=cut	418	=cut
307		419
308	sub rcv($@);	420	sub rcv($@);
309		421
310	sub _kilme {	422	my $KILME = sub {
311	die "received message on port without callback";	423	(my $tag = substr $_[0], 0, 30) =~ s/([\x20-\x7e])/./g;
312	}	424	kil $SELF, unhandled_message => "no callback found for message '$tag'";
		425	};
313		426
314	sub port(;&) {	427	sub port(;&) {
315	my $id = "$UNIQ." . $ID++;	428	my $id = $UNIQ . ++$ID;
316	my $port = "$NODE#$id";	429	my $port = "$NODE#$id";
317		430
318	rcv $port, shift \|\| \&_kilme;	431	rcv $port, shift \|\| $KILME;
319		432
320	$port	433	$port
321	}	434	}
322		435
323	=item rcv $local_port, $callback->(@msg)	436	=item rcv $local_port, $callback->(@msg)
…		…
328		441
329	The global C<$SELF> (exported by this module) contains C<$port> while	442	The global C<$SELF> (exported by this module) contains C<$port> while
330	executing the callback. Runtime errors during callback execution will	443	executing the callback. Runtime errors during callback execution will
331	result in the port being C<kil>ed.	444	result in the port being C<kil>ed.
332		445
333	The default callback received all messages not matched by a more specific	446	The default callback receives all messages not matched by a more specific
334	C<tag> match.	447	C<tag> match.
335		448
336	=item rcv $local_port, tag => $callback->(@msg_without_tag), ...	449	=item rcv $local_port, tag => $callback->(@msg_without_tag), ...
337		450
338	Register (or replace) callbacks to be called on messages starting with the	451	Register (or replace) callbacks to be called on messages starting with the
…		…
359	msg1 => sub { ... },	472	msg1 => sub { ... },
360	...	473	...
361	;	474	;
362		475
363	Example: temporarily register a rcv callback for a tag matching some port	476	Example: temporarily register a rcv callback for a tag matching some port
364	(e.g. for a rpc reply) and unregister it after a message was received.	477	(e.g. for an rpc reply) and unregister it after a message was received.
365		478
366	rcv $port, $otherport => sub {	479	rcv $port, $otherport => sub {
367	my @reply = @_;	480	my @reply = @_;
368		481
369	rcv $SELF, $otherport;	482	rcv $SELF, $otherport;
…		…
373		486
374	sub rcv($@) {	487	sub rcv($@) {
375	my $port = shift;	488	my $port = shift;
376	my ($nodeid, $portid) = split /#/, $port, 2;	489	my ($nodeid, $portid) = split /#/, $port, 2;
377		490
378	$NODE{$nodeid} == $NODE{""}	491	$nodeid eq $NODE
379	or Carp::croak "$port: rcv can only be called on local ports, caught";	492	or Carp::croak "$port: rcv can only be called on local ports, caught";
380		493
381	while (@_) {	494	while (@_) {
382	if (ref $_[0]) {	495	if (ref $_[0]) {
383	if (my $self = $PORT_DATA{$portid}) {	496	if (my $self = $PORT_DATA{$portid}) {
384	"AnyEvent::MP::Port" eq ref $self	497	"AnyEvent::MP::Port" eq ref $self
385	or Carp::croak "$port: rcv can only be called on message matching ports, caught";	498	or Carp::croak "$port: rcv can only be called on message matching ports, caught";
386		499
387	$self->[2] = shift;	500	$self->[0] = shift;
388	} else {	501	} else {
389	my $cb = shift;	502	my $cb = shift;
390	$PORT{$portid} = sub {	503	$PORT{$portid} = sub {
391	local $SELF = $port;	504	local $SELF = $port;
392	eval { &$cb }; _self_die if $@;	505	eval { &$cb }; _self_die if $@;
393	};	506	};
394	}	507	}
395	} elsif (defined $_[0]) {	508	} elsif (defined $_[0]) {
396	my $self = $PORT_DATA{$portid} \|\|= do {	509	my $self = $PORT_DATA{$portid} \|\|= do {
397	my $self = bless [$PORT{$port} \|\| sub { }, { }, $port], "AnyEvent::MP::Port";	510	my $self = bless [$PORT{$portid} \|\| sub { }, { }, $port], "AnyEvent::MP::Port";
398		511
399	$PORT{$portid} = sub {	512	$PORT{$portid} = sub {
400	local $SELF = $port;	513	local $SELF = $port;
401		514
402	if (my $cb = $self->[1]{$_[0]}) {	515	if (my $cb = $self->[1]{$_[0]}) {
…		…
424	}	537	}
425		538
426	$port	539	$port
427	}	540	}
428		541
		542	=item peval $port, $coderef[, @args]
		543
		544	Evaluates the given C<$codref> within the contetx of C<$port>, that is,
		545	when the code throws an exception the C<$port> will be killed.
		546
		547	Any remaining args will be passed to the callback. Any return values will
		548	be returned to the caller.
		549
		550	This is useful when you temporarily want to execute code in the context of
		551	a port.
		552
		553	Example: create a port and run some initialisation code in it's context.
		554
		555	my $port = port { ... };
		556
		557	peval $port, sub {
		558	init
		559	or die "unable to init";
		560	};
		561
		562	=cut
		563
		564	sub peval($$) {
		565	local $SELF = shift;
		566	my $cb = shift;
		567
		568	if (wantarray) {
		569	my @res = eval { &$cb };
		570	_self_die if $@;
		571	@res
		572	} else {
		573	my $res = eval { &$cb };
		574	_self_die if $@;
		575	$res
		576	}
		577	}
		578
429	=item $closure = psub { BLOCK }	579	=item $closure = psub { BLOCK }
430		580
431	Remembers C<$SELF> and creates a closure out of the BLOCK. When the	581	Remembers C<$SELF> and creates a closure out of the BLOCK. When the
432	closure is executed, sets up the environment in the same way as in C<rcv>	582	closure is executed, sets up the environment in the same way as in C<rcv>
433	callbacks, i.e. runtime errors will cause the port to get C<kil>ed.	583	callbacks, i.e. runtime errors will cause the port to get C<kil>ed.
		584
		585	The effect is basically as if it returned C<< sub { peval $SELF, sub {
		586	BLOCK }, @_ } >>.
434		587
435	This is useful when you register callbacks from C<rcv> callbacks:	588	This is useful when you register callbacks from C<rcv> callbacks:
436		589
437	rcv delayed_reply => sub {	590	rcv delayed_reply => sub {
438	my ($delay, @reply) = @_;	591	my ($delay, @reply) = @_;
…		…
462	$res	615	$res
463	}	616	}
464	}	617	}
465	}	618	}
466		619
		620	=item $guard = mon $port, $rcvport # kill $rcvport when $port dies
		621
		622	=item $guard = mon $port # kill $SELF when $port dies
		623
467	=item $guard = mon $port, $cb->(@reason) # call $cb when $port dies	624	=item $guard = mon $port, $cb->(@reason) # call $cb when $port dies
468
469	=item $guard = mon $port, $rcvport # kill $rcvport when $port dies
470
471	=item $guard = mon $port # kill $SELF when $port dies
472		625
473	=item $guard = mon $port, $rcvport, @msg # send a message when $port dies	626	=item $guard = mon $port, $rcvport, @msg # send a message when $port dies
474		627
475	Monitor the given port and do something when the port is killed or	628	Monitor the given port and do something when the port is killed or
476	messages to it were lost, and optionally return a guard that can be used	629	messages to it were lost, and optionally return a guard that can be used
477	to stop monitoring again.	630	to stop monitoring again.
		631
		632	The first two forms distinguish between "normal" and "abnormal" kil's:
		633
		634	In the first form (another port given), if the C<$port> is C<kil>'ed with
		635	a non-empty reason, the other port (C<$rcvport>) will be kil'ed with the
		636	same reason. That is, on "normal" kil's nothing happens, while under all
		637	other conditions, the other port is killed with the same reason.
		638
		639	The second form (kill self) is the same as the first form, except that
		640	C<$rvport> defaults to C<$SELF>.
		641
		642	The remaining forms don't distinguish between "normal" and "abnormal" kil's
		643	- it's up to the callback or receiver to check whether the C<@reason> is
		644	empty and act accordingly.
		645
		646	In the third form (callback), the callback is simply called with any
		647	number of C<@reason> elements (empty @reason means that the port was deleted
		648	"normally"). Note also that I<< the callback B<must> never die >>, so use
		649	C<eval> if unsure.
		650
		651	In the last form (message), a message of the form C<$rcvport, @msg,
		652	@reason> will be C<snd>.
		653
		654	Monitoring-actions are one-shot: once messages are lost (and a monitoring
		655	alert was raised), they are removed and will not trigger again, even if it
		656	turns out that the port is still alive.
		657
		658	As a rule of thumb, monitoring requests should always monitor a remote
		659	port locally (using a local C<$rcvport> or a callback). The reason is that
		660	kill messages might get lost, just like any other message. Another less
		661	obvious reason is that even monitoring requests can get lost (for example,
		662	when the connection to the other node goes down permanently). When
		663	monitoring a port locally these problems do not exist.
478		664
479	C<mon> effectively guarantees that, in the absence of hardware failures,	665	C<mon> effectively guarantees that, in the absence of hardware failures,
480	after starting the monitor, either all messages sent to the port will	666	after starting the monitor, either all messages sent to the port will
481	arrive, or the monitoring action will be invoked after possible message	667	arrive, or the monitoring action will be invoked after possible message
482	loss has been detected. No messages will be lost "in between" (after	668	loss has been detected. No messages will be lost "in between" (after
483	the first lost message no further messages will be received by the	669	the first lost message no further messages will be received by the
484	port). After the monitoring action was invoked, further messages might get	670	port). After the monitoring action was invoked, further messages might get
485	delivered again.	671	delivered again.
486		672
487	Note that monitoring-actions are one-shot: once messages are lost (and a	673	Inter-host-connection timeouts and monitoring depend on the transport
488	monitoring alert was raised), they are removed and will not trigger again.	674	used. The only transport currently implemented is TCP, and AnyEvent::MP
		675	relies on TCP to detect node-downs (this can take 10-15 minutes on a
		676	non-idle connection, and usually around two hours for idle connections).
489		677
490	In the first form (callback), the callback is simply called with any	678	This means that monitoring is good for program errors and cleaning up
491	number of C<@reason> elements (no @reason means that the port was deleted	679	stuff eventually, but they are no replacement for a timeout when you need
492	"normally"). Note also that I<< the callback B<must> never die >>, so use	680	to ensure some maximum latency.
493	C<eval> if unsure.
494
495	In the second form (another port given), the other port (C<$rcvport>)
496	will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on
497	"normal" kils nothing happens, while under all other conditions, the other
498	port is killed with the same reason.
499
500	The third form (kill self) is the same as the second form, except that
501	C<$rvport> defaults to C<$SELF>.
502
503	In the last form (message), a message of the form C<@msg, @reason> will be
504	C<snd>.
505
506	As a rule of thumb, monitoring requests should always monitor a port from
507	a local port (or callback). The reason is that kill messages might get
508	lost, just like any other message. Another less obvious reason is that
509	even monitoring requests can get lost (for exmaple, when the connection
510	to the other node goes down permanently). When monitoring a port locally
511	these problems do not exist.
512		681
513	Example: call a given callback when C<$port> is killed.	682	Example: call a given callback when C<$port> is killed.
514		683
515	mon $port, sub { warn "port died because of <@_>\n" };	684	mon $port, sub { warn "port died because of <@_>\n" };
516		685
…		…
544	}	713	}
545		714
546	$node->monitor ($port, $cb);	715	$node->monitor ($port, $cb);
547		716
548	defined wantarray	717	defined wantarray
549	and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }	718	and ($cb += 0, Guard::guard { $node->unmonitor ($port, $cb) })
550	}	719	}
551		720
552	=item $guard = mon_guard $port, $ref, $ref...	721	=item $guard = mon_guard $port, $ref, $ref...
553		722
554	Monitors the given C<$port> and keeps the passed references. When the port	723	Monitors the given C<$port> and keeps the passed references. When the port
…		…
577		746
578	=item kil $port[, @reason]	747	=item kil $port[, @reason]
579		748
580	Kill the specified port with the given C<@reason>.	749	Kill the specified port with the given C<@reason>.
581		750
582	If no C<@reason> is specified, then the port is killed "normally" (ports	751	If no C<@reason> is specified, then the port is killed "normally" -
583	monitoring other ports will not necessarily die because a port dies	752	monitor callback will be invoked, but the kil will not cause linked ports
584	"normally").	753	(C<mon $mport, $lport> form) to get killed.
585		754
586	Otherwise, linked ports get killed with the same reason (second form of	755	If a C<@reason> is specified, then linked ports (C<mon $mport, $lport>
587	C<mon>, see above).	756	form) get killed with the same reason.
588		757
589	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks	758	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
590	will be reported as reason C<< die => $@ >>.	759	will be reported as reason C<< die => $@ >>.
591		760
592	Transport/communication errors are reported as C<< transport_error =>	761	Transport/communication errors are reported as C<< transport_error =>
593	$message >>.	762	$message >>.
594		763
595	=cut	764	Common idioms:
		765
		766	# silently remove yourself, do not kill linked ports
		767	kil $SELF;
		768
		769	# report a failure in some detail
		770	kil $SELF, failure_mode_1 => "it failed with too high temperature";
		771
		772	# do not waste much time with killing, just die when something goes wrong
		773	open my $fh, "<file"
		774	or die "file: $!";
596		775
597	=item $port = spawn $node, $initfunc[, @initdata]	776	=item $port = spawn $node, $initfunc[, @initdata]
598		777
599	Creates a port on the node C<$node> (which can also be a port ID, in which	778	Creates a port on the node C<$node> (which can also be a port ID, in which
600	case it's the node where that port resides).	779	case it's the node where that port resides).
…		…
611	the package, then the package above the package and so on (e.g.	790	the package, then the package above the package and so on (e.g.
612	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function	791	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
613	exists or it runs out of package names.	792	exists or it runs out of package names.
614		793
615	The init function is then called with the newly-created port as context	794	The init function is then called with the newly-created port as context
616	object (C<$SELF>) and the C<@initdata> values as arguments.	795	object (C<$SELF>) and the C<@initdata> values as arguments. It I<must>
		796	call one of the C<rcv> functions to set callbacks on C<$SELF>, otherwise
		797	the port might not get created.
617		798
618	A common idiom is to pass a local port, immediately monitor the spawned	799	A common idiom is to pass a local port, immediately monitor the spawned
619	port, and in the remote init function, immediately monitor the passed	800	port, and in the remote init function, immediately monitor the passed
620	local port. This two-way monitoring ensures that both ports get cleaned up	801	local port. This two-way monitoring ensures that both ports get cleaned up
621	when there is a problem.	802	when there is a problem.
622		803
		804	C<spawn> guarantees that the C<$initfunc> has no visible effects on the
		805	caller before C<spawn> returns (by delaying invocation when spawn is
		806	called for the local node).
		807
623	Example: spawn a chat server port on C<$othernode>.	808	Example: spawn a chat server port on C<$othernode>.
624		809
625	# this node, executed from within a port context:	810	# this node, executed from within a port context:
626	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;	811	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;
627	mon $server;	812	mon $server;
…		…
641		826
642	sub _spawn {	827	sub _spawn {
643	my $port = shift;	828	my $port = shift;
644	my $init = shift;	829	my $init = shift;
645		830
		831	# rcv will create the actual port
646	local $SELF = "$NODE#$port";	832	local $SELF = "$NODE#$port";
647	eval {	833	eval {
648	&{ load_func $init }	834	&{ load_func $init }
649	};	835	};
650	_self_die if $@;	836	_self_die if $@;
651	}	837	}
652		838
653	sub spawn(@) {	839	sub spawn(@) {
654	my ($nodeid, undef) = split /#/, shift, 2;	840	my ($nodeid, undef) = split /#/, shift, 2;
655		841
656	my $id = "$RUNIQ." . $ID++;	842	my $id = $RUNIQ . ++$ID;
657		843
658	$_[0] =~ /::/	844	$_[0] =~ /::/
659	or Carp::croak "spawn init function must be a fully-qualified name, caught";	845	or Carp::croak "spawn init function must be a fully-qualified name, caught";
660		846
661	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;	847	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;
662		848
663	"$nodeid#$id"	849	"$nodeid#$id"
664	}	850	}
		851
665		852
666	=item after $timeout, @msg	853	=item after $timeout, @msg
667		854
668	=item after $timeout, $callback	855	=item after $timeout, $callback
669		856
…		…
685	? $action[0]()	872	? $action[0]()
686	: snd @action;	873	: snd @action;
687	};	874	};
688	}	875	}
689		876
		877	#=item $cb2 = timeout $seconds, $cb[, @args]
		878
		879	=item cal $port, @msg, $callback[, $timeout]
		880
		881	A simple form of RPC - sends a message to the given C<$port> with the
		882	given contents (C<@msg>), but adds a reply port to the message.
		883
		884	The reply port is created temporarily just for the purpose of receiving
		885	the reply, and will be C<kil>ed when no longer needed.
		886
		887	A reply message sent to the port is passed to the C<$callback> as-is.
		888
		889	If an optional time-out (in seconds) is given and it is not C<undef>,
		890	then the callback will be called without any arguments after the time-out
		891	elapsed and the port is C<kil>ed.
		892
		893	If no time-out is given (or it is C<undef>), then the local port will
		894	monitor the remote port instead, so it eventually gets cleaned-up.
		895
		896	Currently this function returns the temporary port, but this "feature"
		897	might go in future versions unless you can make a convincing case that
		898	this is indeed useful for something.
		899
		900	=cut
		901
		902	sub cal(@) {
		903	my $timeout = ref $_[-1] ? undef : pop;
		904	my $cb = pop;
		905
		906	my $port = port {
		907	undef $timeout;
		908	kil $SELF;
		909	&$cb;
		910	};
		911
		912	if (defined $timeout) {
		913	$timeout = AE::timer $timeout, 0, sub {
		914	undef $timeout;
		915	kil $port;
		916	$cb->();
		917	};
		918	} else {
		919	mon $_[0], sub {
		920	kil $port;
		921	$cb->();
		922	};
		923	}
		924
		925	push @_, $port;
		926	&snd;
		927
		928	$port
		929	}
		930
		931	=back
		932
		933	=head1 DISTRIBUTED DATABASE
		934
		935	AnyEvent::MP comes with a simple distributed database. The database will
		936	be mirrored asynchronously on all global nodes. Other nodes bind to one
		937	of the global nodes for their needs. Every node has a "local database"
		938	which contains all the values that are set locally. All local databases
		939	are merged together to form the global database, which can be queried.
		940
		941	The database structure is that of a two-level hash - the database hash
		942	contains hashes which contain values, similarly to a perl hash of hashes,
		943	i.e.:
		944
		945	$DATABASE{$family}{$subkey} = $value
		946
		947	The top level hash key is called "family", and the second-level hash key
		948	is called "subkey" or simply "key".
		949
		950	The family must be alphanumeric, i.e. start with a letter and consist
		951	of letters, digits, underscores and colons (C<[A-Za-z][A-Za-z0-9_:]*>,
		952	pretty much like Perl module names.
		953
		954	As the family namespace is global, it is recommended to prefix family names
		955	with the name of the application or module using it.
		956
		957	The subkeys must be non-empty strings, with no further restrictions.
		958
		959	The values should preferably be strings, but other perl scalars should
		960	work as well (such as C<undef>, arrays and hashes).
		961
		962	Every database entry is owned by one node - adding the same family/subkey
		963	combination on multiple nodes will not cause discomfort for AnyEvent::MP,
		964	but the result might be nondeterministic, i.e. the key might have
		965	different values on different nodes.
		966
		967	Different subkeys in the same family can be owned by different nodes
		968	without problems, and in fact, this is the common method to create worker
		969	pools. For example, a worker port for image scaling might do this:
		970
		971	db_set my_image_scalers => $port;
		972
		973	And clients looking for an image scaler will want to get the
		974	C<my_image_scalers> keys from time to time:
		975
		976	db_keys my_image_scalers => sub {
		977	@ports = @{ $_[0] };
		978	};
		979
		980	Or better yet, they want to monitor the database family, so they always
		981	have a reasonable up-to-date copy:
		982
		983	db_mon my_image_scalers => sub {
		984	@ports = keys %{ $_[0] };
		985	};
		986
		987	In general, you can set or delete single subkeys, but query and monitor
		988	whole families only.
		989
		990	If you feel the need to monitor or query a single subkey, try giving it
		991	it's own family.
		992
		993	=over
		994
		995	=item $guard = db_set $family => $subkey [=> $value]
		996
		997	Sets (or replaces) a key to the database - if C<$value> is omitted,
		998	C<undef> is used instead.
		999
		1000	When called in non-void context, C<db_set> returns a guard that
		1001	automatically calls C<db_del> when it is destroyed.
		1002
		1003	=item db_del $family => $subkey...
		1004
		1005	Deletes one or more subkeys from the database family.
		1006
		1007	=item $guard = db_reg $family => $port => $value
		1008
		1009	=item $guard = db_reg $family => $port
		1010
		1011	=item $guard = db_reg $family
		1012
		1013	Registers a port in the given family and optionally returns a guard to
		1014	remove it.
		1015
		1016	This function basically does the same as:
		1017
		1018	db_set $family => $port => $value
		1019
		1020	Except that the port is monitored and automatically removed from the
		1021	database family when it is kil'ed.
		1022
		1023	If C<$value> is missing, C<undef> is used. If C<$port> is missing, then
		1024	C<$SELF> is used.
		1025
		1026	This function is most useful to register a port in some port group (which
		1027	is just another name for a database family), and have it removed when the
		1028	port is gone. This works best when the port is a local port.
		1029
		1030	=cut
		1031
		1032	sub db_reg($$;$) {
		1033	my $family = shift;
		1034	my $port = @_ ? shift : $SELF;
		1035
		1036	my $clr = sub { db_del $family => $port };
		1037	mon $port, $clr;
		1038
		1039	db_set $family => $port => $_[0];
		1040
		1041	defined wantarray
		1042	and &Guard::guard ($clr)
		1043	}
		1044
		1045	=item db_family $family => $cb->(\%familyhash)
		1046
		1047	Queries the named database C<$family> and call the callback with the
		1048	family represented as a hash. You can keep and freely modify the hash.
		1049
		1050	=item db_keys $family => $cb->(\@keys)
		1051
		1052	Same as C<db_family>, except it only queries the family I<subkeys> and passes
		1053	them as array reference to the callback.
		1054
		1055	=item db_values $family => $cb->(\@values)
		1056
		1057	Same as C<db_family>, except it only queries the family I<values> and passes them
		1058	as array reference to the callback.
		1059
		1060	=item $guard = db_mon $family => $cb->(\%familyhash, \@added, \@changed, \@deleted)
		1061
		1062	Creates a monitor on the given database family. Each time a key is
		1063	set or is deleted the callback is called with a hash containing the
		1064	database family and three lists of added, changed and deleted subkeys,
		1065	respectively. If no keys have changed then the array reference might be
		1066	C<undef> or even missing.
		1067
		1068	If not called in void context, a guard object is returned that, when
		1069	destroyed, stops the monitor.
		1070
		1071	The family hash reference and the key arrays belong to AnyEvent::MP and
		1072	B<must not be modified or stored> by the callback. When in doubt, make a
		1073	copy.
		1074
		1075	As soon as possible after the monitoring starts, the callback will be
		1076	called with the intiial contents of the family, even if it is empty,
		1077	i.e. there will always be a timely call to the callback with the current
		1078	contents.
		1079
		1080	It is possible that the callback is called with a change event even though
		1081	the subkey is already present and the value has not changed.
		1082
		1083	The monitoring stops when the guard object is destroyed.
		1084
		1085	Example: on every change to the family "mygroup", print out all keys.
		1086
		1087	my $guard = db_mon mygroup => sub {
		1088	my ($family, $a, $c, $d) = @_;
		1089	print "mygroup members: ", (join " ", keys %$family), "\n";
		1090	};
		1091
		1092	Exmaple: wait until the family "My::Module::workers" is non-empty.
		1093
		1094	my $guard; $guard = db_mon My::Module::workers => sub {
		1095	my ($family, $a, $c, $d) = @_;
		1096	return unless %$family;
		1097	undef $guard;
		1098	print "My::Module::workers now nonempty\n";
		1099	};
		1100
		1101	Example: print all changes to the family "AnyEvent::Fantasy::Module".
		1102
		1103	my $guard = db_mon AnyEvent::Fantasy::Module => sub {
		1104	my ($family, $a, $c, $d) = @_;
		1105
		1106	print "+$_=$family->{$_}\n" for @$a;
		1107	print "*$_=$family->{$_}\n" for @$c;
		1108	print "-$_=$family->{$_}\n" for @$d;
		1109	};
		1110
		1111	=cut
		1112
690	=back	1113	=back
691		1114
692	=head1 AnyEvent::MP vs. Distributed Erlang	1115	=head1 AnyEvent::MP vs. Distributed Erlang
693		1116
694	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node	1117	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
695	== aemp node, Erlang process == aemp port), so many of the documents and	1118	== aemp node, Erlang process == aemp port), so many of the documents and
696	programming techniques employed by Erlang apply to AnyEvent::MP. Here is a	1119	programming techniques employed by Erlang apply to AnyEvent::MP. Here is a
697	sample:	1120	sample:
698		1121
699	http://www.Erlang.se/doc/programming_rules.shtml	1122	http://www.erlang.se/doc/programming_rules.shtml
700	http://Erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4	1123	http://erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4
701	http://Erlang.org/download/Erlang-book-part1.pdf # chapters 5 and 6	1124	http://erlang.org/download/erlang-book-part1.pdf # chapters 5 and 6
702	http://Erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5	1125	http://erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5
703		1126
704	Despite the similarities, there are also some important differences:	1127	Despite the similarities, there are also some important differences:
705		1128
706	=over 4	1129	=over 4
707		1130
708	=item * Node IDs are arbitrary strings in AEMP.	1131	=item * Node IDs are arbitrary strings in AEMP.
709		1132
710	Erlang relies on special naming and DNS to work everywhere in the same	1133	Erlang relies on special naming and DNS to work everywhere in the same
711	way. AEMP relies on each node somehow knowing its own address(es) (e.g. by	1134	way. AEMP relies on each node somehow knowing its own address(es) (e.g. by
712	configuraiton or DNS), but will otherwise discover other odes itself.	1135	configuration or DNS), and possibly the addresses of some seed nodes, but
		1136	will otherwise discover other nodes (and their IDs) itself.
713		1137
714	=item * Erlang has a "remote ports are like local ports" philosophy, AEMP	1138	=item * Erlang has a "remote ports are like local ports" philosophy, AEMP
715	uses "local ports are like remote ports".	1139	uses "local ports are like remote ports".
716		1140
717	The failure modes for local ports are quite different (runtime errors	1141	The failure modes for local ports are quite different (runtime errors
…		…
726	ports being the special case/exception, where transport errors cannot	1150	ports being the special case/exception, where transport errors cannot
727	occur.	1151	occur.
728		1152
729	=item * Erlang uses processes and a mailbox, AEMP does not queue.	1153	=item * Erlang uses processes and a mailbox, AEMP does not queue.
730		1154
731	Erlang uses processes that selectively receive messages, and therefore	1155	Erlang uses processes that selectively receive messages out of order, and
732	needs a queue. AEMP is event based, queuing messages would serve no	1156	therefore needs a queue. AEMP is event based, queuing messages would serve
733	useful purpose. For the same reason the pattern-matching abilities of	1157	no useful purpose. For the same reason the pattern-matching abilities
734	AnyEvent::MP are more limited, as there is little need to be able to	1158	of AnyEvent::MP are more limited, as there is little need to be able to
735	filter messages without dequeing them.	1159	filter messages without dequeuing them.
736		1160
737	(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).	1161	This is not a philosophical difference, but simply stems from AnyEvent::MP
		1162	being event-based, while Erlang is process-based.
		1163
		1164	You can have a look at L<Coro::MP> for a more Erlang-like process model on
		1165	top of AEMP and Coro threads.
738		1166
739	=item * Erlang sends are synchronous, AEMP sends are asynchronous.	1167	=item * Erlang sends are synchronous, AEMP sends are asynchronous.
740		1168
741	Sending messages in Erlang is synchronous and blocks the process (and	1169	Sending messages in Erlang is synchronous and blocks the process until
		1170	a connection has been established and the message sent (and so does not
742	so does not need a queue that can overflow). AEMP sends are immediate,	1171	need a queue that can overflow). AEMP sends return immediately, connection
743	connection establishment is handled in the background.	1172	establishment is handled in the background.
744		1173
745	=item * Erlang suffers from silent message loss, AEMP does not.	1174	=item * Erlang suffers from silent message loss, AEMP does not.
746		1175
747	Erlang makes few guarantees on messages delivery - messages can get lost	1176	Erlang implements few guarantees on messages delivery - messages can get
748	without any of the processes realising it (i.e. you send messages a, b,	1177	lost without any of the processes realising it (i.e. you send messages a,
749	and c, and the other side only receives messages a and c).	1178	b, and c, and the other side only receives messages a and c).
750		1179
751	AEMP guarantees correct ordering, and the guarantee that after one message	1180	AEMP guarantees (modulo hardware errors) correct ordering, and the
752	is lost, all following ones sent to the same port are lost as well, until	1181	guarantee that after one message is lost, all following ones sent to the
753	monitoring raises an error, so there are no silent "holes" in the message	1182	same port are lost as well, until monitoring raises an error, so there are
754	sequence.	1183	no silent "holes" in the message sequence.
		1184
		1185	If you want your software to be very reliable, you have to cope with
		1186	corrupted and even out-of-order messages in both Erlang and AEMP. AEMP
		1187	simply tries to work better in common error cases, such as when a network
		1188	link goes down.
755		1189
756	=item * Erlang can send messages to the wrong port, AEMP does not.	1190	=item * Erlang can send messages to the wrong port, AEMP does not.
757		1191
758	In Erlang it is quite likely that a node that restarts reuses a process ID	1192	In Erlang it is quite likely that a node that restarts reuses an Erlang
759	known to other nodes for a completely different process, causing messages	1193	process ID known to other nodes for a completely different process,
760	destined for that process to end up in an unrelated process.	1194	causing messages destined for that process to end up in an unrelated
		1195	process.
761		1196
762	AEMP never reuses port IDs, so old messages or old port IDs floating	1197	AEMP does not reuse port IDs, so old messages or old port IDs floating
763	around in the network will not be sent to an unrelated port.	1198	around in the network will not be sent to an unrelated port.
764		1199
765	=item * Erlang uses unprotected connections, AEMP uses secure	1200	=item * Erlang uses unprotected connections, AEMP uses secure
766	authentication and can use TLS.	1201	authentication and can use TLS.
767		1202
…		…
770		1205
771	=item * The AEMP protocol is optimised for both text-based and binary	1206	=item * The AEMP protocol is optimised for both text-based and binary
772	communications.	1207	communications.
773		1208
774	The AEMP protocol, unlike the Erlang protocol, supports both programming	1209	The AEMP protocol, unlike the Erlang protocol, supports both programming
775	language independent text-only protocols (good for debugging) and binary,	1210	language independent text-only protocols (good for debugging), and binary,
776	language-specific serialisers (e.g. Storable). By default, unless TLS is	1211	language-specific serialisers (e.g. Storable). By default, unless TLS is
777	used, the protocol is actually completely text-based.	1212	used, the protocol is actually completely text-based.
778		1213
779	It has also been carefully designed to be implementable in other languages	1214	It has also been carefully designed to be implementable in other languages
780	with a minimum of work while gracefully degrading functionality to make the	1215	with a minimum of work while gracefully degrading functionality to make the
781	protocol simple.	1216	protocol simple.
782		1217
783	=item * AEMP has more flexible monitoring options than Erlang.	1218	=item * AEMP has more flexible monitoring options than Erlang.
784		1219
785	In Erlang, you can chose to receive I<all> exit signals as messages	1220	In Erlang, you can chose to receive I<all> exit signals as messages or
786	or I<none>, there is no in-between, so monitoring single processes is	1221	I<none>, there is no in-between, so monitoring single Erlang processes is
787	difficult to implement. Monitoring in AEMP is more flexible than in	1222	difficult to implement.
788	Erlang, as one can choose between automatic kill, exit message or callback	1223
789	on a per-process basis.	1224	Monitoring in AEMP is more flexible than in Erlang, as one can choose
		1225	between automatic kill, exit message or callback on a per-port basis.
790		1226
791	=item * Erlang tries to hide remote/local connections, AEMP does not.	1227	=item * Erlang tries to hide remote/local connections, AEMP does not.
792		1228
793	Monitoring in Erlang is not an indicator of process death/crashes, in the	1229	Monitoring in Erlang is not an indicator of process death/crashes, in the
794	same way as linking is (except linking is unreliable in Erlang).	1230	same way as linking is (except linking is unreliable in Erlang).
…		…
816	overhead, as well as having to keep a proxy object everywhere.	1252	overhead, as well as having to keep a proxy object everywhere.
817		1253
818	Strings can easily be printed, easily serialised etc. and need no special	1254	Strings can easily be printed, easily serialised etc. and need no special
819	procedures to be "valid".	1255	procedures to be "valid".
820		1256
821	And as a result, a miniport consists of a single closure stored in a	1257	And as a result, a port with just a default receiver consists of a single
822	global hash - it can't become much cheaper.	1258	code reference stored in a global hash - it can't become much cheaper.
823		1259
824	=item Why favour JSON, why not a real serialising format such as Storable?	1260	=item Why favour JSON, why not a real serialising format such as Storable?
825		1261
826	In fact, any AnyEvent::MP node will happily accept Storable as framing	1262	In fact, any AnyEvent::MP node will happily accept Storable as framing
827	format, but currently there is no way to make a node use Storable by	1263	format, but currently there is no way to make a node use Storable by
…		…
837	Keeping your messages simple, concentrating on data structures rather than	1273	Keeping your messages simple, concentrating on data structures rather than
838	objects, will keep your messages clean, tidy and efficient.	1274	objects, will keep your messages clean, tidy and efficient.
839		1275
840	=back	1276	=back
841		1277
		1278	=head1 PORTING FROM AnyEvent::MP VERSION 1.X
		1279
		1280	AEMP version 2 has a few major incompatible changes compared to version 1:
		1281
		1282	=over 4
		1283
		1284	=item AnyEvent::MP::Global no longer has group management functions.
		1285
		1286	At least not officially - the grp_* functions are still exported and might
		1287	work, but they will be removed in some later release.
		1288
		1289	AnyEvent::MP now comes with a distributed database that is more
		1290	powerful. Its database families map closely to port groups, but the API
		1291	has changed (the functions are also now exported by AnyEvent::MP). Here is
		1292	a rough porting guide:
		1293
		1294	grp_reg $group, $port # old
		1295	db_reg $group, $port # new
		1296
		1297	$list = grp_get $group # old
		1298	db_keys $group, sub { my $list = shift } # new
		1299
		1300	grp_mon $group, $cb->(\@ports, $add, $del) # old
		1301	db_mon $group, $cb->(\%ports, $add, $change, $del) # new
		1302
		1303	C<grp_reg> is a no-brainer (just replace by C<db_reg>), but C<grp_get> is
		1304	no longer instant, because the local node might not have a copy of the
		1305	group. You can either modify your code to allow for a callback, or use
		1306	C<db_mon> to keep an updated copy of the group:
		1307
		1308	my $local_group_copy;
		1309	db_mon $group => sub { $local_group_copy = $_[0] };
		1310
		1311	# now "keys %$local_group_copy" always returns the most up-to-date
		1312	# list of ports in the group.
		1313
		1314	C<grp_mon> can be replaced by C<db_mon> with minor changes - C<db_mon>
		1315	passes a hash as first argument, and an extra C<$chg> argument that can be
		1316	ignored:
		1317
		1318	db_mon $group => sub {
		1319	my ($ports, $add, $chg, $lde) = @_;
		1320	$ports = [keys %$ports];
		1321
		1322	# now $ports, $add and $del are the same as
		1323	# were originally passed by grp_mon.
		1324	...
		1325	};
		1326
		1327	=item Nodes not longer connect to all other nodes.
		1328
		1329	In AEMP 1.x, every node automatically loads the L<AnyEvent::MP::Global>
		1330	module, which in turn would create connections to all other nodes in the
		1331	network (helped by the seed nodes).
		1332
		1333	In version 2.x, global nodes still connect to all other global nodes, but
		1334	other nodes don't - now every node either is a global node itself, or
		1335	attaches itself to another global node.
		1336
		1337	If a node isn't a global node itself, then it attaches itself to one
		1338	of its seed nodes. If that seed node isn't a global node yet, it will
		1339	automatically be upgraded to a global node.
		1340
		1341	So in many cases, nothing needs to be changed - one just has to make sure
		1342	that all seed nodes are meshed together with the other seed nodes (as with
		1343	AEMP 1.x), and other nodes specify them as seed nodes. This is most easily
		1344	achieved by specifying the same set of seed nodes for all nodes in the
		1345	network.
		1346
		1347	Not opening a connection to every other node is usually an advantage,
		1348	except when you need the lower latency of an already established
		1349	connection. To ensure a node establishes a connection to another node,
		1350	you can monitor the node port (C<mon $node, ...>), which will attempt to
		1351	create the connection (and notify you when the connection fails).
		1352
		1353	=item Listener-less nodes (nodes without binds) are gone.
		1354
		1355	And are not coming back, at least not in their old form. If no C<binds>
		1356	are specified for a node, AnyEvent::MP assumes a default of C<:>.
		1357
		1358	There are vague plans to implement some form of routing domains, which
		1359	might or might not bring back listener-less nodes, but don't count on it.
		1360
		1361	The fact that most connections are now optional somewhat mitigates this,
		1362	as a node can be effectively unreachable from the outside without any
		1363	problems, as long as it isn't a global node and only reaches out to other
		1364	nodes (as opposed to being contacted from other nodes).
		1365
		1366	=item $AnyEvent::MP::Kernel::WARN has gone.
		1367
		1368	AnyEvent has acquired a logging framework (L<AnyEvent::Log>), and AEMP now
		1369	uses this, and so should your programs.
		1370
		1371	Every module now documents what kinds of messages it generates, with
		1372	AnyEvent::MP acting as a catch all.
		1373
		1374	On the positive side, this means that instead of setting
		1375	C<PERL_ANYEVENT_MP_WARNLEVEL>, you can get away by setting C<AE_VERBOSE> -
		1376	much less to type.
		1377
		1378	=back
		1379
		1380	=head1 LOGGING
		1381
		1382	AnyEvent::MP does not normally log anything by itself, but since it is the
		1383	root of the contetx hierarchy for AnyEvent::MP modules, it will receive
		1384	all log messages by submodules.
		1385
842	=head1 SEE ALSO	1386	=head1 SEE ALSO
843		1387
844	L<AnyEvent::MP::Intro> - a gentle introduction.	1388	L<AnyEvent::MP::Intro> - a gentle introduction.
845		1389
846	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.	1390	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.
847		1391
848	L<AnyEvent::MP::Global> - network maintainance and port groups, to find	1392	L<AnyEvent::MP::Global> - network maintenance and port groups, to find
849	your applications.	1393	your applications.
		1394
		1395	L<AnyEvent::MP::DataConn> - establish data connections between nodes.
		1396
		1397	L<AnyEvent::MP::LogCatcher> - simple service to display log messages from
		1398	all nodes.
850		1399
851	L<AnyEvent>.	1400	L<AnyEvent>.
852		1401
853	=head1 AUTHOR	1402	=head1 AUTHOR
854		1403

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.75 by root, Mon Aug 31 13:18:06 2009 UTC vs. Revision 1.147 by root, Mon Jun 20 16:58:15 2016 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.75 by root, Mon Aug 31 13:18:06 2009 UTC vs.
Revision 1.147 by root, Mon Jun 20 16:58:15 2016 UTC