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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.52 by root, Fri Aug 14 15:13:20 2009 UTC vs.
Revision 1.87 by root, Fri Sep 11 02:32:23 2009 UTC

…		…
4		4
5	=head1 SYNOPSIS	5	=head1 SYNOPSIS
6		6
7	use AnyEvent::MP;	7	use AnyEvent::MP;
8		8
9	$NODE # contains this node's noderef	9	$NODE # contains this node's node ID
10	NODE # returns this node's noderef	10	NODE # returns this node's node ID
11	NODE $port # returns the noderef of the port
12		11
13	$SELF # receiving/own port id in rcv callbacks	12	$SELF # receiving/own port id in rcv callbacks
14		13
15	# initialise the node so it can send/receive messages	14	# initialise the node so it can send/receive messages
16	initialise_node; # -OR-	15	configure;
17	initialise_node "localhost:4040"; # -OR-
18	initialise_node "slave/", "localhost:4040"
19		16
20	# ports are message endpoints	17	# ports are message destinations
21		18
22	# sending messages	19	# sending messages
23	snd $port, type => data...;	20	snd $port, type => data...;
24	snd $port, @msg;	21	snd $port, @msg;
25	snd @msg_with_first_element_being_a_port;	22	snd @msg_with_first_element_being_a_port;
26		23
27	# creating/using ports, the simple way	24	# creating/using ports, the simple way
28	my $somple_port = port { my @msg = @_; 0 };	25	my $simple_port = port { my @msg = @_ };
29		26
30	# creating/using ports, tagged message matching	27	# creating/using ports, tagged message matching
31	my $port = port;	28	my $port = port;
32	rcv $port, ping => sub { snd $_[0], "pong"; 0 };	29	rcv $port, ping => sub { snd $_[0], "pong" };
33	rcv $port, pong => sub { warn "pong received\n"; 0 };	30	rcv $port, pong => sub { warn "pong received\n" };
34		31
35	# create a port on another node	32	# create a port on another node
36	my $port = spawn $node, $initfunc, @initdata;	33	my $port = spawn $node, $initfunc, @initdata;
37		34
38	# monitoring	35	# monitoring
…		…
40	mon $port, $otherport # kill otherport on abnormal death	37	mon $port, $otherport # kill otherport on abnormal death
41	mon $port, $otherport, @msg # send message on death	38	mon $port, $otherport, @msg # send message on death
42		39
43	=head1 CURRENT STATUS	40	=head1 CURRENT STATUS
44		41
		42	bin/aemp - stable.
45	AnyEvent::MP - stable API, should work	43	AnyEvent::MP - stable API, should work.
46	AnyEvent::MP::Intro - outdated	44	AnyEvent::MP::Intro - explains most concepts.
47	AnyEvent::MP::Kernel - WIP
48	AnyEvent::MP::Transport - mostly stable	45	AnyEvent::MP::Kernel - mostly stable.
		46	AnyEvent::MP::Global - stable but incomplete, protocol not yet final.
49		47
50	stay tuned.	48	stay tuned.
51		49
52	=head1 DESCRIPTION	50	=head1 DESCRIPTION
53		51
54	This module (-family) implements a simple message passing framework.	52	This module (-family) implements a simple message passing framework.
55		53
56	Despite its simplicity, you can securely message other processes running	54	Despite its simplicity, you can securely message other processes running
57	on the same or other hosts.	55	on the same or other hosts, and you can supervise entities remotely.
58		56
59	For an introduction to this module family, see the L<AnyEvent::MP::Intro>	57	For an introduction to this module family, see the L<AnyEvent::MP::Intro>
60	manual page.	58	manual page and the examples under F<eg/>.
61
62	At the moment, this module family is severly broken and underdocumented,
63	so do not use. This was uploaded mainly to reserve the CPAN namespace -
64	stay tuned!
65		59
66	=head1 CONCEPTS	60	=head1 CONCEPTS
67		61
68	=over 4	62	=over 4
69		63
70	=item port	64	=item port
71		65
72	A port is something you can send messages to (with the C<snd> function).	66	Not to be confused with a TCP port, a "port" is something you can send
		67	messages to (with the C<snd> function).
