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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.77 by elmex, Thu Sep 3 07:57:30 2009 UTC vs.
Revision 1.127 by root, Sat Mar 3 20:35:10 2012 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 $localport, $cb->(@msg) # callback is invoked on death
37	mon $port, $otherport # kill otherport on abnormal death	41	mon $localport, $otherport # kill otherport on abnormal death
38	mon $port, $otherport, @msg # send message on death	42	mon $localport, $otherport, @msg # send message on death
		43
		44	# temporarily execute code in port context
		45	peval $port, sub { die "kill the port!" };
		46
		47	# execute callbacks in $SELF port context
		48	my $timer = AE::timer 1, 0, psub {
		49	die "kill the port, delayed";
		50	};
39		51
40	=head1 CURRENT STATUS	52	=head1 CURRENT STATUS
41		53
42	bin/aemp - stable.	54	bin/aemp - stable.
43	AnyEvent::MP - stable API, should work.	55	AnyEvent::MP - stable API, should work.
44	AnyEvent::MP::Intro - explains most concepts.	56	AnyEvent::MP::Intro - explains most concepts.
45	AnyEvent::MP::Kernel - mostly stable.	57	AnyEvent::MP::Kernel - mostly stable API.
46	AnyEvent::MP::Global - stable API, protocol not yet final.	58	AnyEvent::MP::Global - stable API.
47
48	stay tuned.
49		59
50	=head1 DESCRIPTION	60	=head1 DESCRIPTION
51		61
52	This module (-family) implements a simple message passing framework.	62	This module (-family) implements a simple message passing framework.
53		63
…		…
61		71
62	=over 4	72	=over 4
63		73
64	=item port	74	=item port
65		75
66	A port is something you can send messages to (with the C<snd> function).	76	Not to be confused with a TCP port, a "port" is something you can send
		77	messages to (with the C<snd> function).
67		78
68	Ports allow you to register C<rcv> handlers that can match all or just	79	Ports allow you to register C<rcv> handlers that can match all or just
69	some messages. Messages send to ports will not be queued, regardless of	80	some messages. Messages send to ports will not be queued, regardless of
70	anything was listening for them or not.	81	anything was listening for them or not.
71		82
		83	Ports are represented by (printable) strings called "port IDs".
		84
72	=item port ID - C<nodeid#portname>	85	=item port ID - C<nodeid#portname>
73		86
74	A port ID is the concatenation of a node ID, a hash-mark (C<#>) as	87	A port ID is the concatenation of a node ID, a hash-mark (C<#>)
75	separator, and a port name (a printable string of unspecified format).	88	as separator, and a port name (a printable string of unspecified
		89	format created by AnyEvent::MP).
76		90
77	=item node	91	=item node
78		92
79	A node is a single process containing at least one port - the node port,	93	A node is a single process containing at least one port - the node port,
80	which enables nodes to manage each other remotely, and to create new	94	which enables nodes to manage each other remotely, and to create new
81	ports.	95	ports.
82		96
83	Nodes are either public (have one or more listening ports) or private	97	Nodes are either public (have one or more listening ports) or private
84	(no listening ports). Private nodes cannot talk to other private nodes	98	(no listening ports). Private nodes cannot talk to other private nodes
85	currently.	99	currently, but all nodes can talk to public nodes.
86		100
		101	Nodes is represented by (printable) strings called "node IDs".
		102
87	=item node ID - C<[a-za-Z0-9_\-.:]+>	103	=item node ID - C<[A-Za-z0-9_\-.:]*>
88		104
89	A node ID is a string that uniquely identifies the node within a	105	A node ID is a string that uniquely identifies the node within a
90	network. Depending on the configuration used, node IDs can look like a	106	network. Depending on the configuration used, node IDs can look like a
91	hostname, a hostname and a port, or a random string. AnyEvent::MP itself	107	hostname, a hostname and a port, or a random string. AnyEvent::MP itself
92	doesn't interpret node IDs in any way.	108	doesn't interpret node IDs in any way except to uniquely identify a node.
93		109
94	=item binds - C<ip:port>	110	=item binds - C<ip:port>
95		111
96	Nodes can only talk to each other by creating some kind of connection to	112	Nodes can only talk to each other by creating some kind of connection to
97	each other. To do this, nodes should listen on one or more local transport	113	each other. To do this, nodes should listen on one or more local transport
		114	endpoints - binds.
		115
98	endpoints - binds. Currently, only standard C<ip:port> specifications can	116	Currently, only standard C<ip:port> specifications can be used, which
99	be used, which specify TCP ports to listen on.	117	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.
100		119
		120	=item seed nodes
		121
		122	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
		124	network. These other nodes are called "seed nodes".
		125
		126	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
		128	node for other nodes, and eahc node cna use a different set of seed nodes.
		129
		130	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
		132	the same network. If a network is split into multiple subnets because e.g.
		133	the network link between the parts goes down, then using the same seed
		134	nodes for all nodes ensures that eventually the subnets get merged again.
		135
		136	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
		138	seed node that blocks for long periods will slow down everybody else.
		139
		140	For small networks, it's best if every node uses the same set of seed
		141	nodes. For large networks, it can be useful to specify "regional" seed
		142	nodes for most nodes in an area, and use all seed nodes as seed nodes for
		143	each other. What's important is that all seed nodes connections form a
		144	complete graph, so that the network cannot split into separate subnets
		145	forever.
		146
		147	Seed nodes are represented by seed IDs.
		148
101	=item seeds - C<host:port>	149	=item seed IDs - C<host:port>
102		150
103	When a node starts, it knows nothing about the network. To teach the node	151	Seed IDs are transport endpoint(s) (usually a hostname/IP address and a
104	about the network it first has to contact some other node within the	152	TCP port) of nodes that should be used as seed nodes.
105	network. This node is called a seed.
106		153
107	Seeds are transport endpoint(s) of as many nodes as one wants. Those nodes	154	=item global nodes
108	are expected to be long-running, and at least one of those should always
109	be available. When nodes run out of connections (e.g. due to a network
110	error), they try to re-establish connections to some seednodes again to
111	join the network.
112		155
113	Apart from being sued for seeding, seednodes are not special in any way -	156	An AEMP network needs a discovery service - nodes need to know how to
114	every public node can be a seednode.	157	connect to other nodes they only know by name. In addition, AEMP offers a
		158	distributed "group database", which maps group names to a list of strings
		159	- for example, to register worker ports.
		160
		161	A network needs at least one global node to work, and allows every node to
		162	be a global node.
		163
		164	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
		166	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
		168	keep connections to seed nodes and global nodes, so makign them the same
		169	reduces overhead).
