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

Comparing cvsroot/AnyEvent-MP/MP.pm (file contents):
Revision 1.123 by root, Thu Mar 1 19:37:59 2012 UTC vs.
Revision 1.136 by root, Wed Mar 21 15:22:16 2012 UTC

…		…
35	# destroy a port again	35	# destroy a port again
36	kil $port; # "normal" kill	36	kil $port; # "normal" kill
37	kil $port, my_error => "everything is broken"; # error kill	37	kil $port, my_error => "everything is broken"; # error kill
38		38
39	# monitoring	39	# monitoring
40	mon $localport, $cb->(@msg) # callback is invoked on death	40	mon $port, $cb->(@msg) # callback is invoked on death
41	mon $localport, $otherport # kill otherport on abnormal death	41	mon $port, $localport # kill localport on abnormal death
42	mon $localport, $otherport, @msg # send message on death	42	mon $port, $localport, @msg # send message on death
43		43
44	# temporarily execute code in port context	44	# temporarily execute code in port context
45	peval $port, sub { die "kill the port!" };	45	peval $port, sub { die "kill the port!" };
46		46
47	# execute callbacks in $SELF port context	47	# execute callbacks in $SELF port context
…		…
185	use common::sense;	185	use common::sense;
186		186
187	use Carp ();	187	use Carp ();
188		188
189	use AE ();	189	use AE ();
		190	use Guard ();