73		68
74	Some ports allow you to register C<rcv> handlers that can match specific	69	Ports allow you to register C<rcv> handlers that can match all or just
75	messages. All C<rcv> handlers will receive messages they match, messages	70	some messages. Messages send to ports will not be queued, regardless of
76	will not be queued.	71	anything was listening for them or not.
77		72
78	=item port id - C<noderef#portname>	73	=item port ID - C<nodeid#portname>
79		74
80	A port id is normaly the concatenation of a noderef, a hash-mark (C<#>) as	75	A port ID is the concatenation of a node ID, a hash-mark (C<#>) as
81	separator, and a port name (a printable string of unspecified format). An	76	separator, and a port name (a printable string of unspecified format).
82	exception is the the node port, whose ID is identical to its node
83	reference.
84		77
85	=item node	78	=item node
86		79
87	A node is a single process containing at least one port - the node	80	A node is a single process containing at least one port - the node port,
88	port. You can send messages to node ports to find existing ports or to	81	which enables nodes to manage each other remotely, and to create new
89	create new ports, among other things.	82	ports.
90		83
91	Nodes are either private (single-process only), slaves (connected to a	84	Nodes are either public (have one or more listening ports) or private
92	master node only) or public nodes (connectable from unrelated nodes).	85	(no listening ports). Private nodes cannot talk to other private nodes
		86	currently.
93		87
94	=item noderef - C<host:port,host:port...>, C<id@noderef>, C<id>	88	=item node ID - C<[A-Z_][a-zA-Z0-9_\-.:]*>
95		89
96	A node reference is a string that either simply identifies the node (for	90	A node ID is a string that uniquely identifies the node within a
97	private and slave nodes), or contains a recipe on how to reach a given	91	network. Depending on the configuration used, node IDs can look like a
98	node (for public nodes).	92	hostname, a hostname and a port, or a random string. AnyEvent::MP itself
		93	doesn't interpret node IDs in any way.
99		94
100	This recipe is simply a comma-separated list of C<address:port> pairs (for	95	=item binds - C<ip:port>
101	TCP/IP, other protocols might look different).
102		96
103	Node references come in two flavours: resolved (containing only numerical	97	Nodes can only talk to each other by creating some kind of connection to
104	addresses) or unresolved (where hostnames are used instead of addresses).	98	each other. To do this, nodes should listen on one or more local transport
		99	endpoints - binds. Currently, only standard C<ip:port> specifications can
		100	be used, which specify TCP ports to listen on.
105		101
106	Before using an unresolved node reference in a message you first have to	102	=item seed nodes
107	resolve it.	103
		104	When a node starts, it knows nothing about the network. To teach the node
		105	about the network it first has to contact some other node within the
		106	network. This node is called a seed.
		107
		108	Apart from the fact that other nodes know them as seed nodes and they have
		109	to have fixed listening addresses, seed nodes are perfectly normal nodes -
		110	any node can function as a seed node for others.
		111
		112	In addition to discovering the network, seed nodes are also used to
		113	maintain the network and to connect nodes that otherwise would have
		114	trouble connecting. They form the backbone of an AnyEvent::MP network.
		115
		116	Seed nodes are expected to be long-running, and at least one seed node
		117	should always be available. They should also be relatively responsive - a
		118	seed node that blocks for long periods will slow down everybody else.
		119
		120	=item seeds - C<host:port>
		121
		122	Seeds are transport endpoint(s) (usually a hostname/IP address and a
		123	TCP port) of nodes thta should be used as seed nodes.
		124
		125	The nodes listening on those endpoints are expected to be long-running,
		126	and at least one of those should always be available. When nodes run out
		127	of connections (e.g. due to a network error), they try to re-establish
		128	connections to some seednodes again to join the network.
108		129
109	=back	130	=back
110		131
111	=head1 VARIABLES/FUNCTIONS	132	=head1 VARIABLES/FUNCTIONS
112		133
…		…
127	use base "Exporter";	148	use base "Exporter";
128		149
129	our $VERSION = $AnyEvent::MP::Kernel::VERSION;	150	our $VERSION = $AnyEvent::MP::Kernel::VERSION;
130		151
131	our @EXPORT = qw(	152	our @EXPORT = qw(
132	NODE $NODE *SELF node_of _any_	153	NODE $NODE *SELF node_of after
133	resolve_node initialise_node	154	configure
134	snd rcv mon kil reg psub spawn	155	snd rcv mon mon_guard kil reg psub spawn cal
135	port	156	port
136	);	157	);
137		158
138	our $SELF;	159	our $SELF;
139		160
…		…
143	kil $SELF, die => $msg;	164	kil $SELF, die => $msg;
144	}	165	}
145		166
146	=item $thisnode = NODE / $NODE	167	=item $thisnode = NODE / $NODE
147		168
148	The C<NODE> function returns, and the C<$NODE> variable contains the	169	The C<NODE> function returns, and the C<$NODE> variable contains, the node
149	noderef of the local node. The value is initialised by a call to	170	ID of the node running in the current process. This value is initialised by
150	C<initialise_node>.	171	a call to C<configure>.
151		172
152	=item $noderef = node_of $port	173	=item $nodeid = node_of $port
153		174
154	Extracts and returns the noderef from a port ID or a noderef.	175	Extracts and returns the node ID from a port ID or a node ID.
155		176
156	=item initialise_node $noderef, $seednode, $seednode...	177	=item configure $profile, key => value...
157		178
158	=item initialise_node "slave/", $master, $master...	179	=item configure key => value...
159		180
160	Before a node can talk to other nodes on the network it has to initialise	181	Before a node can talk to other nodes on the network (i.e. enter
161	itself - the minimum a node needs to know is it's own name, and optionally	182	"distributed mode") it has to configure itself - the minimum a node needs
162	it should know the noderefs of some other nodes in the network.	183	to know is its own name, and optionally it should know the addresses of
		184	some other nodes in the network to discover other nodes.
163		185
164	This function initialises a node - it must be called exactly once (or	186	This function configures a node - it must be called exactly once (or
165	never) before calling other AnyEvent::MP functions.	187	never) before calling other AnyEvent::MP functions.
166		188
167	All arguments (optionally except for the first) are noderefs, which can be
168	either resolved or unresolved.
169
170	The first argument will be looked up in the configuration database first
171	(if it is C<undef> then the current nodename will be used instead) to find
172	the relevant configuration profile (see L<aemp>). If none is found then
173	the default configuration is used. The configuration supplies additional
174	seed/master nodes and can override the actual noderef.
175
176	There are two types of networked nodes, public nodes and slave nodes:
177
178	=over 4	189	=over 4
179		190
180	=item public nodes	191	=item step 1, gathering configuration from profiles
181		192
182	For public nodes, C<$noderef> (supplied either directly to	193	The function first looks up a profile in the aemp configuration (see the
183	C<initialise_node> or indirectly via a profile or the nodename) must be a	194	L<aemp> commandline utility). The profile name can be specified via the
184	noderef (possibly unresolved, in which case it will be resolved).	195	named C<profile> parameter or can simply be the first parameter). If it is
		196	missing, then the nodename (F<uname -n>) will be used as profile name.
