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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.134 by root, Mon Mar 12 14:47:23 2012 UTC vs.
Revision 1.138 by root, Thu Mar 22 00:48:29 2012 UTC

…		…
247		247
248	IF true, then the values specified in the C<configure> will take	248	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	249	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.	250	the rc file to override any options specified in the program.
251		251
252	=item secure => $pass->($nodeid)	252	=item secure => $pass->(@msg)
253		253
254	In addition to specifying a boolean, you can specify a code reference that	254	In addition to specifying a boolean, you can specify a code reference that
255	is called for every remote execution attempt - the execution request is	255	is called for every code execution attempt - the execution request is
256	granted iff the callback returns a true value.	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).
257		262
258	See F<semp setsecure> for more info.	263	See F<semp setsecure> for more info.
259		264
260	=back	265	=back
261		266
…		…
400		405
401	sub rcv($@);	406	sub rcv($@);
402		407
403	my $KILME = sub {	408	my $KILME = sub {
404	(my $tag = substr $_[0], 0, 30) =~ s/([\x20-\x7e])/./g;	409	(my $tag = substr $_[0], 0, 30) =~ s/([\x20-\x7e])/./g;
405	kil $SELF, unhandled_message => "missing (tag or fallback) callback for message '$tag'";	410	kil $SELF, unhandled_message => "no callback found for message '$tag'";
406	};	411	};
407		412
408	sub port(;&) {	413	sub port(;&) {
409	my $id = $UNIQ . ++$ID;	414	my $id = $UNIQ . ++$ID;
410	my $port = "$NODE#$id";	415	my $port = "$NODE#$id";
…		…
964	If you feel the need to monitor or query a single subkey, try giving it	969	If you feel the need to monitor or query a single subkey, try giving it
965	it's own family.	970	it's own family.
966		971
967	=over	972	=over
968		973
969	=item db_set $family => $subkey [=> $value]	974	=item $guard = db_set $family => $subkey [=> $value]
970		975
971	Sets (or replaces) a key to the database - if C<$value> is omitted,	976	Sets (or replaces) a key to the database - if C<$value> is omitted,
972	C<undef> is used instead.	977	C<undef> is used instead.
973		978
		979	When called in non-void context, C<db_set> returns a guard that
		980	automatically calls C<db_del> when it is destroyed.
		981
974	=item db_del $family => $subkey...	982	=item db_del $family => $subkey...
975		983
976	Deletes one or more subkeys from the database family.	984	Deletes one or more subkeys from the database family.
977		985
978	=item $guard = db_reg $family => $subkey [=> $value]	986	=item $guard = db_reg $family => $port => $value
979		987
980	Sets the key on the database and returns a guard. When the guard is	988	=item $guard = db_reg $family => $port
981	destroyed, the key is deleted from the database. If C<$value> is missing,	989
982	then C<undef> is used.	990	=item $guard = db_reg $family
		991
		992	Registers a port in the given family and optionally returns a guard to
		993	remove it.
		994
		995	This function basically does the same as:
		996
		997	db_set $family => $port => $value
		998
		999	Except that the port is monitored and automatically removed from the
		1000	database family when it is kil'ed.
		1001
		1002	If C<$value> is missing, C<undef> is used. If C<$port> is missing, then
		1003	C<$SELF> is used.
		1004
		1005	This function is most useful to register a port in some port group (which
		1006	is just another name for a database family), and have it removed when the
		1007	port is gone. This works best when the port is a local port.
		1008
		1009	=cut
		1010
		1011	sub db_reg($$;$) {
		1012	my $family = shift;
		1013	my $port = @_ ? shift : $SELF;
		1014
		1015	my $clr = sub { db_del $family => $port };
		1016	mon $port, $clr;
		1017
		1018	db_set $family => $port => $_[0];
		1019
		1020	defined wantarray
		1021	and &Guard::guard ($clr)
		1022	}
983		1023
984	=item db_family $family => $cb->(\%familyhash)	1024	=item db_family $family => $cb->(\%familyhash)
985		1025
986	Queries the named database C<$family> and call the callback with the	1026	Queries the named database C<$family> and call the callback with the
987	family represented as a hash. You can keep and freely modify the hash.	1027	family represented as a hash. You can keep and freely modify the hash.
…		…
1212	Keeping your messages simple, concentrating on data structures rather than	1252	Keeping your messages simple, concentrating on data structures rather than
1213	objects, will keep your messages clean, tidy and efficient.	1253	objects, will keep your messages clean, tidy and efficient.
1214		1254
1215	=back	1255	=back
1216		1256
		1257	=head1 PORTING FROM AnyEvent::MP VERSION 1.X
		1258
		1259	AEMP version 2 has three major incompatible changes compared to version 1:
		1260
		1261	=over 4
		1262
		1263	=item AnyEvent::MP::Global no longer has group management functions.
		1264
		1265	AnyEvent::MP now comes with a distributed database that is more
		1266	powerful. It's database families map closely to ports, but the API has
		1267	minor differences:
		1268
		1269	grp_reg $group, $port # old
		1270	db_reg $group, $port # new
		1271
		1272	$list = grp_get $group # old
		1273	db_keys $group, sub { my $list = shift } # new
		1274
		1275	grp_mon $group, $cb->(\@ports, $add, $del) # old
		1276	db_mon $group, $cb->(\%ports, $add, $change, $del) # new
		1277
		1278	C<grp_reg> is a no-brainer (just replace by C<db_reg>), but C<grp_get>
		1279	is no longer instant, because the local node might not have a copy of
		1280	the group. This can be partially remedied by using C<db_mon> to keep an
		1281	updated copy of the group:
		1282
		1283	my $local_group_copy;
		1284	db_mon $group => sub { $local_group_copy = shift };
		1285
		1286	# no keys %$local_group_copy always returns the most up-to-date
		1287	# list of ports in the group.
		1288
		1289	C<grp_mon> can almost be replaced by C<db_mon>:
		1290
		1291	db_mon $group => sub {
		1292	my ($ports, $add, $chg, $lde) = @_;
		1293	$ports = [keys %$ports];
		1294
		1295	# now $ports, $add and $del are the same as
		1296	# were originally passed by grp_mon.
		1297	...
		1298	};
		1299
		1300	=item Nodes not longer connect to all other nodes.
		1301
		1302	In AEMP 1.x, every node automatically loads the L<AnyEvent::MP::Global>
		1303	module, which in turn would create connections to all other nodes in the
		1304	network (helped by the seed nodes).
		1305
		1306	In version 2.x, global nodes still connect to all other global nodes, but
		1307	other nodes don't - now every node either is a global node itself, or
		1308	attaches itself to another global node.
		1309
		1310	If a node isn't a global node itself, then it attaches itself to one
		1311	of its seed nodes. If that seed node isn't a global node yet, it will
		1312	automatically be upgraded to a global node.
		1313
		1314	So in many cases, nothing needs to be changed - one just has to make sure
		1315	that all seed nodes are meshed together with the other seed nodes (as with
		1316	AEMP 1.x), and other nodes specify them as seed nodes.
		1317
		1318	Not opening a connection to every other node is usually an advantage,
		1319	except when you need the lower latency of an already established
		1320	connection. To ensure a node establishes a connection to another node,
		1321	you can monitor the node port (C<mon $node, ...>), which will attempt to
		1322	create the connection (and notify you when the connection fails).
		1323
		1324	=item Listener-less nodes (nodes without binds) are gone.
		1325
		1326	And are not coming back, at least not in their old form. If no C<binds>
		1327	are specified for a node, AnyEvent::MP now assumes a default of C<:>.
		1328
		1329	There are vague plans to implement some form of routing domains, which
		1330	might or might not bring back listener-less nodes, but don't count on it.
		1331
		1332	The fact that most connections are now optional somewhat mitigates this,
		1333	as a node can be effectively unreachable from the outside without any
		1334	problems, as long as it isn't a global node and only reaches out to other
		1335	nodes (as opposed to being contacted from other nodes).
		1336
		1337	=item $AnyEvent::MP::Kernel::WARN has gone.
		1338
		1339	AnyEvent has acquired a logging framework (L<AnyEvent::Log>), and AEMP now
		1340	uses this, and so should your programs.
		1341
		1342	Every module now documents what kinds of messages it generates, with
		1343	AnyEvent::MP acting as a catch all.
		1344
		1345	On the positive side, this means that instead of setting
		1346	C<PERL_ANYEVENT_MP_WARNLEVEL>, you can get away by setting C<AE_VERBOSE>,
		1347	much less to type.
		1348
		1349	=back
		1350
1217	=head1 SEE ALSO	1351	=head1 SEE ALSO
1218		1352
1219	L<AnyEvent::MP::Intro> - a gentle introduction.	1353	L<AnyEvent::MP::Intro> - a gentle introduction.
1220		1354
1221	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.	1355	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.134 by root, Mon Mar 12 14:47:23 2012 UTC vs. Revision 1.138 by root, Thu Mar 22 00:48:29 2012 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.134 by root, Mon Mar 12 14:47:23 2012 UTC vs.
Revision 1.138 by root, Thu Mar 22 00:48:29 2012 UTC