190		191
191	use base "Exporter";	192	use base "Exporter";
192		193
193	our $VERSION = $AnyEvent::MP::Config::VERSION;	194	our $VERSION = $AnyEvent::MP::Config::VERSION;
194		195
195	our @EXPORT = qw(	196	our @EXPORT = qw(
196	NODE $NODE *SELF node_of after	197	NODE $NODE *SELF node_of after
197	configure	198	configure
198	snd rcv mon mon_guard kil psub peval spawn cal	199	snd rcv mon mon_guard kil psub peval spawn cal
199	port	200	port
		201	db_set db_del db_reg
		202	db_mon db_family db_keys db_values
200	);	203	);
201		204
202	our $SELF;	205	our $SELF;
203		206
204	sub _self_die() {	207	sub _self_die() {
…		…
228		231
229	This function configures a node - it must be called exactly once (or	232	This function configures a node - it must be called exactly once (or
230	never) before calling other AnyEvent::MP functions.	233	never) before calling other AnyEvent::MP functions.
231		234
232	The key/value pairs are basically the same ones as documented for the	235	The key/value pairs are basically the same ones as documented for the
233	F<aemp> command line utility (sans the set/del prefix), with two additions:	236	F<aemp> command line utility (sans the set/del prefix), with these additions:
234		237
235	=over 4	238	=over 4
236		239
237	=item norc => $boolean (default false)	240	=item norc => $boolean (default false)
238		241
…		…
243	=item force => $boolean (default false)	246	=item force => $boolean (default false)
244		247
245	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
246	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
247	the rc file to override any options specified in the program.	250	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.
248		264
249	=back	265	=back
250		266
251	=over 4	267	=over 4
252		268
…		…
269	and the values specified directly via C<configure> have lowest priority,	285	and the values specified directly via C<configure> have lowest priority,
270	and can only be used to specify defaults.	286	and can only be used to specify defaults.
271		287
272	If the profile specifies a node ID, then this will become the node ID of	288	If the profile specifies a node ID, then this will become the node ID of
273	this process. If not, then the profile name will be used as node ID, with	289	this process. If not, then the profile name will be used as node ID, with
274	a slash (C</>) attached.	290	a unique randoms tring (C</%u>) appended.
275		291
276	If the node ID (or profile name) ends with a slash (C</>), then a random	292	The node ID can contain some C<%> sequences that are expanded: C<%n>
277	string is appended to make it unique.	293	is expanded to the local nodename, C<%u> is replaced by a random
		294	strign to make the node unique. For example, the F<aemp> commandline
		295	utility uses C<aemp/%n/%u> as nodename, which might expand to
		296	C<aemp/cerebro/ZQDGSIkRhEZQDGSIkRhE>.
278		297
279	=item step 2, bind listener sockets	298	=item step 2, bind listener sockets
280		299
281	The next step is to look up the binds in the profile, followed by binding	300	The next step is to look up the binds in the profile, followed by binding
282	aemp protocol listeners on all binds specified (it is possible and valid	301	aemp protocol listeners on all binds specified (it is possible and valid
…		…
299	Example: become a distributed node using the local node name as profile.	318	Example: become a distributed node using the local node name as profile.
300	This should be the most common form of invocation for "daemon"-type nodes.	319	This should be the most common form of invocation for "daemon"-type nodes.
301		320
302	configure	321	configure
303		322
304	Example: become an anonymous node. This form is often used for commandline	323	Example: become a semi-anonymous node. This form is often used for
305	clients.	324	commandline clients.
306		325
307	configure nodeid => "anon/";	326	configure nodeid => "myscript/%n/%u";
308		327
309	Example: configure a node using a profile called seed, which is suitable	328	Example: configure a node using a profile called seed, which is suitable
310	for a seed node as it binds on all local addresses on a fixed port (4040,	329	for a seed node as it binds on all local addresses on a fixed port (4040,
311	customary for aemp).	330	customary for aemp).
312		331
…		…
384		403
385	=cut	404	=cut
386		405
387	sub rcv($@);	406	sub rcv($@);
388		407
389	sub _kilme {	408	my $KILME = sub {
390	die "received message on port without callback";	409	(my $tag = substr $_[0], 0, 30) =~ s/([\x20-\x7e])/./g;
391	}	410	kil $SELF, unhandled_message => "no callback found for message '$tag'";
		411	};
392		412
393	sub port(;&) {	413	sub port(;&) {
394	my $id = $UNIQ . ++$ID;	414	my $id = $UNIQ . ++$ID;
395	my $port = "$NODE#$id";	415	my $port = "$NODE#$id";
396		416
397	rcv $port, shift \|\| \&_kilme;	417	rcv $port, shift \|\| $KILME;
398		418
399	$port	419	$port
400	}	420	}
401		421
402	=item rcv $local_port, $callback->(@msg)	422	=item rcv $local_port, $callback->(@msg)
…		…
407		427
408	The global C<$SELF> (exported by this module) contains C<$port> while	428	The global C<$SELF> (exported by this module) contains C<$port> while
409	executing the callback. Runtime errors during callback execution will	429	executing the callback. Runtime errors during callback execution will
410	result in the port being C<kil>ed.	430	result in the port being C<kil>ed.
411		431
412	The default callback received all messages not matched by a more specific	432	The default callback receives all messages not matched by a more specific
413	C<tag> match.	433	C<tag> match.
414		434
415	=item rcv $local_port, tag => $callback->(@msg_without_tag), ...	435	=item rcv $local_port, tag => $callback->(@msg_without_tag), ...
416		436
417	Register (or replace) callbacks to be called on messages starting with the	437	Register (or replace) callbacks to be called on messages starting with the
…		…
672	}	692	}
673		693
674	$node->monitor ($port, $cb);	694	$node->monitor ($port, $cb);
675		695
676	defined wantarray	696	defined wantarray
677	and ($cb += 0, AnyEvent::Util::guard { $node->unmonitor ($port, $cb) })	697	and ($cb += 0, Guard::guard { $node->unmonitor ($port, $cb) })
678	}	698	}
679		699
680	=item $guard = mon_guard $port, $ref, $ref...	700	=item $guard = mon_guard $port, $ref, $ref...
681		701
682	Monitors the given C<$port> and keeps the passed references. When the port	702	Monitors the given C<$port> and keeps the passed references. When the port
…		…
718	will be reported as reason C<< die => $@ >>.	738	will be reported as reason C<< die => $@ >>.
719		739
720	Transport/communication errors are reported as C<< transport_error =>	740	Transport/communication errors are reported as C<< transport_error =>
721	$message >>.	741	$message >>.
722		742
723	=cut	743	Common idioms:
		744
		745	# silently remove yourself, do not kill linked ports
		746	kil $SELF;
		747
		748	# report a failure in some detail
		749	kil $SELF, failure_mode_1 => "it failed with too high temperature";
		750
		751	# do not waste much time with killing, just die when something goes wrong
		752	open my $fh, "<file"
		753	or die "file: $!";