185		197
186	After resolving, the node will bind itself on all endpoints and try to	198	The profile data is then gathered as follows:
187	connect to all additional C<$seednodes> that are specified. Seednodes are
188	optional and can be used to quickly bootstrap the node into an existing
189	network.
190		199
191	=item slave nodes	200	First, all remaining key => value pairs (all of which are conveniently
		201	undocumented at the moment) will be interpreted as configuration
		202	data. Then they will be overwritten by any values specified in the global
		203	default configuration (see the F<aemp> utility), then the chain of
		204	profiles chosen by the profile name (and any C<parent> attributes).
192		205
193	When the C<$noderef> (either as given or overriden by the config file)	206	That means that the values specified in the profile have highest priority
194	is the special string C<slave/>, then the node will become a slave	207	and the values specified directly via C<configure> have lowest priority,
195	node. Slave nodes cannot be contacted from outside and will route most of	208	and can only be used to specify defaults.
196	their traffic to the master node that they attach to.
197		209
198	At least one additional noderef is required (either by specifying it	210	If the profile specifies a node ID, then this will become the node ID of
199	directly or because it is part of the configuration profile): The node	211	this process. If not, then the profile name will be used as node ID. The
200	will try to connect to all of them and will become a slave attached to the	212	special node ID of C<anon/> will be replaced by a random node ID.
201	first node it can successfully connect to.	213
		214	=item step 2, bind listener sockets
		215
		216	The next step is to look up the binds in the profile, followed by binding
		217	aemp protocol listeners on all binds specified (it is possible and valid
		218	to have no binds, meaning that the node cannot be contacted form the
		219	outside. This means the node cannot talk to other nodes that also have no
		220	binds, but it can still talk to all "normal" nodes).
		221
		222	If the profile does not specify a binds list, then a default of C<*> is
		223	used, meaning the node will bind on a dynamically-assigned port on every
		224	local IP address it finds.
		225
		226	=item step 3, connect to seed nodes
		227
		228	As the last step, the seeds list from the profile is passed to the
		229	L<AnyEvent::MP::Global> module, which will then use it to keep
		230	connectivity with at least one node at any point in time.
202		231
203	=back	232	=back
204		233
205	This function will block until all nodes have been resolved and, for slave	234	Example: become a distributed node using the local node name as profile.
206	nodes, until it has successfully established a connection to a master	235	This should be the most common form of invocation for "daemon"-type nodes.
207	server.
208		236
209	Example: become a public node listening on the guessed noderef, or the one	237	configure
210	specified via C<aemp> for the current node. This should be the most common
211	form of invocation for "daemon"-type nodes.
212		238
213	initialise_node;	239	Example: become an anonymous node. This form is often used for commandline
		240	clients.
214		241
215	Example: become a slave node to any of the the seednodes specified via	242	configure nodeid => "anon/";
216	C<aemp>. This form is often used for commandline clients.
217		243
218	initialise_node "slave/";	244	Example: configure a node using a profile called seed, which si suitable
		245	for a seed node as it binds on all local addresses on a fixed port (4040,
		246	customary for aemp).
219		247
220	Example: become a slave node to any of the specified master servers. This	248	# use the aemp commandline utility
221	form is also often used for commandline clients.	249	# aemp profile seed nodeid anon/ binds '*:4040'
222		250
223	initialise_node "slave/", "master1", "192.168.13.17", "mp.example.net";	251	# then use it
		252	configure profile => "seed";
224		253
225	Example: become a public node, and try to contact some well-known master	254	# or simply use aemp from the shell again:
226	servers to become part of the network.	255	# aemp run profile seed
227		256
228	initialise_node undef, "master1", "master2";	257	# or provide a nicer-to-remember nodeid
229		258	# aemp run profile seed nodeid "$(hostname)"
230	Example: become a public node listening on port C<4041>.
231
232	initialise_node 4041;
233
234	Example: become a public node, only visible on localhost port 4044.
235
236	initialise_node "localhost:4044";
237
238	=item $cv = resolve_node $noderef
239
240	Takes an unresolved node reference that may contain hostnames and
241	abbreviated IDs, resolves all of them and returns a resolved node
242	reference.
243
244	In addition to C<address:port> pairs allowed in resolved noderefs, the
245	following forms are supported:
246
247	=over 4
248
249	=item the empty string
250
251	An empty-string component gets resolved as if the default port (4040) was
252	specified.
253
254	=item naked port numbers (e.g. C<1234>)
255
256	These are resolved by prepending the local nodename and a colon, to be
257	further resolved.
258
259	=item hostnames (e.g. C<localhost:1234>, C<localhost>)
260
261	These are resolved by using AnyEvent::DNS to resolve them, optionally
262	looking up SRV records for the C<aemp=4040> port, if no port was
263	specified.
264
265	=back
266		259
267	=item $SELF	260	=item $SELF
268		261
269	Contains the current port id while executing C<rcv> callbacks or C<psub>	262	Contains the current port id while executing C<rcv> callbacks or C<psub>
270	blocks.	263	blocks.
271		264
272	=item SELF, %SELF, @SELF...	265	=item *SELF, SELF, %SELF, @SELF...
273		266
274	Due to some quirks in how perl exports variables, it is impossible to	267	Due to some quirks in how perl exports variables, it is impossible to
275	just export C<$SELF>, all the symbols called C<SELF> are exported by this	268	just export C<$SELF>, all the symbols named C<SELF> are exported by this
276	module, but only C<$SELF> is currently used.	269	module, but only C<$SELF> is currently used.
277		270
278	=item snd $port, type => @data	271	=item snd $port, type => @data
279		272
280	=item snd $port, @msg	273	=item snd $port, @msg
281		274
282	Send the given message to the given port ID, which can identify either	275	Send the given message to the given port, which can identify either a
283	a local or a remote port, and must be a port ID.	276	local or a remote port, and must be a port ID.
284		277
285	While the message can be about anything, it is highly recommended to use a	278	While the message can be almost anything, it is highly recommended to
286	string as first element (a port ID, or some word that indicates a request	279	use a string as first element (a port ID, or some word that indicates a
287	type etc.).	280	request type etc.) and to consist if only simple perl values (scalars,
		281	arrays, hashes) - if you think you need to pass an object, think again.
