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

Comparing cvsroot/AnyEvent-MP/MP.pm (file contents):
Revision 1.136 by root, Wed Mar 21 15:22:16 2012 UTC vs.
Revision 1.153 by root, Sat Nov 2 01:30:49 2019 UTC

…		…
47	# execute callbacks in $SELF port context	47	# execute callbacks in $SELF port context
48	my $timer = AE::timer 1, 0, psub {	48	my $timer = AE::timer 1, 0, psub {
49	die "kill the port, delayed";	49	die "kill the port, delayed";
50	};	50	};
51		51
52	=head1 CURRENT STATUS	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
53		56
54	bin/aemp - stable.	57	# distributed database - queries
55	AnyEvent::MP - stable API, should work.	58	db_family $family => $cb->(\%familyhash)
56	AnyEvent::MP::Intro - explains most concepts.	59	db_keys $family => $cb->(\@keys)
57	AnyEvent::MP::Kernel - mostly stable API.	60	db_values $family => $cb->(\@values)
58	AnyEvent::MP::Global - stable API.	61
		62	# distributed database - monitoring a family
		63	db_mon $family => $cb->(\%familyhash, \@added, \@changed, \@deleted)
59		64
60	=head1 DESCRIPTION	65	=head1 DESCRIPTION
61		66
62	This module (-family) implements a simple message passing framework.	67	This module (-family) implements a simple message passing framework.
63		68
…		…
113	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
114	endpoints - binds.	119	endpoints - binds.
115		120
116	Currently, only standard C<ip:port> specifications can be used, which	121	Currently, only standard C<ip:port> specifications can be used, which
117	specify TCP ports to listen on. So a bind is basically just a tcp socket	122	specify TCP ports to listen on. So a bind is basically just a tcp socket
118	in listening mode thta accepts conenctions form other nodes.	123	in listening mode that accepts connections from other nodes.
119		124
120	=item seed nodes	125	=item seed nodes
121		126
122	When a node starts, it knows nothing about the network it is in - it	127	When a node starts, it knows nothing about the network it is in - it
123	needs to connect to at least one other node that is already in the	128	needs to connect to at least one other node that is already in the
124	network. These other nodes are called "seed nodes".	129	network. These other nodes are called "seed nodes".
125		130
126	Seed nodes themselves are not special - they are seed nodes only because	131	Seed nodes themselves are not special - they are seed nodes only because
127	some other node I<uses> them as such, but any node can be used as seed	132	some other node I<uses> them as such, but any node can be used as seed
128	node for other nodes, and eahc node cna use a different set of seed nodes.	133	node for other nodes, and eahc node can use a different set of seed nodes.
129		134
130	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
131	maintain the network - all nodes using the same seed node form are part of	136	maintain the network - all nodes using the same seed node are part of the
132	the same network. If a network is split into multiple subnets because e.g.	137	same network. If a network is split into multiple subnets because e.g. the
133	the network link between the parts goes down, then using the same seed	138	network link between the parts goes down, then using the same seed nodes
134	nodes for all nodes ensures that eventually the subnets get merged again.	139	for all nodes ensures that eventually the subnets get merged again.
135		140
136	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
137	should always be available. They should also be relatively responsive - a	142	should always be available. They should also be relatively responsive - a
138	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.
139		144
…		…
163		168
164	Any node that loads the L<AnyEvent::MP::Global> module becomes a global	169	Any node that loads the L<AnyEvent::MP::Global> module becomes a global
165	node and tries to keep connections to all other nodes. So while it can	170	node and tries to keep connections to all other nodes. So while it can
166	make sense to make every node "global" in small networks, it usually makes	171	make sense to make every node "global" in small networks, it usually makes
167	sense to only make seed nodes into global nodes in large networks (nodes	172	sense to only make seed nodes into global nodes in large networks (nodes
168	keep connections to seed nodes and global nodes, so makign them the same	173	keep connections to seed nodes and global nodes, so making them the same
169	reduces overhead).	174	reduces overhead).
170		175
171	=back	176	=back
172		177
173	=head1 VARIABLES/FUNCTIONS	178	=head1 VARIABLES/FUNCTIONS
…		…
178		183
179	package AnyEvent::MP;	184	package AnyEvent::MP;
180		185
181	use AnyEvent::MP::Config ();	186	use AnyEvent::MP::Config ();
182	use AnyEvent::MP::Kernel;	187	use AnyEvent::MP::Kernel;
183	use AnyEvent::MP::Kernel qw(%NODE %PORT %PORT_DATA $UNIQ $RUNIQ $ID);	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	);
184		199
185	use common::sense;	200	use common::sense;
186		201
187	use Carp ();	202	use Carp ();
188		203
189	use AE ();	204	use AnyEvent ();
190	use Guard ();	205	use Guard ();
191		206
192	use base "Exporter";	207	use base "Exporter";
193		208
194	our $VERSION = $AnyEvent::MP::Config::VERSION;	209	our $VERSION = '2.02'; # also in MP/Config.pm
195		210
196	our @EXPORT = qw(	211	our @EXPORT = qw(
197	NODE $NODE *SELF node_of after
198	configure	212	configure
		213
		214	NODE $NODE
		215	*SELF
		216
		217	node_of port_is_local
		218
		219	snd kil
199	snd rcv mon mon_guard kil psub peval spawn cal	220	port rcv mon mon_guard psub peval spawn cal
200	port
201	db_set db_del db_reg	221	db_set db_del db_reg
202	db_mon db_family db_keys db_values	222	db_mon db_family db_keys db_values
		223
		224	after
203	);	225	);
204		226
205	our $SELF;	227	our $SELF;
206		228
207	sub _self_die() {	229	sub _self_die() {
…		…
218		240
219	=item $nodeid = node_of $port	241	=item $nodeid = node_of $port
220		242
221	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.
222		244
		245	=item $is_local = port_is_local $port
		246
		247	Returns true iff the port is a local port.
		248
223	=item configure $profile, key => value...	249	=item configure $profile, key => value...
224		250
225	=item configure key => value...	251	=item configure key => value...
226		252
227	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
…		…
238	=over 4	264	=over 4
239		265
240	=item norc => $boolean (default false)	266	=item norc => $boolean (default false)
241		267
242	If true, then the rc file (e.g. F<~/.perl-anyevent-mp>) will I<not>	268	If true, then the rc file (e.g. F<~/.perl-anyevent-mp>) will I<not>
243	be consulted - all configuraiton options must be specified in the	269	be consulted - all configuration options must be specified in the
244	C<configure> call.	270	C<configure> call.
245		271
246	=item force => $boolean (default false)	272	=item force => $boolean (default false)
247		273
248	IF true, then the values specified in the C<configure> will take	274	IF true, then the values specified in the C<configure> will take
249	precedence over any values configured via the rc file. The default is for	275	precedence over any values configured via the rc file. The default is for
250	the rc file to override any options specified in the program.	276	the rc file to override any options specified in the program.
251
252	=item secure => $pass->(@msg)
253
254	In addition to specifying a boolean, you can specify a code reference that
255	is called for every code execution attempt - the execution request is
256	granted iff the callback returns a true value.
257
258	Most of the time the callback should look only at
259	C<$AnyEvent::MP::Kernel::SRCNODE> to make a decision, and not at the
260	actual message (which can be about anything, and is mostly provided for
261	diagnostic purposes).
262
263	See F<semp setsecure> for more info.
264		277
265	=back	278	=back
266		279
267	=over 4	280	=over 4
268		281
…		…
297		310
298	=item step 2, bind listener sockets	311	=item step 2, bind listener sockets
299		312
300	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
301	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
302	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
303	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
304	binds, but it can still talk to all "normal" nodes).	317	binds, but it can still talk to all "normal" nodes).
305		318
306	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
307	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
…		…
404	=cut	417	=cut
405		418
406	sub rcv($@);	419	sub rcv($@);
407		420
408	my $KILME = sub {	421	my $KILME = sub {
409	(my $tag = substr $_[0], 0, 30) =~ s/([\x20-\x7e])/./g;	422	(my $tag = substr $_[0], 0, 30) =~ s/([^\x20-\x7e])/./g;
410	kil $SELF, unhandled_message => "no callback found for message '$tag'";	423	kil $SELF, unhandled_message => "no callback found for message '$tag'";
411	};	424	};
412		425
413	sub port(;&) {	426	sub port(;&) {
414	my $id = $UNIQ . ++$ID;	427	my $id = $UNIQ . ++$ID;
…		…
472		485
473	sub rcv($@) {	486	sub rcv($@) {
474	my $port = shift;	487	my $port = shift;
475	my ($nodeid, $portid) = split /#/, $port, 2;	488	my ($nodeid, $portid) = split /#/, $port, 2;
476		489
477	$NODE{$nodeid} == $NODE{""}	490	$nodeid eq $NODE
478	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";
479		492
480	while (@_) {	493	while (@_) {
481	if (ref $_[0]) {	494	if (ref $_[0]) {
482	if (my $self = $PORT_DATA{$portid}) {	495	if (my $self = $PORT_DATA{$portid}) {
…		…
525	$port	538	$port
526	}	539	}
527		540
528	=item peval $port, $coderef[, @args]	541	=item peval $port, $coderef[, @args]
529		542
530	Evaluates the given C<$codref> within the contetx of C<$port>, that is,	543	Evaluates the given C<$codref> within the context of C<$port>, that is,
531	when the code throews an exception the C<$port> will be killed.	544	when the code throws an exception the C<$port> will be killed.
532		545
533	Any remaining args will be passed to the callback. Any return values will	546	Any remaining args will be passed to the callback. Any return values will
534	be returned to the caller.	547	be returned to the caller.
535		548
536	This is useful when you temporarily want to execute code in the context of	549	This is useful when you temporarily want to execute code in the context of
…		…
601	$res	614	$res
602	}	615	}
603	}	616	}
604	}	617	}
605		618
		619	=item $guard = mon $port, $rcvport # kill $rcvport when $port dies
		620
		621	=item $guard = mon $port # kill $SELF when $port dies
		622
606	=item $guard = mon $port, $cb->(@reason) # call $cb when $port dies	623	=item $guard = mon $port, $cb->(@reason) # call $cb when $port dies
607
608	=item $guard = mon $port, $rcvport # kill $rcvport when $port dies
609
610	=item $guard = mon $port # kill $SELF when $port dies
611		624
612	=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
613		626
614	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
615	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
616	to stop monitoring again.	629	to stop monitoring again.
617		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
618	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
619	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
620	"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
621	C<eval> if unsure.	648	C<eval> if unsure.
622		649
623	In the second form (another port given), the other port (C<$rcvport>)
624	will be C<kil>'ed with C<@reason>, if a @reason was specified, i.e. on
625	"normal" kils nothing happens, while under all other conditions, the other
626	port is killed with the same reason.
627
628	The third form (kill self) is the same as the second form, except that
629	C<$rvport> defaults to C<$SELF>.
630
631	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,
632	C<snd>.	651	@reason> will be C<snd>.
633		652
634	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
635	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.
636		656
637	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
638	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
639	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
640	even monitoring requests can get lost (for example, when the connection	660	obvious reason is that even monitoring requests can get lost (for example,
641	to the other node goes down permanently). When monitoring a port locally	661	when the connection to the other node goes down permanently). When
642	these problems do not exist.	662	monitoring a port locally these problems do not exist.
643		663
644	C<mon> effectively guarantees that, in the absence of hardware failures,	664	C<mon> effectively guarantees that, in the absence of hardware failures,
645	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
646	arrive, or the monitoring action will be invoked after possible message	666	arrive, or the monitoring action will be invoked after possible message
647	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
…		…
969	If you feel the need to monitor or query a single subkey, try giving it	989	If you feel the need to monitor or query a single subkey, try giving it
970	it's own family.	990	it's own family.
971		991
972	=over	992	=over
973		993
974	=item db_set $family => $subkey [=> $value]	994	=item $guard = db_set $family => $subkey [=> $value]
975		995
976	Sets (or replaces) a key to the database - if C<$value> is omitted,	996	Sets (or replaces) a key to the database - if C<$value> is omitted,
977	C<undef> is used instead.	997	C<undef> is used instead.
978		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
979	=item db_del $family => $subkey...	1002	=item db_del $family => $subkey...
980		1003
981	Deletes one or more subkeys from the database family.	1004	Deletes one or more subkeys from the database family.
982		1005
983	=item $guard = db_reg $family => $subkey [=> $value]	1006	=item $guard = db_reg $family => $port => $value
984		1007
985	Sets the key on the database and returns a guard. When the guard is	1008	=item $guard = db_reg $family => $port
986	destroyed, the key is deleted from the database. If C<$value> is missing,	1009
987	then C<undef> is used.	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	}
988		1043
989	=item db_family $family => $cb->(\%familyhash)	1044	=item db_family $family => $cb->(\%familyhash)
990		1045
991	Queries the named database C<$family> and call the callback with the	1046	Queries the named database C<$family> and call the callback with the
992	family represented as a hash. You can keep and freely modify the hash.	1047	family represented as a hash. You can keep and freely modify the hash.
…		…
999	=item db_values $family => $cb->(\@values)	1054	=item db_values $family => $cb->(\@values)
1000		1055
1001	Same as C<db_family>, except it only queries the family I<values> and passes them	1056	Same as C<db_family>, except it only queries the family I<values> and passes them
1002	as array reference to the callback.	1057	as array reference to the callback.
1003		1058
1004	=item $guard = db_mon $family => $cb->($familyhash, \@added, \@changed, \@deleted)	1059	=item $guard = db_mon $family => $cb->(\%familyhash, \@added, \@changed, \@deleted)
1005		1060
1006	Creates a monitor on the given database family. Each time a key is set	1061	Creates a monitor on the given database family. Each time a key is
1007	or or is deleted the callback is called with a hash containing the	1062	set or is deleted the callback is called with a hash containing the
1008	database family and three lists of added, changed and deleted subkeys,	1063	database family and three lists of added, changed and deleted subkeys,
1009	respectively. If no keys have changed then the array reference might be	1064	respectively. If no keys have changed then the array reference might be
1010	C<undef> or even missing.	1065	C<undef> or even missing.
1011		1066
1012	If not called in void context, a guard object is returned that, when	1067	If not called in void context, a guard object is returned that, when
…		…
1040	return unless %$family;	1095	return unless %$family;
1041	undef $guard;	1096	undef $guard;
1042	print "My::Module::workers now nonempty\n";	1097	print "My::Module::workers now nonempty\n";
1043	};	1098	};
1044		1099
1045	Example: print all changes to the family "AnyRvent::Fantasy::Module".	1100	Example: print all changes to the family "AnyEvent::Fantasy::Module".
1046		1101
1047	my $guard = db_mon AnyRvent::Fantasy::Module => sub {	1102	my $guard = db_mon AnyEvent::Fantasy::Module => sub {
1048	my ($family, $a, $c, $d) = @_;	1103	my ($family, $a, $c, $d) = @_;
1049		1104
1050	print "+$_=$family->{$_}\n" for @$a;	1105	print "+$_=$family->{$_}\n" for @$a;
1051	print "*$_=$family->{$_}\n" for @$c;	1106	print "*$_=$family->{$_}\n" for @$c;
1052	print "-$_=$family->{$_}\n" for @$d;	1107	print "-$_=$family->{$_}\n" for @$d;
…		…
1103	filter messages without dequeuing them.	1158	filter messages without dequeuing them.
1104		1159
1105	This is not a philosophical difference, but simply stems from AnyEvent::MP	1160	This is not a philosophical difference, but simply stems from AnyEvent::MP
1106	being event-based, while Erlang is process-based.	1161	being event-based, while Erlang is process-based.
1107		1162
1108	You cna have a look at L<Coro::MP> for a more Erlang-like process model on	1163	You can have a look at L<Coro::MP> for a more Erlang-like process model on
1109	top of AEMP and Coro threads.	1164	top of AEMP and Coro threads.
1110		1165
1111	=item * Erlang sends are synchronous, AEMP sends are asynchronous.	1166	=item * Erlang sends are synchronous, AEMP sends are asynchronous.
1112		1167
1113	Sending messages in Erlang is synchronous and blocks the process until	1168	Sending messages in Erlang is synchronous and blocks the process until
1114	a conenction has been established and the message sent (and so does not	1169	a connection has been established and the message sent (and so does not
1115	need a queue that can overflow). AEMP sends return immediately, connection	1170	need a queue that can overflow). AEMP sends return immediately, connection
1116	establishment is handled in the background.	1171	establishment is handled in the background.
1117		1172
1118	=item * Erlang suffers from silent message loss, AEMP does not.	1173	=item * Erlang suffers from silent message loss, AEMP does not.
1119		1174
…		…
1217	Keeping your messages simple, concentrating on data structures rather than	1272	Keeping your messages simple, concentrating on data structures rather than
1218	objects, will keep your messages clean, tidy and efficient.	1273	objects, will keep your messages clean, tidy and efficient.
1219		1274
1220	=back	1275	=back
1221		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
1222	=head1 SEE ALSO	1385	=head1 SEE ALSO
1223		1386
1224	L<AnyEvent::MP::Intro> - a gentle introduction.	1387	L<AnyEvent::MP::Intro> - a gentle introduction.
1225		1388
1226	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.	1389	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.

Diff Legend

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

Comparing cvsroot/AnyEvent-MP/MP.pm (file contents): Revision 1.136 by root, Wed Mar 21 15:22:16 2012 UTC vs. Revision 1.153 by root, Sat Nov 2 01:30:49 2019 UTC

Diff Legend

Comparing cvsroot/AnyEvent-MP/MP.pm (file contents):
Revision 1.136 by root, Wed Mar 21 15:22:16 2012 UTC vs.
Revision 1.153 by root, Sat Nov 2 01:30:49 2019 UTC