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

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

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.75 by root, Mon Aug 31 13:18:06 2009 UTC vs. Revision 1.126 by root, Sat Mar 3 19:43:41 2012 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.75 by root, Mon Aug 31 13:18:06 2009 UTC vs.
Revision 1.126 by root, Sat Mar 3 19:43:41 2012 UTC