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

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

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.54 by root, Fri Aug 14 16:15:37 2009 UTC vs. Revision 1.77 by elmex, Thu Sep 3 07:57:30 2009 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.54 by root, Fri Aug 14 16:15:37 2009 UTC vs.
Revision 1.77 by elmex, Thu Sep 3 07:57:30 2009 UTC