288		282
289	The message data effectively becomes read-only after a call to this	283	The message data logically becomes read-only after a call to this
290	function: modifying any argument is not allowed and can cause many	284	function: modifying any argument (or values referenced by them) is
291	problems.	285	forbidden, as there can be considerable time between the call to C<snd>
		286	and the time the message is actually being serialised - in fact, it might
		287	never be copied as within the same process it is simply handed to the
		288	receiving port.
292		289
293	The type of data you can transfer depends on the transport protocol: when	290	The type of data you can transfer depends on the transport protocol: when
294	JSON is used, then only strings, numbers and arrays and hashes consisting	291	JSON is used, then only strings, numbers and arrays and hashes consisting
295	of those are allowed (no objects). When Storable is used, then anything	292	of those are allowed (no objects). When Storable is used, then anything
296	that Storable can serialise and deserialise is allowed, and for the local	293	that Storable can serialise and deserialise is allowed, and for the local
297	node, anything can be passed.	294	node, anything can be passed. Best rely only on the common denominator of
		295	these.
298		296
299	=item $local_port = port	297	=item $local_port = port
300		298
301	Create a new local port object and returns its port ID. Initially it has	299	Create a new local port object and returns its port ID. Initially it has
302	no callbacks set and will throw an error when it receives messages.	300	no callbacks set and will throw an error when it receives messages.
…		…
349	The default callback received all messages not matched by a more specific	347	The default callback received all messages not matched by a more specific
350	C<tag> match.	348	C<tag> match.
351		349
352	=item rcv $local_port, tag => $callback->(@msg_without_tag), ...	350	=item rcv $local_port, tag => $callback->(@msg_without_tag), ...
353		351
354	Register callbacks to be called on messages starting with the given tag on	352	Register (or replace) callbacks to be called on messages starting with the
355	the given port (and return the port), or unregister it (when C<$callback>	353	given tag on the given port (and return the port), or unregister it (when
356	is C<$undef>).	354	C<$callback> is C<$undef> or missing). There can only be one callback
		355	registered for each tag.
357		356
358	The original message will be passed to the callback, after the first	357	The original message will be passed to the callback, after the first
359	element (the tag) has been removed. The callback will use the same	358	element (the tag) has been removed. The callback will use the same
360	environment as the default callback (see above).	359	environment as the default callback (see above).
361		360
…		…
373	rcv port,	372	rcv port,
374	msg1 => sub { ... },	373	msg1 => sub { ... },
375	...	374	...
376	;	375	;
377		376
		377	Example: temporarily register a rcv callback for a tag matching some port
		378	(e.g. for a rpc reply) and unregister it after a message was received.
		379
		380	rcv $port, $otherport => sub {
		381	my @reply = @_;
		382
		383	rcv $SELF, $otherport;
		384	};
		385