115		170
116	=back	171	=back
117		172
118	=head1 VARIABLES/FUNCTIONS	173	=head1 VARIABLES/FUNCTIONS
119		174
…		…
121		176
122	=cut	177	=cut
123		178
124	package AnyEvent::MP;	179	package AnyEvent::MP;
125		180
		181	use AnyEvent::MP::Config ();
126	use AnyEvent::MP::Kernel;	182	use AnyEvent::MP::Kernel;
		183	use AnyEvent::MP::Kernel qw(%NODE %PORT %PORT_DATA $UNIQ $RUNIQ $ID);
127		184
128	use common::sense;	185	use common::sense;
129		186
130	use Carp ();	187	use Carp ();
131		188
132	use AE ();	189	use AE ();
		190	use Guard ();
133		191
134	use base "Exporter";	192	use base "Exporter";
135		193
136	our $VERSION = $AnyEvent::MP::Kernel::VERSION;	194	our $VERSION = $AnyEvent::MP::Config::VERSION;
137		195
138	our @EXPORT = qw(	196	our @EXPORT = qw(
139	NODE $NODE *SELF node_of after	197	NODE $NODE *SELF node_of after
140	configure	198	configure
141	snd rcv mon mon_guard kil reg psub spawn	199	snd rcv mon mon_guard kil psub peval spawn cal
142	port	200	port
		201	db_set db_del db_reg
143	);	202	);
144		203
145	our $SELF;	204	our $SELF;
146		205
147	sub _self_die() {	206	sub _self_die() {
…		…
158		217
159	=item $nodeid = node_of $port	218	=item $nodeid = node_of $port
160		219
161	Extracts and returns the node ID from a port ID or a node ID.	220	Extracts and returns the node ID from a port ID or a node ID.
162		221
		222	=item configure $profile, key => value...
		223
163	=item configure key => value...	224	=item configure key => value...
164		225
165	Before a node can talk to other nodes on the network (i.e. enter	226	Before a node can talk to other nodes on the network (i.e. enter
166	"distributed mode") it has to configure itself - the minimum a node needs	227	"distributed mode") it has to configure itself - the minimum a node needs
167	to know is its own name, and optionally it should know the addresses of	228	to know is its own name, and optionally it should know the addresses of
168	some other nodes in the network to discover other nodes.	229	some other nodes in the network to discover other nodes.
169		230
170	This function configures a node - it must be called exactly once (or	231	This function configures a node - it must be called exactly once (or
171	never) before calling other AnyEvent::MP functions.	232	never) before calling other AnyEvent::MP functions.
172		233
		234	The key/value pairs are basically the same ones as documented for the
		235	F<aemp> command line utility (sans the set/del prefix), with these additions:
		236
		237	=over 4
		238
		239	=item norc => $boolean (default false)
		240
		241	If true, then the rc file (e.g. F<~/.perl-anyevent-mp>) will I<not>
		242	be consulted - all configuraiton options must be specified in the
		243	C<configure> call.
		244
		245	=item force => $boolean (default false)
		246
		247	IF true, then the values specified in the C<configure> will take
		248	precedence over any values configured via the rc file. The default is for
		249	the rc file to override any options specified in the program.
		250
		251	=item secure => $pass->($nodeid)
		252
		253	In addition to specifying a boolean, you can specify a code reference that
		254	is called for every remote execution attempt - the execution request is
		255	granted iff the callback returns a true value.
		256
		257	See F<semp setsecure> for more info.
		258
		259	=back
		260
173	=over 4	261	=over 4
174		262
175	=item step 1, gathering configuration from profiles	263	=item step 1, gathering configuration from profiles
176		264
177	The function first looks up a profile in the aemp configuration (see the	265	The function first looks up a profile in the aemp configuration (see the
178	L<aemp> commandline utility). The profile name can be specified via the	266	L<aemp> commandline utility). The profile name can be specified via the
179	named C<profile> parameter. If it is missing, then the nodename (F<uname	267	named C<profile> parameter or can simply be the first parameter). If it is
180	-n>) will be used as profile name.	268	missing, then the nodename (F<uname -n>) will be used as profile name.
181		269
182	The profile data is then gathered as follows:	270	The profile data is then gathered as follows:
183		271
184	First, all remaining key => value pairs (all of which are conveniently	272	First, all remaining key => value pairs (all of which are conveniently
185	undocumented at the moment) will be interpreted as configuration	273	undocumented at the moment) will be interpreted as configuration
…		…
190	That means that the values specified in the profile have highest priority	278	That means that the values specified in the profile have highest priority
191	and the values specified directly via C<configure> have lowest priority,	279	and the values specified directly via C<configure> have lowest priority,
192	and can only be used to specify defaults.	280	and can only be used to specify defaults.
193		281
194	If the profile specifies a node ID, then this will become the node ID of	282	If the profile specifies a node ID, then this will become the node ID of
195	this process. If not, then the profile name will be used as node ID. The	283	this process. If not, then the profile name will be used as node ID, with
196	special node ID of C<anon/> will be replaced by a random node ID.	284	a unique randoms tring (C</%u>) appended.
		285
		286	The node ID can contain some C<%> sequences that are expanded: C<%n>
		287	is expanded to the local nodename, C<%u> is replaced by a random
		288	strign to make the node unique. For example, the F<aemp> commandline
		289	utility uses C<aemp/%n/%u> as nodename, which might expand to
		290	C<aemp/cerebro/ZQDGSIkRhEZQDGSIkRhE>.
197		291
198	=item step 2, bind listener sockets	292	=item step 2, bind listener sockets
199		293
200	The next step is to look up the binds in the profile, followed by binding	294	The next step is to look up the binds in the profile, followed by binding
201	aemp protocol listeners on all binds specified (it is possible and valid	295	aemp protocol listeners on all binds specified (it is possible and valid
…		…
207	used, meaning the node will bind on a dynamically-assigned port on every	301	used, meaning the node will bind on a dynamically-assigned port on every
208	local IP address it finds.	302	local IP address it finds.
209		303
210	=item step 3, connect to seed nodes	304	=item step 3, connect to seed nodes
211		305
212	As the last step, the seeds list from the profile is passed to the	306	As the last step, the seed ID list from the profile is passed to the
213	L<AnyEvent::MP::Global> module, which will then use it to keep	307	L<AnyEvent::MP::Global> module, which will then use it to keep
214	connectivity with at least one node at any point in time.	308	connectivity with at least one node at any point in time.
215		309
216	=back	310	=back
217		311
218	Example: become a distributed node using the locla node name as profile.	312	Example: become a distributed node using the local node name as profile.
219	This should be the most common form of invocation for "daemon"-type nodes.	313	This should be the most common form of invocation for "daemon"-type nodes.
220		314
221	configure	315	configure
222		316
223	Example: become an anonymous node. This form is often used for commandline	317	Example: become a semi-anonymous node. This form is often used for
224	clients.	318	commandline clients.
225		319
226	configure nodeid => "anon/";	320	configure nodeid => "myscript/%n/%u";
227		321
228	Example: configure a node using a profile called seed, which si suitable	322	Example: configure a node using a profile called seed, which is suitable
229	for a seed node as it binds on all local addresses on a fixed port (4040,	323	for a seed node as it binds on all local addresses on a fixed port (4040,
230	customary for aemp).	324	customary for aemp).
231		325
232	# use the aemp commandline utility	326	# use the aemp commandline utility
233	# aemp profile seed nodeid anon/ binds '*:4040'	327	# aemp profile seed binds '*:4040'
234		328
235	# then use it	329	# then use it
236	configure profile => "seed";	330	configure profile => "seed";
237		331
238	# or simply use aemp from the shell again:	332	# or simply use aemp from the shell again:
…		…
308	sub _kilme {	402	sub _kilme {
309	die "received message on port without callback";	403	die "received message on port without callback";
310	}	404	}
311		405
312	sub port(;&) {	406	sub port(;&) {
313	my $id = "$UNIQ." . $ID++;	407	my $id = $UNIQ . ++$ID;
314	my $port = "$NODE#$id";	408	my $port = "$NODE#$id";
315		409
316	rcv $port, shift \|\| \&_kilme;	410	rcv $port, shift \|\| \&_kilme;
317		411
318	$port	412	$port
…		…
357	msg1 => sub { ... },	451	msg1 => sub { ... },
358	...	452	...
359	;	453	;
360		454
361	Example: temporarily register a rcv callback for a tag matching some port	455	Example: temporarily register a rcv callback for a tag matching some port
362	(e.g. for a rpc reply) and unregister it after a message was received.	456	(e.g. for an rpc reply) and unregister it after a message was received.
363		457
364	rcv $port, $otherport => sub {	458	rcv $port, $otherport => sub {
365	my @reply = @_;	459	my @reply = @_;
366		460
367	rcv $SELF, $otherport;	461	rcv $SELF, $otherport;
…		…
380	if (ref $_[0]) {	474	if (ref $_[0]) {
381	if (my $self = $PORT_DATA{$portid}) {	475	if (my $self = $PORT_DATA{$portid}) {
382	"AnyEvent::MP::Port" eq ref $self	476	"AnyEvent::MP::Port" eq ref $self
383	or Carp::croak "$port: rcv can only be called on message matching ports, caught";	477	or Carp::croak "$port: rcv can only be called on message matching ports, caught";
384		478
385	$self->[2] = shift;	479	$self->[0] = shift;
386	} else {	480	} else {
387	my $cb = shift;	481	my $cb = shift;
388	$PORT{$portid} = sub {	482	$PORT{$portid} = sub {
389	local $SELF = $port;	483	local $SELF = $port;
390	eval { &$cb }; _self_die if $@;	484	eval { &$cb }; _self_die if $@;
391	};	485	};
392	}	486	}
393	} elsif (defined $_[0]) {	487	} elsif (defined $_[0]) {
394	my $self = $PORT_DATA{$portid} \|\|= do {	488	my $self = $PORT_DATA{$portid} \|\|= do {
395	my $self = bless [$PORT{$port} \|\| sub { }, { }, $port], "AnyEvent::MP::Port";	489	my $self = bless [$PORT{$portid} \|\| sub { }, { }, $port], "AnyEvent::MP::Port";
396		490
397	$PORT{$portid} = sub {	491	$PORT{$portid} = sub {
398	local $SELF = $port;	492	local $SELF = $port;
399		493
400	if (my $cb = $self->[1]{$_[0]}) {	494	if (my $cb = $self->[1]{$_[0]}) {
…		…
422	}	516	}
423		517
424	$port	518	$port
425	}	519	}
426		520
		521	=item peval $port, $coderef[, @args]
		522
		523	Evaluates the given C<$codref> within the contetx of C<$port>, that is,
		524	when the code throews an exception the C<$port> will be killed.
		525
		526	Any remaining args will be passed to the callback. Any return values will
		527	be returned to the caller.
		528
		529	This is useful when you temporarily want to execute code in the context of
		530	a port.
		531
		532	Example: create a port and run some initialisation code in it's context.
		533
		534	my $port = port { ... };
		535
		536	peval $port, sub {
		537	init
		538	or die "unable to init";
		539	};
		540
		541	=cut
		542
		543	sub peval($$) {
		544	local $SELF = shift;
		545	my $cb = shift;
		546
		547	if (wantarray) {
		548	my @res = eval { &$cb };
		549	_self_die if $@;
		550	@res
		551	} else {
		552	my $res = eval { &$cb };
		553	_self_die if $@;
		554	$res
		555	}
		556	}
		557
427	=item $closure = psub { BLOCK }	558	=item $closure = psub { BLOCK }
428		559
429	Remembers C<$SELF> and creates a closure out of the BLOCK. When the	560	Remembers C<$SELF> and creates a closure out of the BLOCK. When the
430	closure is executed, sets up the environment in the same way as in C<rcv>	561	closure is executed, sets up the environment in the same way as in C<rcv>
431	callbacks, i.e. runtime errors will cause the port to get C<kil>ed.	562	callbacks, i.e. runtime errors will cause the port to get C<kil>ed.
		563
		564	The effect is basically as if it returned C<< sub { peval $SELF, sub {
		565	BLOCK }, @_ } >>.
432		566
433	This is useful when you register callbacks from C<rcv> callbacks:	567	This is useful when you register callbacks from C<rcv> callbacks:
434		568
435	rcv delayed_reply => sub {	569	rcv delayed_reply => sub {
436	my ($delay, @reply) = @_;	570	my ($delay, @reply) = @_;
…		…
472		606
473	Monitor the given port and do something when the port is killed or	607	Monitor the given port and do something when the port is killed or
474	messages to it were lost, and optionally return a guard that can be used	608	messages to it were lost, and optionally return a guard that can be used
475	to stop monitoring again.	609	to stop monitoring again.
476		610
		611	In the first form (callback), the callback is simply called with any
		612	number of C<@reason> elements (no @reason means that the port was deleted
		613	"normally"). Note also that I<< the callback B<must> never die >>, so use
		614	C<eval> if unsure.
		615
		616	In the second form (another port given), the other port (C<$rcvport>)
		617	will be C<kil>'ed with C<@reason>, if a @reason was specified, i.e. on
		618	"normal" kils nothing happens, while under all other conditions, the other
		619	port is killed with the same reason.
		620
		621	The third form (kill self) is the same as the second form, except that
		622	C<$rvport> defaults to C<$SELF>.
		623
		624	In the last form (message), a message of the form C<@msg, @reason> will be
		625	C<snd>.
		626
		627	Monitoring-actions are one-shot: once messages are lost (and a monitoring
		628	alert was raised), they are removed and will not trigger again.
		629
		630	As a rule of thumb, monitoring requests should always monitor a port from
		631	a local port (or callback). The reason is that kill messages might get
		632	lost, just like any other message. Another less obvious reason is that
		633	even monitoring requests can get lost (for example, when the connection
		634	to the other node goes down permanently). When monitoring a port locally
		635	these problems do not exist.
		636
477	C<mon> effectively guarantees that, in the absence of hardware failures,	637	C<mon> effectively guarantees that, in the absence of hardware failures,
478	after starting the monitor, either all messages sent to the port will	638	after starting the monitor, either all messages sent to the port will
479	arrive, or the monitoring action will be invoked after possible message	639	arrive, or the monitoring action will be invoked after possible message
480	loss has been detected. No messages will be lost "in between" (after	640	loss has been detected. No messages will be lost "in between" (after
481	the first lost message no further messages will be received by the	641	the first lost message no further messages will be received by the
482	port). After the monitoring action was invoked, further messages might get	642	port). After the monitoring action was invoked, further messages might get
483	delivered again.	643	delivered again.
484		644
485	Note that monitoring-actions are one-shot: once messages are lost (and a	645	Inter-host-connection timeouts and monitoring depend on the transport
486	monitoring alert was raised), they are removed and will not trigger again.	646	used. The only transport currently implemented is TCP, and AnyEvent::MP
		647	relies on TCP to detect node-downs (this can take 10-15 minutes on a
		648	non-idle connection, and usually around two hours for idle connections).
487		649
488	In the first form (callback), the callback is simply called with any	650	This means that monitoring is good for program errors and cleaning up
489	number of C<@reason> elements (no @reason means that the port was deleted	651	stuff eventually, but they are no replacement for a timeout when you need
490	"normally"). Note also that I<< the callback B<must> never die >>, so use	652	to ensure some maximum latency.
491	C<eval> if unsure.
492
493	In the second form (another port given), the other port (C<$rcvport>)
494	will be C<kil>'ed with C<@reason>, if a @reason was specified, i.e. on
495	"normal" kils nothing happens, while under all other conditions, the other
496	port is killed with the same reason.
497
498	The third form (kill self) is the same as the second form, except that
499	C<$rvport> defaults to C<$SELF>.
500
501	In the last form (message), a message of the form C<@msg, @reason> will be
502	C<snd>.
503
504	As a rule of thumb, monitoring requests should always monitor a port from
505	a local port (or callback). The reason is that kill messages might get
506	lost, just like any other message. Another less obvious reason is that
507	even monitoring requests can get lost (for example, when the connection
508	to the other node goes down permanently). When monitoring a port locally
509	these problems do not exist.
510		653
511	Example: call a given callback when C<$port> is killed.	654	Example: call a given callback when C<$port> is killed.
512		655
513	mon $port, sub { warn "port died because of <@_>\n" };	656	mon $port, sub { warn "port died because of <@_>\n" };
514		657
…		…
542	}	685	}
543		686
544	$node->monitor ($port, $cb);	687	$node->monitor ($port, $cb);
545		688
546	defined wantarray	689	defined wantarray
547	and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }	690	and ($cb += 0, Guard::guard { $node->unmonitor ($port, $cb) })
548	}	691	}
549		692
550	=item $guard = mon_guard $port, $ref, $ref...	693	=item $guard = mon_guard $port, $ref, $ref...
551		694
552	Monitors the given C<$port> and keeps the passed references. When the port	695	Monitors the given C<$port> and keeps the passed references. When the port
…		…
575		718
576	=item kil $port[, @reason]	719	=item kil $port[, @reason]
577		720
578	Kill the specified port with the given C<@reason>.	721	Kill the specified port with the given C<@reason>.
579		722
580	If no C<@reason> is specified, then the port is killed "normally" (ports	723	If no C<@reason> is specified, then the port is killed "normally" -
581	monitoring other ports will not necessarily die because a port dies	724	monitor callback will be invoked, but the kil will not cause linked ports
582	"normally").	725	(C<mon $mport, $lport> form) to get killed.
583		726
584	Otherwise, linked ports get killed with the same reason (second form of	727	If a C<@reason> is specified, then linked ports (C<mon $mport, $lport>
585	C<mon>, see above).	728	form) get killed with the same reason.
586		729
587	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks	730	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
588	will be reported as reason C<< die => $@ >>.	731	will be reported as reason C<< die => $@ >>.
589		732
590	Transport/communication errors are reported as C<< transport_error =>	733	Transport/communication errors are reported as C<< transport_error =>
…		…
609	the package, then the package above the package and so on (e.g.	752	the package, then the package above the package and so on (e.g.
610	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function	753	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
611	exists or it runs out of package names.	754	exists or it runs out of package names.
612		755
613	The init function is then called with the newly-created port as context	756	The init function is then called with the newly-created port as context
614	object (C<$SELF>) and the C<@initdata> values as arguments.	757	object (C<$SELF>) and the C<@initdata> values as arguments. It I<must>
		758	call one of the C<rcv> functions to set callbacks on C<$SELF>, otherwise
		759	the port might not get created.
615		760
616	A common idiom is to pass a local port, immediately monitor the spawned	761	A common idiom is to pass a local port, immediately monitor the spawned
617	port, and in the remote init function, immediately monitor the passed	762	port, and in the remote init function, immediately monitor the passed
618	local port. This two-way monitoring ensures that both ports get cleaned up	763	local port. This two-way monitoring ensures that both ports get cleaned up
619	when there is a problem.	764	when there is a problem.
620		765
		766	C<spawn> guarantees that the C<$initfunc> has no visible effects on the
		767	caller before C<spawn> returns (by delaying invocation when spawn is
		768	called for the local node).
		769
621	Example: spawn a chat server port on C<$othernode>.	770	Example: spawn a chat server port on C<$othernode>.
622		771
623	# this node, executed from within a port context:	772	# this node, executed from within a port context:
624	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;	773	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;
625	mon $server;	774	mon $server;
…		…
639		788
640	sub _spawn {	789	sub _spawn {
641	my $port = shift;	790	my $port = shift;
642	my $init = shift;	791	my $init = shift;
643		792
		793	# rcv will create the actual port
644	local $SELF = "$NODE#$port";	794	local $SELF = "$NODE#$port";
645	eval {	795	eval {
646	&{ load_func $init }	796	&{ load_func $init }
647	};	797	};
648	_self_die if $@;	798	_self_die if $@;
649	}	799	}
650		800
651	sub spawn(@) {	801	sub spawn(@) {
652	my ($nodeid, undef) = split /#/, shift, 2;	802	my ($nodeid, undef) = split /#/, shift, 2;
653		803
654	my $id = "$RUNIQ." . $ID++;	804	my $id = $RUNIQ . ++$ID;
655		805
656	$_[0] =~ /::/	806	$_[0] =~ /::/
657	or Carp::croak "spawn init function must be a fully-qualified name, caught";	807	or Carp::croak "spawn init function must be a fully-qualified name, caught";
658		808
659	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;	809	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;
660		810
661	"$nodeid#$id"	811	"$nodeid#$id"
662	}	812	}
		813
663		814
664	=item after $timeout, @msg	815	=item after $timeout, @msg
665		816
666	=item after $timeout, $callback	817	=item after $timeout, $callback
667		818
…		…
683	? $action[0]()	834	? $action[0]()
684	: snd @action;	835	: snd @action;
685	};	836	};
686	}	837	}
687		838
		839	=item cal $port, @msg, $callback[, $timeout]
		840
		841	A simple form of RPC - sends a message to the given C<$port> with the
		842	given contents (C<@msg>), but adds a reply port to the message.
		843
		844	The reply port is created temporarily just for the purpose of receiving
		845	the reply, and will be C<kil>ed when no longer needed.
		846
		847	A reply message sent to the port is passed to the C<$callback> as-is.
		848
		849	If an optional time-out (in seconds) is given and it is not C<undef>,
		850	then the callback will be called without any arguments after the time-out
		851	elapsed and the port is C<kil>ed.
		852
		853	If no time-out is given (or it is C<undef>), then the local port will
		854	monitor the remote port instead, so it eventually gets cleaned-up.
		855
		856	Currently this function returns the temporary port, but this "feature"
		857	might go in future versions unless you can make a convincing case that
		858	this is indeed useful for something.
		859
		860	=cut
		861
		862	sub cal(@) {
		863	my $timeout = ref $_[-1] ? undef : pop;
		864	my $cb = pop;
		865
		866	my $port = port {
		867	undef $timeout;
		868	kil $SELF;
		869	&$cb;
		870	};
		871
		872	if (defined $timeout) {
		873	$timeout = AE::timer $timeout, 0, sub {
		874	undef $timeout;
		875	kil $port;
		876	$cb->();
		877	};
		878	} else {
		879	mon $_[0], sub {
		880	kil $port;
		881	$cb->();
		882	};
		883	}
		884
		885	push @_, $port;
		886	&snd;
		887
		888	$port
		889	}
		890
		891	=back
		892
		893	=head1 DISTRIBUTED DATABASE
		894
		895	AnyEvent::MP comes with a simple distributed database. The database will
		896	be mirrored asynchronously at all global nodes. Other nodes bind to one of
		897	the global nodes for their needs.
		898
		899	The database consists of a two-level hash - a hash contains a hash which
		900	contains values.
		901
		902	The top level hash key is called "family", and the second-level hash key
		903	is called "subkey" or simply "key".
		904
		905	The family must be alphanumeric, i.e. start with a letter and consist
		906	of letters, digits, underscores and colons (C<[A-Za-z][A-Za-z0-9_:]*>,
		907	pretty much like Perl module names.
		908
		909	As the family namespace is global, it is recommended to prefix family names
		910	with the name of the application or module using it.
		911
		912	The subkeys must be non-empty strings, with no further restrictions.
		913
		914	The values should preferably be strings, but other perl scalars should
		915	work as well (such as undef, arrays and hashes).
		916
		917	Every database entry is owned by one node - adding the same family/subkey
		918	combination on multiple nodes will not cause discomfort for AnyEvent::MP,
		919	but the result might be nondeterministic, i.e. the key might have
		920	different values on different nodes.
		921
		922	Different subkeys in the same family can be owned by different nodes
		923	without problems, and in fact, this is the common method to create worker
		924	pools. For example, a worker port for image scaling might do this:
		925
		926	db_set my_image_scalers => $port;
		927
		928	And clients looking for an image scaler will want to get the
		929	C<my_image_scalers> keys:
		930
		931	db_keys "my_image_scalers" => 60 => sub {
		932	#d##TODO#
		933
		934	=over
		935
		936	=item db_set $family => $subkey [=> $value]
		937
		938	Sets (or replaces) a key to the database - if C<$value> is omitted,
		939	C<undef> is used instead.
		940
		941	=item db_del $family => $subkey
		942
		943	Deletes a key from the database.
		944
		945	=item $guard = db_reg $family => $subkey [=> $value]
		946
		947	Sets the key on the database and returns a guard. When the guard is
		948	destroyed, the key is deleted from the database. If C<$value> is missing,
		949	then C<undef> is used.
		950
		951	=cut
		952
688	=back	953	=back
689		954
690	=head1 AnyEvent::MP vs. Distributed Erlang	955	=head1 AnyEvent::MP vs. Distributed Erlang
691		956
692	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node	957	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
693	== aemp node, Erlang process == aemp port), so many of the documents and	958	== aemp node, Erlang process == aemp port), so many of the documents and
694	programming techniques employed by Erlang apply to AnyEvent::MP. Here is a	959	programming techniques employed by Erlang apply to AnyEvent::MP. Here is a
695	sample:	960	sample:
696		961
697	http://www.Erlang.se/doc/programming_rules.shtml	962	http://www.erlang.se/doc/programming_rules.shtml
698	http://Erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4	963	http://erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4
699	http://Erlang.org/download/Erlang-book-part1.pdf # chapters 5 and 6	964	http://erlang.org/download/erlang-book-part1.pdf # chapters 5 and 6
700	http://Erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5	965	http://erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5
701		966
702	Despite the similarities, there are also some important differences:	967	Despite the similarities, there are also some important differences:
703		968
704	=over 4	969	=over 4
705		970
706	=item * Node IDs are arbitrary strings in AEMP.	971	=item * Node IDs are arbitrary strings in AEMP.
707		972
708	Erlang relies on special naming and DNS to work everywhere in the same	973	Erlang relies on special naming and DNS to work everywhere in the same
709	way. AEMP relies on each node somehow knowing its own address(es) (e.g. by	974	way. AEMP relies on each node somehow knowing its own address(es) (e.g. by
710	configuration or DNS), but will otherwise discover other odes itself.	975	configuration or DNS), and possibly the addresses of some seed nodes, but
		976	will otherwise discover other nodes (and their IDs) itself.
711		977
712	=item * Erlang has a "remote ports are like local ports" philosophy, AEMP	978	=item * Erlang has a "remote ports are like local ports" philosophy, AEMP
713	uses "local ports are like remote ports".	979	uses "local ports are like remote ports".
714		980
715	The failure modes for local ports are quite different (runtime errors	981	The failure modes for local ports are quite different (runtime errors
…		…
724	ports being the special case/exception, where transport errors cannot	990	ports being the special case/exception, where transport errors cannot
725	occur.	991	occur.
726		992
727	=item * Erlang uses processes and a mailbox, AEMP does not queue.	993	=item * Erlang uses processes and a mailbox, AEMP does not queue.
728		994
729	Erlang uses processes that selectively receive messages, and therefore	995	Erlang uses processes that selectively receive messages out of order, and
730	needs a queue. AEMP is event based, queuing messages would serve no	996	therefore needs a queue. AEMP is event based, queuing messages would serve
731	useful purpose. For the same reason the pattern-matching abilities of	997	no useful purpose. For the same reason the pattern-matching abilities
732	AnyEvent::MP are more limited, as there is little need to be able to	998	of AnyEvent::MP are more limited, as there is little need to be able to
733	filter messages without dequeuing them.	999	filter messages without dequeuing them.
734		1000
735	(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).	1001	This is not a philosophical difference, but simply stems from AnyEvent::MP
		1002	being event-based, while Erlang is process-based.
		1003
		1004	You cna have a look at L<Coro::MP> for a more Erlang-like process model on
		1005	top of AEMP and Coro threads.
736		1006
737	=item * Erlang sends are synchronous, AEMP sends are asynchronous.	1007	=item * Erlang sends are synchronous, AEMP sends are asynchronous.
738		1008
739	Sending messages in Erlang is synchronous and blocks the process (and	1009	Sending messages in Erlang is synchronous and blocks the process until
		1010	a conenction has been established and the message sent (and so does not
740	so does not need a queue that can overflow). AEMP sends are immediate,	1011	need a queue that can overflow). AEMP sends return immediately, connection
741	connection establishment is handled in the background.	1012	establishment is handled in the background.
742		1013
743	=item * Erlang suffers from silent message loss, AEMP does not.	1014	=item * Erlang suffers from silent message loss, AEMP does not.
744		1015
745	Erlang makes few guarantees on messages delivery - messages can get lost	1016	Erlang implements few guarantees on messages delivery - messages can get
746	without any of the processes realising it (i.e. you send messages a, b,	1017	lost without any of the processes realising it (i.e. you send messages a,
747	and c, and the other side only receives messages a and c).	1018	b, and c, and the other side only receives messages a and c).
748		1019
749	AEMP guarantees correct ordering, and the guarantee that after one message	1020	AEMP guarantees (modulo hardware errors) correct ordering, and the
750	is lost, all following ones sent to the same port are lost as well, until	1021	guarantee that after one message is lost, all following ones sent to the
751	monitoring raises an error, so there are no silent "holes" in the message	1022	same port are lost as well, until monitoring raises an error, so there are
752	sequence.	1023	no silent "holes" in the message sequence.
		1024
		1025	If you want your software to be very reliable, you have to cope with
		1026	corrupted and even out-of-order messages in both Erlang and AEMP. AEMP
		1027	simply tries to work better in common error cases, such as when a network
		1028	link goes down.
753		1029
754	=item * Erlang can send messages to the wrong port, AEMP does not.	1030	=item * Erlang can send messages to the wrong port, AEMP does not.
755		1031
756	In Erlang it is quite likely that a node that restarts reuses a process ID	1032	In Erlang it is quite likely that a node that restarts reuses an Erlang
757	known to other nodes for a completely different process, causing messages	1033	process ID known to other nodes for a completely different process,
758	destined for that process to end up in an unrelated process.	1034	causing messages destined for that process to end up in an unrelated
		1035	process.
759		1036
760	AEMP never reuses port IDs, so old messages or old port IDs floating	1037	AEMP does not reuse port IDs, so old messages or old port IDs floating
761	around in the network will not be sent to an unrelated port.	1038	around in the network will not be sent to an unrelated port.
762		1039
763	=item * Erlang uses unprotected connections, AEMP uses secure	1040	=item * Erlang uses unprotected connections, AEMP uses secure
764	authentication and can use TLS.	1041	authentication and can use TLS.
765		1042
…		…
768		1045
769	=item * The AEMP protocol is optimised for both text-based and binary	1046	=item * The AEMP protocol is optimised for both text-based and binary
770	communications.	1047	communications.
771		1048
772	The AEMP protocol, unlike the Erlang protocol, supports both programming	1049	The AEMP protocol, unlike the Erlang protocol, supports both programming
773	language independent text-only protocols (good for debugging) and binary,	1050	language independent text-only protocols (good for debugging), and binary,
774	language-specific serialisers (e.g. Storable). By default, unless TLS is	1051	language-specific serialisers (e.g. Storable). By default, unless TLS is
775	used, the protocol is actually completely text-based.	1052	used, the protocol is actually completely text-based.
776		1053
777	It has also been carefully designed to be implementable in other languages	1054	It has also been carefully designed to be implementable in other languages
778	with a minimum of work while gracefully degrading functionality to make the	1055	with a minimum of work while gracefully degrading functionality to make the
779	protocol simple.	1056	protocol simple.
780		1057
781	=item * AEMP has more flexible monitoring options than Erlang.	1058	=item * AEMP has more flexible monitoring options than Erlang.
782		1059
783	In Erlang, you can chose to receive I<all> exit signals as messages	1060	In Erlang, you can chose to receive I<all> exit signals as messages or
784	or I<none>, there is no in-between, so monitoring single processes is	1061	I<none>, there is no in-between, so monitoring single Erlang processes is
785	difficult to implement. Monitoring in AEMP is more flexible than in	1062	difficult to implement.
786	Erlang, as one can choose between automatic kill, exit message or callback	1063
787	on a per-process basis.	1064	Monitoring in AEMP is more flexible than in Erlang, as one can choose
		1065	between automatic kill, exit message or callback on a per-port basis.
788		1066
789	=item * Erlang tries to hide remote/local connections, AEMP does not.	1067	=item * Erlang tries to hide remote/local connections, AEMP does not.
790		1068
791	Monitoring in Erlang is not an indicator of process death/crashes, in the	1069	Monitoring in Erlang is not an indicator of process death/crashes, in the
792	same way as linking is (except linking is unreliable in Erlang).	1070	same way as linking is (except linking is unreliable in Erlang).
…		…
814	overhead, as well as having to keep a proxy object everywhere.	1092	overhead, as well as having to keep a proxy object everywhere.
815		1093
816	Strings can easily be printed, easily serialised etc. and need no special	1094	Strings can easily be printed, easily serialised etc. and need no special
817	procedures to be "valid".	1095	procedures to be "valid".
818		1096
819	And as a result, a miniport consists of a single closure stored in a	1097	And as a result, a port with just a default receiver consists of a single
820	global hash - it can't become much cheaper.	1098	code reference stored in a global hash - it can't become much cheaper.
821		1099
822	=item Why favour JSON, why not a real serialising format such as Storable?	1100	=item Why favour JSON, why not a real serialising format such as Storable?
823		1101
824	In fact, any AnyEvent::MP node will happily accept Storable as framing	1102	In fact, any AnyEvent::MP node will happily accept Storable as framing
825	format, but currently there is no way to make a node use Storable by	1103	format, but currently there is no way to make a node use Storable by
…		…
841		1119
842	L<AnyEvent::MP::Intro> - a gentle introduction.	1120	L<AnyEvent::MP::Intro> - a gentle introduction.
843		1121
844	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.	1122	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.
845		1123
846	L<AnyEvent::MP::Global> - network maintainance and port groups, to find	1124	L<AnyEvent::MP::Global> - network maintenance and port groups, to find
847	your applications.	1125	your applications.
		1126
		1127	L<AnyEvent::MP::DataConn> - establish data connections between nodes.
		1128
		1129	L<AnyEvent::MP::LogCatcher> - simple service to display log messages from
		1130	all nodes.
848		1131
849	L<AnyEvent>.	1132	L<AnyEvent>.
850		1133
851	=head1 AUTHOR	1134	=head1 AUTHOR
852		1135

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.77 by elmex, Thu Sep 3 07:57:30 2009 UTC vs. Revision 1.127 by root, Sat Mar 3 20:35:10 2012 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.77 by elmex, Thu Sep 3 07:57:30 2009 UTC vs.
Revision 1.127 by root, Sat Mar 3 20:35:10 2012 UTC