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

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

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.87 by root, Fri Sep 11 02:32:23 2009 UTC vs. Revision 1.153 by root, Sat Nov 2 01:30:49 2019 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.87 by root, Fri Sep 11 02:32:23 2009 UTC vs.
Revision 1.153 by root, Sat Nov 2 01:30:49 2019 UTC