724		754
725	=item $port = spawn $node, $initfunc[, @initdata]	755	=item $port = spawn $node, $initfunc[, @initdata]
726		756
727	Creates a port on the node C<$node> (which can also be a port ID, in which	757	Creates a port on the node C<$node> (which can also be a port ID, in which
728	case it's the node where that port resides).	758	case it's the node where that port resides).
…		…
820	ref $action[0]	850	ref $action[0]
821	? $action[0]()	851	? $action[0]()
822	: snd @action;	852	: snd @action;
823	};	853	};
824	}	854	}
		855
		856	#=item $cb2 = timeout $seconds, $cb[, @args]
825		857
826	=item cal $port, @msg, $callback[, $timeout]	858	=item cal $port, @msg, $callback[, $timeout]
827		859
828	A simple form of RPC - sends a message to the given C<$port> with the	860	A simple form of RPC - sends a message to the given C<$port> with the
829	given contents (C<@msg>), but adds a reply port to the message.	861	given contents (C<@msg>), but adds a reply port to the message.
…		…
875	$port	907	$port
876	}	908	}
877		909
878	=back	910	=back
879		911
		912	=head1 DISTRIBUTED DATABASE
		913
		914	AnyEvent::MP comes with a simple distributed database. The database will
		915	be mirrored asynchronously on all global nodes. Other nodes bind to one
		916	of the global nodes for their needs. Every node has a "local database"
		917	which contains all the values that are set locally. All local databases
		918	are merged together to form the global database, which can be queried.
		919
		920	The database structure is that of a two-level hash - the database hash
		921	contains hashes which contain values, similarly to a perl hash of hashes,
		922	i.e.:
		923
		924	$DATABASE{$family}{$subkey} = $value
		925
		926	The top level hash key is called "family", and the second-level hash key
		927	is called "subkey" or simply "key".
		928
		929	The family must be alphanumeric, i.e. start with a letter and consist
		930	of letters, digits, underscores and colons (C<[A-Za-z][A-Za-z0-9_:]*>,
		931	pretty much like Perl module names.
		932
		933	As the family namespace is global, it is recommended to prefix family names
		934	with the name of the application or module using it.
		935
		936	The subkeys must be non-empty strings, with no further restrictions.
		937
		938	The values should preferably be strings, but other perl scalars should
		939	work as well (such as C<undef>, arrays and hashes).
		940
		941	Every database entry is owned by one node - adding the same family/subkey
		942	combination on multiple nodes will not cause discomfort for AnyEvent::MP,
		943	but the result might be nondeterministic, i.e. the key might have
		944	different values on different nodes.
		945
		946	Different subkeys in the same family can be owned by different nodes
		947	without problems, and in fact, this is the common method to create worker
		948	pools. For example, a worker port for image scaling might do this:
		949
		950	db_set my_image_scalers => $port;
		951
		952	And clients looking for an image scaler will want to get the
		953	C<my_image_scalers> keys from time to time:
		954
		955	db_keys my_image_scalers => sub {
		956	@ports = @{ $_[0] };
		957	};
		958
		959	Or better yet, they want to monitor the database family, so they always
		960	have a reasonable up-to-date copy:
		961
		962	db_mon my_image_scalers => sub {
		963	@ports = keys %{ $_[0] };
		964	};
		965
		966	In general, you can set or delete single subkeys, but query and monitor
		967	whole families only.
		968
		969	If you feel the need to monitor or query a single subkey, try giving it
		970	it's own family.
		971
		972	=over
		973
		974	=item db_set $family => $subkey [=> $value]
		975
		976	Sets (or replaces) a key to the database - if C<$value> is omitted,
		977	C<undef> is used instead.
		978
		979	=item db_del $family => $subkey...
		980
		981	Deletes one or more subkeys from the database family.
		982
		983	=item $guard = db_reg $family => $subkey [=> $value]
		984
		985	Sets the key on the database and returns a guard. When the guard is
		986	destroyed, the key is deleted from the database. If C<$value> is missing,
		987	then C<undef> is used.
		988
		989	=item db_family $family => $cb->(\%familyhash)
		990
		991	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.
		993
		994	=item db_keys $family => $cb->(\@keys)
		995
		996	Same as C<db_family>, except it only queries the family I<subkeys> and passes
		997	them as array reference to the callback.
		998
		999	=item db_values $family => $cb->(\@values)
		1000
		1001	Same as C<db_family>, except it only queries the family I<values> and passes them
		1002	as array reference to the callback.
		1003
		1004	=item $guard = db_mon $family => $cb->($familyhash, \@added, \@changed, \@deleted)
		1005
		1006	Creates a monitor on the given database family. Each time a key is set
		1007	or or is deleted the callback is called with a hash containing the
		1008	database family and three lists of added, changed and deleted subkeys,
		1009	respectively. If no keys have changed then the array reference might be
		1010	C<undef> or even missing.
		1011
		1012	If not called in void context, a guard object is returned that, when
		1013	destroyed, stops the monitor.
		1014
		1015	The family hash reference and the key arrays belong to AnyEvent::MP and
		1016	B<must not be modified or stored> by the callback. When in doubt, make a
		1017	copy.
		1018
		1019	As soon as possible after the monitoring starts, the callback will be
		1020	called with the intiial contents of the family, even if it is empty,
		1021	i.e. there will always be a timely call to the callback with the current
		1022	contents.
		1023
		1024	It is possible that the callback is called with a change event even though
		1025	the subkey is already present and the value has not changed.
		1026
		1027	The monitoring stops when the guard object is destroyed.
		1028
		1029	Example: on every change to the family "mygroup", print out all keys.
		1030
		1031	my $guard = db_mon mygroup => sub {
		1032	my ($family, $a, $c, $d) = @_;
		1033	print "mygroup members: ", (join " ", keys %$family), "\n";
		1034	};
		1035
		1036	Exmaple: wait until the family "My::Module::workers" is non-empty.
		1037
		1038	my $guard; $guard = db_mon My::Module::workers => sub {
		1039	my ($family, $a, $c, $d) = @_;
		1040	return unless %$family;
		1041	undef $guard;
		1042	print "My::Module::workers now nonempty\n";
		1043	};
		1044
		1045	Example: print all changes to the family "AnyRvent::Fantasy::Module".
		1046
		1047	my $guard = db_mon AnyRvent::Fantasy::Module => sub {
		1048	my ($family, $a, $c, $d) = @_;
		1049
		1050	print "+$_=$family->{$_}\n" for @$a;
		1051	print "*$_=$family->{$_}\n" for @$c;
		1052	print "-$_=$family->{$_}\n" for @$d;
		1053	};
		1054
		1055	=cut
		1056
		1057	=back
		1058
880	=head1 AnyEvent::MP vs. Distributed Erlang	1059	=head1 AnyEvent::MP vs. Distributed Erlang
881		1060
882	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node	1061	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
883	== aemp node, Erlang process == aemp port), so many of the documents and	1062	== aemp node, Erlang process == aemp port), so many of the documents and
884	programming techniques employed by Erlang apply to AnyEvent::MP. Here is a	1063	programming techniques employed by Erlang apply to AnyEvent::MP. Here is a

Diff Legend

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

Comparing cvsroot/AnyEvent-MP/MP.pm (file contents): Revision 1.123 by root, Thu Mar 1 19:37:59 2012 UTC vs. Revision 1.136 by root, Wed Mar 21 15:22:16 2012 UTC

Diff Legend

Comparing cvsroot/AnyEvent-MP/MP.pm (file contents):
Revision 1.123 by root, Thu Mar 1 19:37:59 2012 UTC vs.
Revision 1.136 by root, Wed Mar 21 15:22:16 2012 UTC