378	=cut	386	=cut
379		387
380	sub rcv($@) {	388	sub rcv($@) {
381	my $port = shift;	389	my $port = shift;
382	my ($noderef, $portid) = split /#/, $port, 2;	390	my ($nodeid, $portid) = split /#/, $port, 2;
383		391
384	($NODE{$noderef} \|\| add_node $noderef) == $NODE{""}	392	$NODE{$nodeid} == $NODE{""}
385	or Carp::croak "$port: rcv can only be called on local ports, caught";	393	or Carp::croak "$port: rcv can only be called on local ports, caught";
386		394
387	while (@_) {	395	while (@_) {
388	if (ref $_[0]) {	396	if (ref $_[0]) {
389	if (my $self = $PORT_DATA{$portid}) {	397	if (my $self = $PORT_DATA{$portid}) {
…		…
468	$res	476	$res
469	}	477	}
470	}	478	}
471	}	479	}
472		480
473	=item $guard = mon $port, $cb->(@reason)	481	=item $guard = mon $port, $cb->(@reason) # call $cb when $port dies
474		482
475	=item $guard = mon $port, $rcvport	483	=item $guard = mon $port, $rcvport # kill $rcvport when $port dies
476		484
477	=item $guard = mon $port	485	=item $guard = mon $port # kill $SELF when $port dies
478		486
479	=item $guard = mon $port, $rcvport, @msg	487	=item $guard = mon $port, $rcvport, @msg # send a message when $port dies
480		488
481	Monitor the given port and do something when the port is killed or	489	Monitor the given port and do something when the port is killed or
482	messages to it were lost, and optionally return a guard that can be used	490	messages to it were lost, and optionally return a guard that can be used
483	to stop monitoring again.	491	to stop monitoring again.
484
485	C<mon> effectively guarantees that, in the absence of hardware failures,
486	that after starting the monitor, either all messages sent to the port
487	will arrive, or the monitoring action will be invoked after possible
488	message loss has been detected. No messages will be lost "in between"
489	(after the first lost message no further messages will be received by the
490	port). After the monitoring action was invoked, further messages might get
491	delivered again.
492		492
493	In the first form (callback), the callback is simply called with any	493	In the first form (callback), the callback is simply called with any
494	number of C<@reason> elements (no @reason means that the port was deleted	494	number of C<@reason> elements (no @reason means that the port was deleted
495	"normally"). Note also that I<< the callback B<must> never die >>, so use	495	"normally"). Note also that I<< the callback B<must> never die >>, so use
496	C<eval> if unsure.	496	C<eval> if unsure.
497		497
498	In the second form (another port given), the other port (C<$rcvport>)	498	In the second form (another port given), the other port (C<$rcvport>)
499	will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on	499	will be C<kil>'ed with C<@reason>, if a @reason was specified, i.e. on
500	"normal" kils nothing happens, while under all other conditions, the other	500	"normal" kils nothing happens, while under all other conditions, the other
501	port is killed with the same reason.	501	port is killed with the same reason.
502		502
503	The third form (kill self) is the same as the second form, except that	503	The third form (kill self) is the same as the second form, except that
504	C<$rvport> defaults to C<$SELF>.	504	C<$rvport> defaults to C<$SELF>.
505		505
506	In the last form (message), a message of the form C<@msg, @reason> will be	506	In the last form (message), a message of the form C<@msg, @reason> will be
507	C<snd>.	507	C<snd>.
		508
		509	Monitoring-actions are one-shot: once messages are lost (and a monitoring
		510	alert was raised), they are removed and will not trigger again.
508		511
509	As a rule of thumb, monitoring requests should always monitor a port from	512	As a rule of thumb, monitoring requests should always monitor a port from
510	a local port (or callback). The reason is that kill messages might get	513	a local port (or callback). The reason is that kill messages might get
511	lost, just like any other message. Another less obvious reason is that	514	lost, just like any other message. Another less obvious reason is that
512	even monitoring requests can get lost (for exmaple, when the connection	515	even monitoring requests can get lost (for example, when the connection
513	to the other node goes down permanently). When monitoring a port locally	516	to the other node goes down permanently). When monitoring a port locally
514	these problems do not exist.	517	these problems do not exist.
515		518
		519	C<mon> effectively guarantees that, in the absence of hardware failures,
		520	after starting the monitor, either all messages sent to the port will
		521	arrive, or the monitoring action will be invoked after possible message
		522	loss has been detected. No messages will be lost "in between" (after
		523	the first lost message no further messages will be received by the
		524	port). After the monitoring action was invoked, further messages might get
		525	delivered again.
		526
		527	Inter-host-connection timeouts and monitoring depend on the transport
		528	used. The only transport currently implemented is TCP, and AnyEvent::MP
		529	relies on TCP to detect node-downs (this can take 10-15 minutes on a
		530	non-idle connection, and usually around two hours for idle conenctions).
		531
		532	This means that monitoring is good for program errors and cleaning up
		533	stuff eventually, but they are no replacement for a timeout when you need
		534	to ensure some maximum latency.
		535
516	Example: call a given callback when C<$port> is killed.	536	Example: call a given callback when C<$port> is killed.
517		537
518	mon $port, sub { warn "port died because of <@_>\n" };	538	mon $port, sub { warn "port died because of <@_>\n" };
519		539
520	Example: kill ourselves when C<$port> is killed abnormally.	540	Example: kill ourselves when C<$port> is killed abnormally.
…		…
526	mon $port, $self => "restart";	546	mon $port, $self => "restart";
527		547
528	=cut	548	=cut
529		549
530	sub mon {	550	sub mon {
531	my ($noderef, $port) = split /#/, shift, 2;	551	my ($nodeid, $port) = split /#/, shift, 2;
532		552
533	my $node = $NODE{$noderef} \|\| add_node $noderef;	553	my $node = $NODE{$nodeid} \|\| add_node $nodeid;
534		554
535	my $cb = @_ ? shift : $SELF \|\| Carp::croak 'mon: called with one argument only, but $SELF not set,';	555	my $cb = @_ ? shift : $SELF \|\| Carp::croak 'mon: called with one argument only, but $SELF not set,';
536		556
537	unless (ref $cb) {	557	unless (ref $cb) {
538	if (@_) {	558	if (@_) {
…		…
558	is killed, the references will be freed.	578	is killed, the references will be freed.
559		579
560	Optionally returns a guard that will stop the monitoring.	580	Optionally returns a guard that will stop the monitoring.
561		581
562	This function is useful when you create e.g. timers or other watchers and	582	This function is useful when you create e.g. timers or other watchers and
563	want to free them when the port gets killed:	583	want to free them when the port gets killed (note the use of C<psub>):
564		584
565	$port->rcv (start => sub {	585	$port->rcv (start => sub {
566	my $timer; $timer = mon_guard $port, AE::timer 1, 1, sub {	586	my $timer; $timer = mon_guard $port, AE::timer 1, 1, psub {
567	undef $timer if 0.9 < rand;	587	undef $timer if 0.9 < rand;
568	});	588	});
569	});	589	});
570		590
571	=cut	591	=cut
…		…
580		600
581	=item kil $port[, @reason]	601	=item kil $port[, @reason]
582		602
583	Kill the specified port with the given C<@reason>.	603	Kill the specified port with the given C<@reason>.
584		604
585	If no C<@reason> is specified, then the port is killed "normally" (linked	605	If no C<@reason> is specified, then the port is killed "normally" (ports
586	ports will not be kileld, or even notified).	606	monitoring other ports will not necessarily die because a port dies
		607	"normally").
587		608
588	Otherwise, linked ports get killed with the same reason (second form of	609	Otherwise, linked ports get killed with the same reason (second form of
589	C<mon>, see below).	610	C<mon>, see above).
590		611
591	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks	612	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
592	will be reported as reason C<< die => $@ >>.	613	will be reported as reason C<< die => $@ >>.
593		614
594	Transport/communication errors are reported as C<< transport_error =>	615	Transport/communication errors are reported as C<< transport_error =>
…		…
599	=item $port = spawn $node, $initfunc[, @initdata]	620	=item $port = spawn $node, $initfunc[, @initdata]
600		621
601	Creates a port on the node C<$node> (which can also be a port ID, in which	622	Creates a port on the node C<$node> (which can also be a port ID, in which
602	case it's the node where that port resides).	623	case it's the node where that port resides).
603		624
604	The port ID of the newly created port is return immediately, and it is	625	The port ID of the newly created port is returned immediately, and it is
605	permissible to immediately start sending messages or monitor the port.	626	possible to immediately start sending messages or to monitor the port.
606		627
607	After the port has been created, the init function is	628	After the port has been created, the init function is called on the remote
608	called. This function must be a fully-qualified function name	629	node, in the same context as a C<rcv> callback. This function must be a
609	(e.g. C<MyApp::Chat::Server::init>). To specify a function in the main	630	fully-qualified function name (e.g. C<MyApp::Chat::Server::init>). To
610	program, use C<::name>.	631	specify a function in the main program, use C<::name>.
611		632
612	If the function doesn't exist, then the node tries to C<require>	633	If the function doesn't exist, then the node tries to C<require>
613	the package, then the package above the package and so on (e.g.	634	the package, then the package above the package and so on (e.g.
614	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function	635	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
615	exists or it runs out of package names.	636	exists or it runs out of package names.
616		637
617	The init function is then called with the newly-created port as context	638	The init function is then called with the newly-created port as context
618	object (C<$SELF>) and the C<@initdata> values as arguments.	639	object (C<$SELF>) and the C<@initdata> values as arguments. It I<must>
		640	call one of the C<rcv> functions to set callbacks on C<$SELF>, otherwise
		641	the port might not get created.
619		642
620	A common idiom is to pass your own port, monitor the spawned port, and	643	A common idiom is to pass a local port, immediately monitor the spawned
621	in the init function, monitor the original port. This two-way monitoring	644	port, and in the remote init function, immediately monitor the passed
622	ensures that both ports get cleaned up when there is a problem.	645	local port. This two-way monitoring ensures that both ports get cleaned up
		646	when there is a problem.
		647
		648	C<spawn> guarantees that the C<$initfunc> has no visible effects on the
		649	caller before C<spawn> returns (by delaying invocation when spawn is
		650	called for the local node).
623		651
624	Example: spawn a chat server port on C<$othernode>.	652	Example: spawn a chat server port on C<$othernode>.
625		653
626	# this node, executed from within a port context:	654	# this node, executed from within a port context:
627	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;	655	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;
…		…
642		670
643	sub _spawn {	671	sub _spawn {
644	my $port = shift;	672	my $port = shift;
645	my $init = shift;	673	my $init = shift;
646		674
		675	# rcv will create the actual port
647	local $SELF = "$NODE#$port";	676	local $SELF = "$NODE#$port";
648	eval {	677	eval {
649	&{ load_func $init }	678	&{ load_func $init }
650	};	679	};
651	_self_die if $@;	680	_self_die if $@;
652	}	681	}
653		682
654	sub spawn(@) {	683	sub spawn(@) {
655	my ($noderef, undef) = split /#/, shift, 2;	684	my ($nodeid, undef) = split /#/, shift, 2;
656		685
657	my $id = "$RUNIQ." . $ID++;	686	my $id = "$RUNIQ." . $ID++;
658		687
659	$_[0] =~ /::/	688	$_[0] =~ /::/
660	or Carp::croak "spawn init function must be a fully-qualified name, caught";	689	or Carp::croak "spawn init function must be a fully-qualified name, caught";
661		690
662	($NODE{$noderef} \|\| add_node $noderef)	691	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;
663	->send (["", "AnyEvent::MP::_spawn" => $id, @_]);
664		692
665	"$noderef#$id"	693	"$nodeid#$id"
666	}	694	}
667		695
668	=back	696	=item after $timeout, @msg
669		697
670	=head1 NODE MESSAGES	698	=item after $timeout, $callback
671		699
672	Nodes understand the following messages sent to them. Many of them take	700	Either sends the given message, or call the given callback, after the
673	arguments called C<@reply>, which will simply be used to compose a reply	701	specified number of seconds.
674	message - C<$reply[0]> is the port to reply to, C<$reply[1]> the type and
675	the remaining arguments are simply the message data.
676		702
677	While other messages exist, they are not public and subject to change.	703	This is simply a utility function that comes in handy at times - the
		704	AnyEvent::MP author is not convinced of the wisdom of having it, though,
		705	so it may go away in the future.
678		706
679	=over 4
680
681	=cut	707	=cut
682		708
683	=item lookup => $name, @reply	709	sub after($@) {
		710	my ($timeout, @action) = @_;
684		711
685	Replies with the port ID of the specified well-known port, or C<undef>.	712	my $t; $t = AE::timer $timeout, 0, sub {
		713	undef $t;
		714	ref $action[0]
		715	? $action[0]()
		716	: snd @action;
		717	};
		718	}
686		719
687	=item devnull => ...	720	=item cal $port, @msg, $callback[, $timeout]
688		721
689	Generic data sink/CPU heat conversion.	722	A simple form of RPC - sends a message to the given C<$port> with the
		723	given contents (C<@msg>), but adds a reply port to the message.
690		724
691	=item relay => $port, @msg	725	The reply port is created temporarily just for the purpose of receiving
		726	the reply, and will be C<kil>ed when no longer needed.
692		727
693	Simply forwards the message to the given port.	728	A reply message sent to the port is passed to the C<$callback> as-is.
694		729
695	=item eval => $string[ @reply]	730	If an optional time-out (in seconds) is given and it is not C<undef>,
		731	then the callback will be called without any arguments after the time-out
		732	elapsed and the port is C<kil>ed.
696		733
697	Evaluates the given string. If C<@reply> is given, then a message of the	734	If no time-out is given, then the local port will monitor the remote port
698	form C<@reply, $@, @evalres> is sent.	735	instead, so it eventually gets cleaned-up.
699		736
700	Example: crash another node.	737	Currently this function returns the temporary port, but this "feature"
		738	might go in future versions unless you can make a convincing case that
		739	this is indeed useful for something.
701		740
702	snd $othernode, eval => "exit";	741	=cut
703		742
704	=item time => @reply	743	sub cal(@) {
		744	my $timeout = ref $_[-1] ? undef : pop;
		745	my $cb = pop;
705		746
706	Replies the the current node time to C<@reply>.	747	my $port = port {
		748	undef $timeout;
		749	kil $SELF;
		750	&$cb;
		751	};
707		752
708	Example: tell the current node to send the current time to C<$myport> in a	753	if (defined $timeout) {
709	C<timereply> message.	754	$timeout = AE::timer $timeout, 0, sub {
		755	undef $timeout;
		756	kil $port;
		757	$cb->();
		758	};
		759	} else {
		760	mon $_[0], sub {
		761	kil $port;
		762	$cb->();
		763	};
		764	}
710		765
711	snd $NODE, time => $myport, timereply => 1, 2;	766	push @_, $port;
712	# => snd $myport, timereply => 1, 2, <time>	767	&snd;
		768
		769	$port
		770	}
713		771
714	=back	772	=back
715		773
716	=head1 AnyEvent::MP vs. Distributed Erlang	774	=head1 AnyEvent::MP vs. Distributed Erlang
717		775
…		…
727		785
728	Despite the similarities, there are also some important differences:	786	Despite the similarities, there are also some important differences:
729		787
730	=over 4	788	=over 4
731		789
732	=item * Node references contain the recipe on how to contact them.	790	=item * Node IDs are arbitrary strings in AEMP.
733		791
734	Erlang relies on special naming and DNS to work everywhere in the	792	Erlang relies on special naming and DNS to work everywhere in the same
735	same way. AEMP relies on each node knowing it's own address(es), with	793	way. AEMP relies on each node somehow knowing its own address(es) (e.g. by
736	convenience functionality.	794	configuration or DNS), but will otherwise discover other odes itself.
737		795
738	This means that AEMP requires a less tightly controlled environment at the
739	cost of longer node references and a slightly higher management overhead.
740
741	=item Erlang has a "remote ports are like local ports" philosophy, AEMP	796	=item * Erlang has a "remote ports are like local ports" philosophy, AEMP
742	uses "local ports are like remote ports".	797	uses "local ports are like remote ports".
743		798
744	The failure modes for local ports are quite different (runtime errors	799	The failure modes for local ports are quite different (runtime errors
745	only) then for remote ports - when a local port dies, you I<know> it dies,	800	only) then for remote ports - when a local port dies, you I<know> it dies,
746	when a connection to another node dies, you know nothing about the other	801	when a connection to another node dies, you know nothing about the other
…		…
757		812
758	Erlang uses processes that selectively receive messages, and therefore	813	Erlang uses processes that selectively receive messages, and therefore
759	needs a queue. AEMP is event based, queuing messages would serve no	814	needs a queue. AEMP is event based, queuing messages would serve no
760	useful purpose. For the same reason the pattern-matching abilities of	815	useful purpose. For the same reason the pattern-matching abilities of
761	AnyEvent::MP are more limited, as there is little need to be able to	816	AnyEvent::MP are more limited, as there is little need to be able to
762	filter messages without dequeing them.	817	filter messages without dequeuing them.
763		818
764	(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).	819	(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).
765		820
766	=item * Erlang sends are synchronous, AEMP sends are asynchronous.	821	=item * Erlang sends are synchronous, AEMP sends are asynchronous.
767		822
…		…
773		828
774	Erlang makes few guarantees on messages delivery - messages can get lost	829	Erlang makes few guarantees on messages delivery - messages can get lost
775	without any of the processes realising it (i.e. you send messages a, b,	830	without any of the processes realising it (i.e. you send messages a, b,
776	and c, and the other side only receives messages a and c).	831	and c, and the other side only receives messages a and c).
777		832
778	AEMP guarantees correct ordering, and the guarantee that there are no	833	AEMP guarantees correct ordering, and the guarantee that after one message
779	holes in the message sequence.	834	is lost, all following ones sent to the same port are lost as well, until
780		835	monitoring raises an error, so there are no silent "holes" in the message
781	=item * In Erlang, processes can be declared dead and later be found to be	836	sequence.
782	alive.
783
784	In Erlang it can happen that a monitored process is declared dead and
785	linked processes get killed, but later it turns out that the process is
786	still alive - and can receive messages.
787
788	In AEMP, when port monitoring detects a port as dead, then that port will
789	eventually be killed - it cannot happen that a node detects a port as dead
790	and then later sends messages to it, finding it is still alive.
791		837
792	=item * Erlang can send messages to the wrong port, AEMP does not.	838	=item * Erlang can send messages to the wrong port, AEMP does not.
793		839
794	In Erlang it is quite likely that a node that restarts reuses a process ID	840	In Erlang it is quite likely that a node that restarts reuses a process ID
795	known to other nodes for a completely different process, causing messages	841	known to other nodes for a completely different process, causing messages
…		…
799	around in the network will not be sent to an unrelated port.	845	around in the network will not be sent to an unrelated port.
800		846
801	=item * Erlang uses unprotected connections, AEMP uses secure	847	=item * Erlang uses unprotected connections, AEMP uses secure
802	authentication and can use TLS.	848	authentication and can use TLS.
803		849
804	AEMP can use a proven protocol - SSL/TLS - to protect connections and	850	AEMP can use a proven protocol - TLS - to protect connections and
805	securely authenticate nodes.	851	securely authenticate nodes.
806		852
807	=item * The AEMP protocol is optimised for both text-based and binary	853	=item * The AEMP protocol is optimised for both text-based and binary
808	communications.	854	communications.
809		855
810	The AEMP protocol, unlike the Erlang protocol, supports both	856	The AEMP protocol, unlike the Erlang protocol, supports both programming
811	language-independent text-only protocols (good for debugging) and binary,	857	language independent text-only protocols (good for debugging) and binary,
812	language-specific serialisers (e.g. Storable).	858	language-specific serialisers (e.g. Storable). By default, unless TLS is
		859	used, the protocol is actually completely text-based.
813		860
814	It has also been carefully designed to be implementable in other languages	861	It has also been carefully designed to be implementable in other languages
815	with a minimum of work while gracefully degrading fucntionality to make the	862	with a minimum of work while gracefully degrading functionality to make the
816	protocol simple.	863	protocol simple.
817		864
818	=item * AEMP has more flexible monitoring options than Erlang.	865	=item * AEMP has more flexible monitoring options than Erlang.
819		866
820	In Erlang, you can chose to receive I<all> exit signals as messages	867	In Erlang, you can chose to receive I<all> exit signals as messages
…		…
823	Erlang, as one can choose between automatic kill, exit message or callback	870	Erlang, as one can choose between automatic kill, exit message or callback
824	on a per-process basis.	871	on a per-process basis.
825		872
826	=item * Erlang tries to hide remote/local connections, AEMP does not.	873	=item * Erlang tries to hide remote/local connections, AEMP does not.
827		874
828	Monitoring in Erlang is not an indicator of process death/crashes,	875	Monitoring in Erlang is not an indicator of process death/crashes, in the
829	as linking is (except linking is unreliable in Erlang).	876	same way as linking is (except linking is unreliable in Erlang).
830		877
831	In AEMP, you don't "look up" registered port names or send to named ports	878	In AEMP, you don't "look up" registered port names or send to named ports
832	that might or might not be persistent. Instead, you normally spawn a port	879	that might or might not be persistent. Instead, you normally spawn a port
833	on the remote node. The init function monitors the you, and you monitor	880	on the remote node. The init function monitors you, and you monitor the
834	the remote port. Since both monitors are local to the node, they are much	881	remote port. Since both monitors are local to the node, they are much more
835	more reliable.	882	reliable (no need for C<spawn_link>).
836		883
837	This also saves round-trips and avoids sending messages to the wrong port	884	This also saves round-trips and avoids sending messages to the wrong port
838	(hard to do in Erlang).	885	(hard to do in Erlang).
839		886
840	=back	887	=back
841		888
842	=head1 RATIONALE	889	=head1 RATIONALE
843		890
844	=over 4	891	=over 4
845		892
846	=item Why strings for ports and noderefs, why not objects?	893	=item Why strings for port and node IDs, why not objects?
847		894
848	We considered "objects", but found that the actual number of methods	895	We considered "objects", but found that the actual number of methods
849	thatc an be called are very low. Since port IDs and noderefs travel over	896	that can be called are quite low. Since port and node IDs travel over
850	the network frequently, the serialising/deserialising would add lots of	897	the network frequently, the serialising/deserialising would add lots of
851	overhead, as well as having to keep a proxy object.	898	overhead, as well as having to keep a proxy object everywhere.
852		899
853	Strings can easily be printed, easily serialised etc. and need no special	900	Strings can easily be printed, easily serialised etc. and need no special
854	procedures to be "valid".	901	procedures to be "valid".
855		902
856	And a a miniport consists of a single closure stored in a global hash - it	903	And as a result, a miniport consists of a single closure stored in a
857	can't become much cheaper.	904	global hash - it can't become much cheaper.
858		905
859	=item Why favour JSON, why not real serialising format such as Storable?	906	=item Why favour JSON, why not a real serialising format such as Storable?
860		907
861	In fact, any AnyEvent::MP node will happily accept Storable as framing	908	In fact, any AnyEvent::MP node will happily accept Storable as framing
862	format, but currently there is no way to make a node use Storable by	909	format, but currently there is no way to make a node use Storable by
863	default.	910	default (although all nodes will accept it).
864		911
865	The default framing protocol is JSON because a) JSON::XS is many times	912	The default framing protocol is JSON because a) JSON::XS is many times
866	faster for small messages and b) most importantly, after years of	913	faster for small messages and b) most importantly, after years of
867	experience we found that object serialisation is causing more problems	914	experience we found that object serialisation is causing more problems
868	than it gains: Just like function calls, objects simply do not travel	915	than it solves: Just like function calls, objects simply do not travel
869	easily over the network, mostly because they will always be a copy, so you	916	easily over the network, mostly because they will always be a copy, so you
870	always have to re-think your design.	917	always have to re-think your design.
871		918
872	Keeping your messages simple, concentrating on data structures rather than	919	Keeping your messages simple, concentrating on data structures rather than
873	objects, will keep your messages clean, tidy and efficient.	920	objects, will keep your messages clean, tidy and efficient.
874		921
875	=back	922	=back
876		923
877	=head1 SEE ALSO	924	=head1 SEE ALSO
878		925
		926	L<AnyEvent::MP::Intro> - a gentle introduction.
		927
		928	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.
		929
		930	L<AnyEvent::MP::Global> - network maintainance and port groups, to find
		931	your applications.
		932
		933	L<AnyEvent::MP::LogCatcher> - simple service to display log messages from
		934	all nodes.
		935
879	L<AnyEvent>.	936	L<AnyEvent>.
880		937
881	=head1 AUTHOR	938	=head1 AUTHOR
882		939
883	Marc Lehmann <schmorp@schmorp.de>	940	Marc Lehmann <schmorp@schmorp.de>

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.52 by root, Fri Aug 14 15:13:20 2009 UTC vs. Revision 1.87 by root, Fri Sep 11 02:32:23 2009 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.52 by root, Fri Aug 14 15:13:20 2009 UTC vs.
Revision 1.87 by root, Fri Sep 11 02:32:23 2009 UTC