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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.7 by root, Sat Aug 1 15:04:30 2009 UTC vs.
Revision 1.78 by root, Thu Sep 3 20:16:36 2009 UTC

…		…
4		4
5	=head1 SYNOPSIS	5	=head1 SYNOPSIS
6		6
7	use AnyEvent::MP;	7	use AnyEvent::MP;
8		8
9	NODE # returns this node identifier
10	$NODE # contains this node identifier	9	$NODE # contains this node's node ID
		10	NODE # returns this node's node ID
11		11
		12	$SELF # receiving/own port id in rcv callbacks
		13
		14	# initialise the node so it can send/receive messages
		15	configure;
		16
		17	# ports are message destinations
		18
		19	# sending messages
12	snd $port, type => data...;	20	snd $port, type => data...;
		21	snd $port, @msg;
		22	snd @msg_with_first_element_being_a_port;
13		23
14	rcv $port, smartmatch => $cb->($port, @msg);	24	# creating/using ports, the simple way
		25	my $simple_port = port { my @msg = @_ };
15		26
16	# examples:	27	# creating/using ports, tagged message matching
		28	my $port = port;
17	rcv $port2, ping => sub { snd $_[0], "pong"; 0 };	29	rcv $port, ping => sub { snd $_[0], "pong" };
18	rcv $port1, pong => sub { warn "pong received\n" };	30	rcv $port, pong => sub { warn "pong received\n" };
19	snd $port2, ping => $port1;
20		31
21	# more, smarter, matches (_any_ is exported by this module)	32	# create a port on another node
22	rcv $port, [child_died => $pid] => sub { ...	33	my $port = spawn $node, $initfunc, @initdata;
23	rcv $port, [_any_, _any_, 3] => sub { .. $_[2] is 3	34
		35	# monitoring
		36	mon $port, $cb->(@msg) # callback is invoked on death
		37	mon $port, $otherport # kill otherport on abnormal death
		38	mon $port, $otherport, @msg # send message on death
		39
		40	=head1 CURRENT STATUS
		41
		42	bin/aemp - stable.
		43	AnyEvent::MP - stable API, should work.
		44	AnyEvent::MP::Intro - explains most concepts.
		45	AnyEvent::MP::Kernel - mostly stable.
		46	AnyEvent::MP::Global - stable API, protocol not yet final.
		47
		48	stay tuned.
24		49
25	=head1 DESCRIPTION	50	=head1 DESCRIPTION
26		51
27	This module (-family) implements a simple message passing framework.	52	This module (-family) implements a simple message passing framework.
28		53
29	Despite its simplicity, you can securely message other processes running	54	Despite its simplicity, you can securely message other processes running
30	on the same or other hosts.	55	on the same or other hosts, and you can supervise entities remotely.
31		56
32	At the moment, this module family is severly brokena nd underdocumented,	57	For an introduction to this module family, see the L<AnyEvent::MP::Intro>
33	so do not use. This was uploaded mainly to resreve the CPAN namespace -	58	manual page and the examples under F<eg/>.
34	stay tuned!
35		59
36	=head1 CONCEPTS	60	=head1 CONCEPTS
37		61
38	=over 4	62	=over 4
39		63
40	=item port	64	=item port
41		65
42	A port is something you can send messages to with the C<snd> function, and	66	A port is something you can send messages to (with the C<snd> function).
43	you can register C<rcv> handlers with. All C<rcv> handlers will receive
44	messages they match, messages will not be queued.
45		67
		68	Ports allow you to register C<rcv> handlers that can match all or just
		69	some messages. Messages send to ports will not be queued, regardless of
		70	anything was listening for them or not.
		71
46	=item port id - C<noderef#portname>	72	=item port ID - C<nodeid#portname>
47		73
48	A port id is always the noderef, a hash-mark (C<#>) as separator, followed	74	A port ID is the concatenation of a node ID, a hash-mark (C<#>) as
49	by a port name (a printable string of unspecified format).	75	separator, and a port name (a printable string of unspecified format).
50		76
51	=item node	77	=item node
52		78
53	A node is a single process containing at least one port - the node	79	A node is a single process containing at least one port - the node port,
54	port. You can send messages to node ports to let them create new ports,	80	which enables nodes to manage each other remotely, and to create new
55	among other things.	81	ports.
56		82
57	Initially, nodes are either private (single-process only) or hidden	83	Nodes are either public (have one or more listening ports) or private
58	(connected to a master node only). Only when they epxlicitly "become	84	(no listening ports). Private nodes cannot talk to other private nodes
59	public" can you send them messages from unrelated other nodes.	85	currently.
60		86
61	=item noderef - C<host:port,host:port...>, C<id@noderef>, C<id>	87	=item node ID - C<[a-za-Z0-9_\-.:]+>
62		88
63	A noderef is a string that either uniquely identifies a given node (for	89	A node ID is a string that uniquely identifies the node within a
64	private and hidden nodes), or contains a recipe on how to reach a given	90	network. Depending on the configuration used, node IDs can look like a
65	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.
		93
		94	=item binds - C<ip:port>
		95
		96	Nodes can only talk to each other by creating some kind of connection to
		97	each other. To do this, nodes should listen on one or more local transport
		98	endpoints - binds. Currently, only standard C<ip:port> specifications can
		99	be used, which specify TCP ports to listen on.
		100
		101	=item seeds - C<host:port>
		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.
66		115
67	=back	116	=back
68		117
69	=head1 VARIABLES/FUNCTIONS	118	=head1 VARIABLES/FUNCTIONS
70		119
…		…
72		121
73	=cut	122	=cut
74		123
75	package AnyEvent::MP;	124	package AnyEvent::MP;
76		125
77	use AnyEvent::MP::Util ();
78	use AnyEvent::MP::Node;	126	use AnyEvent::MP::Kernel;
79	use AnyEvent::MP::Transport;
80		127
81	use utf8;
82	use common::sense;	128	use common::sense;
83		129
84	use Carp ();	130	use Carp ();
85		131
86	use AE ();	132	use AE ();
87		133
88	use base "Exporter";	134	use base "Exporter";
89		135
90	our $VERSION = '0.01';	136	our $VERSION = $AnyEvent::MP::Kernel::VERSION;
91	our @EXPORT = qw(NODE $NODE $PORT snd rcv _any_);
92		137
93	our $DEFAULT_SECRET;	138	our @EXPORT = qw(
94	our $DEFAULT_PORT = "4040";	139	NODE $NODE *SELF node_of after
		140	configure
		141	snd rcv mon mon_guard kil reg psub spawn
		142	port
		143	);
95		144
96	our $CONNECT_INTERVAL = 5; # new connect every 5s, at least	145	our $SELF;
97	our $CONNECT_TIMEOUT = 30; # includes handshake
98		146
99	sub default_secret {	147	sub _self_die() {
100	unless (defined $DEFAULT_SECRET) {	148	my $msg = $@;
101	if (open my $fh, "<$ENV{HOME}/.aemp-secret") {	149	$msg =~ s/\n+$// unless ref $msg;
102	sysread $fh, $DEFAULT_SECRET, -s $fh;	150	kil $SELF, die => $msg;
103	} else {
104	$DEFAULT_SECRET = AnyEvent::MP::Util::nonce 32;
105	}
106	}
107
108	$DEFAULT_SECRET
109	}	151	}
110		152
111	=item NODE / $NODE	153	=item $thisnode = NODE / $NODE
112		154
113	The C<NODE ()> function and the C<$NODE> variable contain the noderef of	155	The C<NODE> function returns, and the C<$NODE> variable contains, the node
114	the local node. The value is initialised by a call to C<become_public> or	156	ID of the node running in the current process. This value is initialised by
115	C<become_slave>, after which all local port identifiers become invalid.	157	a call to C<configure>.
116		158
117	=cut	159	=item $nodeid = node_of $port
118		160
119	our $UNIQ = sprintf "%x.%x", $$, time; # per-process/node unique cookie	161	Extracts and returns the node ID from a port ID or a node ID.
120	our $ID = "a0";
121	our $PUBLIC = 0;
122	our $NODE;
123	our $PORT;
124		162
125	our %NODE; # node id to transport mapping, or "undef", for local node	163	=item configure $profile, key => value...
126	our %PORT; # local ports
127	our %LISTENER; # local transports
128		164
129	sub NODE() { $NODE }	165	=item configure key => value...
130		166
131	{	167	Before a node can talk to other nodes on the network (i.e. enter
132	use POSIX ();	168	"distributed mode") it has to configure itself - the minimum a node needs
133	my $nodename = (POSIX::uname)[1];	169	to know is its own name, and optionally it should know the addresses of
134	$NODE = "$$\@$nodename";	170	some other nodes in the network to discover other nodes.
135	}
136		171
137	sub _ANY_() { 1 }	172	This function configures a node - it must be called exactly once (or
138	sub _any_() { \&_ANY_ }	173	never) before calling other AnyEvent::MP functions.
139		174
140	sub add_node {	175	=over 4
141	my ($noderef) = @_;
142		176
143	return $NODE{$noderef}	177	=item step 1, gathering configuration from profiles
144	if exists $NODE{$noderef};
145		178
146	for (split /,/, $noderef) {	179	The function first looks up a profile in the aemp configuration (see the
147	return $NODE{$noderef} = $NODE{$_}	180	L<aemp> commandline utility). The profile name can be specified via the
148	if exists $NODE{$_};	181	named C<profile> parameter or can simply be the first parameter). If it is
149	}	182	missing, then the nodename (F<uname -n>) will be used as profile name.
150		183
151	# for indirect sends, use a different class	184	The profile data is then gathered as follows:
152	my $node = new AnyEvent::MP::Node::Direct $noderef;
153		185
154	$NODE{$_} = $node	186	First, all remaining key => value pairs (all of which are conveniently
155	for $noderef, split /,/, $noderef;	187	undocumented at the moment) will be interpreted as configuration
		188	data. Then they will be overwritten by any values specified in the global
		189	default configuration (see the F<aemp> utility), then the chain of
		190	profiles chosen by the profile name (and any C<parent> attributes).
156		191
157	$node	192	That means that the values specified in the profile have highest priority
158	}	193	and the values specified directly via C<configure> have lowest priority,
		194	and can only be used to specify defaults.
159		195
		196	If the profile specifies a node ID, then this will become the node ID of
		197	this process. If not, then the profile name will be used as node ID. The
		198	special node ID of C<anon/> will be replaced by a random node ID.
		199
		200	=item step 2, bind listener sockets
		201
		202	The next step is to look up the binds in the profile, followed by binding
		203	aemp protocol listeners on all binds specified (it is possible and valid
		204	to have no binds, meaning that the node cannot be contacted form the
		205	outside. This means the node cannot talk to other nodes that also have no
		206	binds, but it can still talk to all "normal" nodes).
		207
		208	If the profile does not specify a binds list, then a default of C<*> is
		209	used, meaning the node will bind on a dynamically-assigned port on every
		210	local IP address it finds.
		211
		212	=item step 3, connect to seed nodes
		213
		214	As the last step, the seeds list from the profile is passed to the
		215	L<AnyEvent::MP::Global> module, which will then use it to keep
		216	connectivity with at least one node at any point in time.
		217
		218	=back
		219
		220	Example: become a distributed node using the locla node name as profile.
		221	This should be the most common form of invocation for "daemon"-type nodes.
		222
		223	configure
		224
		225	Example: become an anonymous node. This form is often used for commandline
		226	clients.
		227
		228	configure nodeid => "anon/";
		229
		230	Example: configure a node using a profile called seed, which si suitable
		231	for a seed node as it binds on all local addresses on a fixed port (4040,
		232	customary for aemp).
		233
		234	# use the aemp commandline utility
		235	# aemp profile seed nodeid anon/ binds '*:4040'
		236
		237	# then use it
		238	configure profile => "seed";
		239
		240	# or simply use aemp from the shell again:
		241	# aemp run profile seed
		242
		243	# or provide a nicer-to-remember nodeid
		244	# aemp run profile seed nodeid "$(hostname)"
		245
		246	=item $SELF
		247
		248	Contains the current port id while executing C<rcv> callbacks or C<psub>
		249	blocks.
		250
		251	=item *SELF, SELF, %SELF, @SELF...
		252
		253	Due to some quirks in how perl exports variables, it is impossible to
		254	just export C<$SELF>, all the symbols named C<SELF> are exported by this
		255	module, but only C<$SELF> is currently used.
		256
160	=item snd $portid, type => @data	257	=item snd $port, type => @data
161		258
162	=item snd $portid, @msg	259	=item snd $port, @msg
163		260
164	Send the given message to the given port ID, which can identify either a	261	Send the given message to the given port, which can identify either a
165	local or a remote port.	262	local or a remote port, and must be a port ID.
166		263
167	While the message can be about anything, it is highly recommended to use	264	While the message can be almost anything, it is highly recommended to
168	a constant string as first element.	265	use a string as first element (a port ID, or some word that indicates a
		266	request type etc.) and to consist if only simple perl values (scalars,
		267	arrays, hashes) - if you think you need to pass an object, think again.
169		268
170	The message data effectively becomes read-only after a call to this	269	The message data logically becomes read-only after a call to this
171	function: modifying any argument is not allowed and can cause many	270	function: modifying any argument (or values referenced by them) is
172	problems.	271	forbidden, as there can be considerable time between the call to C<snd>
		272	and the time the message is actually being serialised - in fact, it might
		273	never be copied as within the same process it is simply handed to the
		274	receiving port.
173		275
174	The type of data you can transfer depends on the transport protocol: when	276	The type of data you can transfer depends on the transport protocol: when
175	JSON is used, then only strings, numbers and arrays and hashes consisting	277	JSON is used, then only strings, numbers and arrays and hashes consisting
176	of those are allowed (no objects). When Storable is used, then anything	278	of those are allowed (no objects). When Storable is used, then anything
177	that Storable can serialise and deserialise is allowed, and for the local	279	that Storable can serialise and deserialise is allowed, and for the local
178	node, anything can be passed.	280	node, anything can be passed. Best rely only on the common denominator of
		281	these.
179		282
180	=cut	283	=item $local_port = port
181		284
182	sub snd(@) {	285	Create a new local port object and returns its port ID. Initially it has
183	my ($noderef, $port) = split /#/, shift, 2;	286	no callbacks set and will throw an error when it receives messages.
184		287
185	add_node $noderef	288	=item $local_port = port { my @msg = @_ }
186	unless exists $NODE{$noderef};
187		289
188	$NODE{$noderef}->send (["$port", [@_]]);	290	Creates a new local port, and returns its ID. Semantically the same as
189	}	291	creating a port and calling C<rcv $port, $callback> on it.
190		292
		293	The block will be called for every message received on the port, with the
		294	global variable C<$SELF> set to the port ID. Runtime errors will cause the
		295	port to be C<kil>ed. The message will be passed as-is, no extra argument
		296	(i.e. no port ID) will be passed to the callback.
		297
		298	If you want to stop/destroy the port, simply C<kil> it:
		299
		300	my $port = port {
		301	my @msg = @_;
		302	...
		303	kil $SELF;
		304	};
		305
		306	=cut
		307
		308	sub rcv($@);
		309
		310	sub _kilme {
		311	die "received message on port without callback";
		312	}
		313
		314	sub port(;&) {
		315	my $id = "$UNIQ." . $ID++;
		316	my $port = "$NODE#$id";
		317
		318	rcv $port, shift \|\| \&_kilme;
		319
		320	$port
		321	}
		322
191	=item rcv $portid, type => $callback->(@msg)	323	=item rcv $local_port, $callback->(@msg)
192		324
193	=item rcv $portid, $smartmatch => $callback->(@msg)	325	Replaces the default callback on the specified port. There is no way to
		326	remove the default callback: use C<sub { }> to disable it, or better
		327	C<kil> the port when it is no longer needed.
194		328
195	=item rcv $portid, [$smartmatch...] => $callback->(@msg)	329	The global C<$SELF> (exported by this module) contains C<$port> while
		330	executing the callback. Runtime errors during callback execution will
		331	result in the port being C<kil>ed.
196		332
197	Register a callback on the port identified by C<$portid>, which I<must> be	333	The default callback received all messages not matched by a more specific
198	a local port.	334	C<tag> match.
199		335
200	The callback has to return a true value when its work is done, after	336	=item rcv $local_port, tag => $callback->(@msg_without_tag), ...
201	which is will be removed, or a false value in which case it will stay
202	registered.
203		337
204	If the match is an array reference, then it will be matched against the	338	Register (or replace) callbacks to be called on messages starting with the
205	first elements of the message, otherwise only the first element is being	339	given tag on the given port (and return the port), or unregister it (when
206	matched.	340	C<$callback> is C<$undef> or missing). There can only be one callback
		341	registered for each tag.
207		342
208	Any element in the match that is specified as C<_any_> (a function	343	The original message will be passed to the callback, after the first
209	exported by this module) matches any single element of the message.	344	element (the tag) has been removed. The callback will use the same
		345	environment as the default callback (see above).
210		346
211	While not required, it is highly recommended that the first matching	347	Example: create a port and bind receivers on it in one go.
212	element is a string identifying the message. The one-string-only match is	348
213	also the most efficient match (by far).	349	my $port = rcv port,
		350	msg1 => sub { ... },
		351	msg2 => sub { ... },
		352	;
		353
		354	Example: create a port, bind receivers and send it in a message elsewhere
		355	in one go:
		356
		357	snd $otherport, reply =>
		358	rcv port,
		359	msg1 => sub { ... },
		360	...
		361	;
		362
		363	Example: temporarily register a rcv callback for a tag matching some port
		364	(e.g. for a rpc reply) and unregister it after a message was received.
		365
		366	rcv $port, $otherport => sub {
		367	my @reply = @_;
		368
		369	rcv $SELF, $otherport;
		370	};
214		371
215	=cut	372	=cut
216		373
217	sub rcv($@) {	374	sub rcv($@) {
218	my ($port, $match, $cb) = @_;	375	my $port = shift;
219
220	my $port = $PORT{$port}
221	or do {
222	my ($noderef, $lport) = split /#/, $port;	376	my ($nodeid, $portid) = split /#/, $port, 2;
223	"AnyEvent::MP::Node::Self" eq ref $NODE{$noderef}	377
		378	$NODE{$nodeid} == $NODE{""}
224	or Carp::croak "$port: can only rcv on local ports";	379	or Carp::croak "$port: rcv can only be called on local ports, caught";
225		380
226	$PORT{$lport}	381	while (@_) {
227	or Carp::croak "$port: port does not exist";	382	if (ref $_[0]) {
228		383	if (my $self = $PORT_DATA{$portid}) {
229	$PORT{$port} = $PORT{$lport} # also return	384	"AnyEvent::MP::Port" eq ref $self
230	};	385	or Carp::croak "$port: rcv can only be called on message matching ports, caught";
231		386
232	if (!ref $match) {	387	$self->[2] = shift;
233	push @{ $port->{rc0}{$match} }, [$cb];
234	} elsif (("ARRAY" eq ref $match && !ref $match->[0])) {
235	my ($type, @match) = @$match;
236	@match
237	? push @{ $port->{rcv}{$match->[0]} }, [$cb, \@match]
238	: push @{ $port->{rc0}{$match->[0]} }, [$cb];
239	} else {	388	} else {
240	push @{ $port->{any} }, [$cb, $match];	389	my $cb = shift;
241	}	390	$PORT{$portid} = sub {
242	}	391	local $SELF = $port;
243		392	eval { &$cb }; _self_die if $@;
244	sub _inject {
245	my ($port, $msg) = @{+shift};
246
247	$port = $PORT{$port}
248	or return;
249
250	@_ = @$msg;
251
252	for (@{ $port->{rc0}{$msg->[0]} }) {
253	$_ && &{$_->[0]}
254	&& undef $_;
255	}
256
257	for (@{ $port->{rcv}{$msg->[0]} }) {
258	$_ && [@_[1..$#{$_->[1]}]] ~~ $_->[1]
259	&& &{$_->[0]}
260	&& undef $_;
261	}
262
263	for (@{ $port->{any} }) {
264	$_ && [@_[0..$#{$_->[1]}]] ~~ $_->[1]
265	&& &{$_->[0]}
266	&& undef $_;
267	}
268	}
269
270	sub normalise_noderef($) {
271	my ($noderef) = @_;
272
273	my $cv = AE::cv;
274	my @res;
275
276	$cv->begin (sub {
277	my %seen;
278	my @refs;
279	for (sort { $a->[0] <=> $b->[0] } @res) {
280	push @refs, $_->[1] unless $seen{$_->[1]}++
281	}
282	shift->send (join ",", @refs);
283	});
284
285	$noderef = $DEFAULT_PORT unless length $noderef;
286
287	my $idx;
288	for my $t (split /,/, $noderef) {
289	my $pri = ++$idx;
290
291	#TODO: this should be outside normalise_noderef and in become_public
292	if ($t =~ /^\d*$/) {
293	my $nodename = (POSIX::uname)[1];
294
295	$cv->begin;
296	AnyEvent::Socket::resolve_sockaddr $nodename, $t \|\| "aemp=$DEFAULT_PORT", "tcp", 0, undef, sub {
297	for (@_) {
298	my ($service, $host) = AnyEvent::Socket::unpack_sockaddr $_->[3];
299	push @res, [
300	$pri += 1e-5,
301	AnyEvent::Socket::format_hostport AnyEvent::Socket::format_address $host, $service
302	];
303	}	393	};
304	$cv->end;	394	}
		395	} elsif (defined $_[0]) {
		396	my $self = $PORT_DATA{$portid} \|\|= do {
		397	my $self = bless [$PORT{$port} \|\| sub { }, { }, $port], "AnyEvent::MP::Port";
		398
		399	$PORT{$portid} = sub {
		400	local $SELF = $port;
		401
		402	if (my $cb = $self->[1]{$_[0]}) {
		403	shift;
		404	eval { &$cb }; _self_die if $@;
		405	} else {
		406	&{ $self->[0] };
		407	}
		408	};
		409
		410	$self
305	};	411	};
306		412
307	# my (undef, undef, undef, undef, @ipv4) = gethostbyname $nodename;	413	"AnyEvent::MP::Port" eq ref $self
308	#	414	or Carp::croak "$port: rcv can only be called on message matching ports, caught";
309	# for (@ipv4) {	415
310	# push @res, [	416	my ($tag, $cb) = splice @_, 0, 2;
311	# $pri,	417
312	# AnyEvent::Socket::format_hostport AnyEvent::Socket::format_address $_, $t \|\| $DEFAULT_PORT,	418	if (defined $cb) {
313	# ];	419	$self->[1]{$tag} = $cb;
314	# }
315	} else {	420	} else {
316	my ($host, $port) = AnyEvent::Socket::parse_hostport $t, "aemp=$DEFAULT_PORT"	421	delete $self->[1]{$tag};
317	or Carp::croak "$t: unparsable transport descriptor";
318
319	$cv->begin;
320	AnyEvent::Socket::resolve_sockaddr $host, $port, "tcp", 0, undef, sub {
321	for (@_) {
322	my ($service, $host) = AnyEvent::Socket::unpack_sockaddr $_->[3];
323	push @res, [
324	$pri += 1e-5,
325	AnyEvent::Socket::format_hostport AnyEvent::Socket::format_address $host, $service
326	];
327	}
328	$cv->end;
329	}	422	}
330	}	423	}
331	}	424	}
332		425
333	$cv->end;	426	$port
334
335	$cv
336	}	427	}
337		428
338	sub become_public {	429	=item $closure = psub { BLOCK }
339	return if $PUBLIC;
340		430
341	my $noderef = join ",", ref $_[0] ? @{+shift} : shift;	431	Remembers C<$SELF> and creates a closure out of the BLOCK. When the
342	my @args = @_;	432	closure is executed, sets up the environment in the same way as in C<rcv>
		433	callbacks, i.e. runtime errors will cause the port to get C<kil>ed.
343		434
344	$NODE = (normalise_noderef $noderef)->recv;	435	This is useful when you register callbacks from C<rcv> callbacks:
345		436
346	for my $t (split /,/, $NODE) {	437	rcv delayed_reply => sub {
347	$NODE{$t} = $NODE{""};	438	my ($delay, @reply) = @_;
348		439	my $timer = AE::timer $delay, 0, psub {
349	my ($host, $port) = AnyEvent::Socket::parse_hostport $t;	440	snd @reply, $SELF;
350
351	$LISTENER{$t} = AnyEvent::MP::Transport::mp_server $host, $port,
352	@args,
353	on_error => sub {
354	die "on_error<@_>\n";#d#
355	},
356	on_connect => sub {
357	my ($tp) = @_;
358
359	$NODE{$tp->{remote_id}} = $_[0];
360	},
361	sub {
362	my ($tp) = @_;
363
364	$NODE{"$tp->{peerhost}:$tp->{peerport}"} = $tp;
365	},
366	;	441	};
		442	};
		443
		444	=cut
		445
		446	sub psub(&) {
		447	my $cb = shift;
		448
		449	my $port = $SELF
		450	or Carp::croak "psub can only be called from within rcv or psub callbacks, not";
		451
		452	sub {
		453	local $SELF = $port;
		454
		455	if (wantarray) {
		456	my @res = eval { &$cb };
		457	_self_die if $@;
		458	@res
		459	} else {
		460	my $res = eval { &$cb };
		461	_self_die if $@;
		462	$res
		463	}
367	}	464	}
		465	}
368		466
369	$PUBLIC = 1;	467	=item $guard = mon $port, $cb->(@reason) # call $cb when $port dies
		468
		469	=item $guard = mon $port, $rcvport # kill $rcvport when $port dies
		470
		471	=item $guard = mon $port # kill $SELF when $port dies
		472
		473	=item $guard = mon $port, $rcvport, @msg # send a message when $port dies
		474
		475	Monitor the given port and do something when the port is killed or
		476	messages to it were lost, and optionally return a guard that can be used
		477	to stop monitoring again.
		478
		479	C<mon> effectively guarantees that, in the absence of hardware failures,
		480	after starting the monitor, either all messages sent to the port will
		481	arrive, or the monitoring action will be invoked after possible message
		482	loss has been detected. No messages will be lost "in between" (after
		483	the first lost message no further messages will be received by the
		484	port). After the monitoring action was invoked, further messages might get
		485	delivered again.
		486
		487	Note that monitoring-actions are one-shot: once messages are lost (and a
		488	monitoring alert was raised), they are removed and will not trigger again.
		489
		490	In the first form (callback), the callback is simply called with any
		491	number of C<@reason> elements (no @reason means that the port was deleted
		492	"normally"). Note also that I<< the callback B<must> never die >>, so use
		493	C<eval> if unsure.
		494
		495	In the second form (another port given), the other port (C<$rcvport>)
		496	will be C<kil>'ed with C<@reason>, if a @reason was specified, i.e. on
		497	"normal" kils nothing happens, while under all other conditions, the other
		498	port is killed with the same reason.
		499
		500	The third form (kill self) is the same as the second form, except that
		501	C<$rvport> defaults to C<$SELF>.
		502
		503	In the last form (message), a message of the form C<@msg, @reason> will be
		504	C<snd>.
		505
		506	As a rule of thumb, monitoring requests should always monitor a port from
		507	a local port (or callback). The reason is that kill messages might get
		508	lost, just like any other message. Another less obvious reason is that
		509	even monitoring requests can get lost (for example, when the connection
		510	to the other node goes down permanently). When monitoring a port locally
		511	these problems do not exist.
		512
		513	Example: call a given callback when C<$port> is killed.
		514
		515	mon $port, sub { warn "port died because of <@_>\n" };
		516
		517	Example: kill ourselves when C<$port> is killed abnormally.
		518
		519	mon $port;
		520
		521	Example: send us a restart message when another C<$port> is killed.
		522
		523	mon $port, $self => "restart";
		524
		525	=cut
		526
		527	sub mon {
		528	my ($nodeid, $port) = split /#/, shift, 2;
		529
		530	my $node = $NODE{$nodeid} \|\| add_node $nodeid;
		531
		532	my $cb = @_ ? shift : $SELF \|\| Carp::croak 'mon: called with one argument only, but $SELF not set,';
		533
		534	unless (ref $cb) {
		535	if (@_) {
		536	# send a kill info message
		537	my (@msg) = ($cb, @_);
		538	$cb = sub { snd @msg, @_ };
		539	} else {
		540	# simply kill other port
		541	my $port = $cb;
		542	$cb = sub { kil $port, @_ if @_ };
		543	}
		544	}
		545
		546	$node->monitor ($port, $cb);
		547
		548	defined wantarray
		549	and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }
		550	}
		551
		552	=item $guard = mon_guard $port, $ref, $ref...
		553
		554	Monitors the given C<$port> and keeps the passed references. When the port
		555	is killed, the references will be freed.
		556
		557	Optionally returns a guard that will stop the monitoring.
		558
		559	This function is useful when you create e.g. timers or other watchers and
		560	want to free them when the port gets killed (note the use of C<psub>):
		561
		562	$port->rcv (start => sub {
		563	my $timer; $timer = mon_guard $port, AE::timer 1, 1, psub {
		564	undef $timer if 0.9 < rand;
		565	});
		566	});
		567
		568	=cut
		569
		570	sub mon_guard {
		571	my ($port, @refs) = @_;
		572
		573	#TODO: mon-less form?
		574
		575	mon $port, sub { 0 && @refs }
		576	}
		577
		578	=item kil $port[, @reason]
		579
		580	Kill the specified port with the given C<@reason>.
		581
		582	If no C<@reason> is specified, then the port is killed "normally" (ports
		583	monitoring other ports will not necessarily die because a port dies
		584	"normally").
		585
		586	Otherwise, linked ports get killed with the same reason (second form of
		587	C<mon>, see above).
		588
		589	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
		590	will be reported as reason C<< die => $@ >>.
		591
		592	Transport/communication errors are reported as C<< transport_error =>
		593	$message >>.
		594
		595	=cut
		596
		597	=item $port = spawn $node, $initfunc[, @initdata]
		598
		599	Creates a port on the node C<$node> (which can also be a port ID, in which
		600	case it's the node where that port resides).
		601
		602	The port ID of the newly created port is returned immediately, and it is
		603	possible to immediately start sending messages or to monitor the port.
		604
		605	After the port has been created, the init function is called on the remote
		606	node, in the same context as a C<rcv> callback. This function must be a
		607	fully-qualified function name (e.g. C<MyApp::Chat::Server::init>). To
		608	specify a function in the main program, use C<::name>.
		609
		610	If the function doesn't exist, then the node tries to C<require>
		611	the package, then the package above the package and so on (e.g.
		612	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
		613	exists or it runs out of package names.
		614
		615	The init function is then called with the newly-created port as context
		616	object (C<$SELF>) and the C<@initdata> values as arguments.
		617
		618	A common idiom is to pass a local port, immediately monitor the spawned
		619	port, and in the remote init function, immediately monitor the passed
		620	local port. This two-way monitoring ensures that both ports get cleaned up
		621	when there is a problem.
		622
		623	Example: spawn a chat server port on C<$othernode>.
		624
		625	# this node, executed from within a port context:
		626	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;
		627	mon $server;
		628
		629	# init function on C<$othernode>
		630	sub connect {
		631	my ($srcport) = @_;
		632
		633	mon $srcport;
		634
		635	rcv $SELF, sub {
		636	...
		637	};
		638	}
		639
		640	=cut
		641
		642	sub _spawn {
		643	my $port = shift;
		644	my $init = shift;
		645
		646	local $SELF = "$NODE#$port";
		647	eval {
		648	&{ load_func $init }
		649	};
		650	_self_die if $@;
		651	}
		652
		653	sub spawn(@) {
		654	my ($nodeid, undef) = split /#/, shift, 2;
		655
		656	my $id = "$RUNIQ." . $ID++;
		657
		658	$_[0] =~ /::/
		659	or Carp::croak "spawn init function must be a fully-qualified name, caught";
		660
		661	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;
		662
		663	"$nodeid#$id"
		664	}
		665
		666	=item after $timeout, @msg
		667
		668	=item after $timeout, $callback
		669
		670	Either sends the given message, or call the given callback, after the
		671	specified number of seconds.
		672
		673	This is simply a utility function that comes in handy at times - the
		674	AnyEvent::MP author is not convinced of the wisdom of having it, though,
		675	so it may go away in the future.
		676
		677	=cut
		678
		679	sub after($@) {
		680	my ($timeout, @action) = @_;
		681
		682	my $t; $t = AE::timer $timeout, 0, sub {
		683	undef $t;
		684	ref $action[0]
		685	? $action[0]()
		686	: snd @action;
		687	};
370	}	688	}
371		689
372	=back	690	=back
373		691
374	=head1 NODE MESSAGES	692	=head1 AnyEvent::MP vs. Distributed Erlang
375		693
376	Nodes understand the following messages sent to them. Many of them take	694	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
377	arguments called C<@reply>, which will simply be used to compose a reply	695	== aemp node, Erlang process == aemp port), so many of the documents and
378	message - C<$reply[0]> is the port to reply to, C<$reply[1]> the type and	696	programming techniques employed by Erlang apply to AnyEvent::MP. Here is a
379	the remaining arguments are simply the message data.	697	sample:
		698
		699	http://www.Erlang.se/doc/programming_rules.shtml
		700	http://Erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4
		701	http://Erlang.org/download/Erlang-book-part1.pdf # chapters 5 and 6
		702	http://Erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5
		703
		704	Despite the similarities, there are also some important differences:
380		705
381	=over 4	706	=over 4
382		707
383	=cut	708	=item * Node IDs are arbitrary strings in AEMP.
384		709
385	#############################################################################	710	Erlang relies on special naming and DNS to work everywhere in the same
386	# self node code	711	way. AEMP relies on each node somehow knowing its own address(es) (e.g. by
		712	configuration or DNS), but will otherwise discover other odes itself.
387		713
388	sub _new_port($) {	714	=item * Erlang has a "remote ports are like local ports" philosophy, AEMP
389	my ($name) = @_;	715	uses "local ports are like remote ports".
390		716
391	my ($noderef, $portname) = split /#/, $name;	717	The failure modes for local ports are quite different (runtime errors
		718	only) then for remote ports - when a local port dies, you I<know> it dies,
		719	when a connection to another node dies, you know nothing about the other
		720	port.
392		721
393	$PORT{$name} =	722	Erlang pretends remote ports are as reliable as local ports, even when
394	$PORT{$portname} = {	723	they are not.
395	names => [$name, $portname],
396	};
397	}
398		724
399	$NODE{""} = new AnyEvent::MP::Node::Self noderef => $NODE;	725	AEMP encourages a "treat remote ports differently" philosophy, with local
400	_new_port "";	726	ports being the special case/exception, where transport errors cannot
		727	occur.
401		728
402	=item devnull => ...	729	=item * Erlang uses processes and a mailbox, AEMP does not queue.
403		730
404	Generic data sink/CPU heat conversion.	731	Erlang uses processes that selectively receive messages, and therefore
		732	needs a queue. AEMP is event based, queuing messages would serve no
		733	useful purpose. For the same reason the pattern-matching abilities of
		734	AnyEvent::MP are more limited, as there is little need to be able to
		735	filter messages without dequeuing them.
405		736
406	=cut	737	(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).
407		738
408	rcv "", devnull => sub { () };	739	=item * Erlang sends are synchronous, AEMP sends are asynchronous.
409		740
410	=item relay => $port, @msg	741	Sending messages in Erlang is synchronous and blocks the process (and
		742	so does not need a queue that can overflow). AEMP sends are immediate,
		743	connection establishment is handled in the background.
411		744
412	Simply forwards the message to the given port.	745	=item * Erlang suffers from silent message loss, AEMP does not.
413		746
414	=cut	747	Erlang makes few guarantees on messages delivery - messages can get lost
		748	without any of the processes realising it (i.e. you send messages a, b,
		749	and c, and the other side only receives messages a and c).
415		750
416	rcv "", relay => sub { \&snd; () };	751	AEMP guarantees correct ordering, and the guarantee that after one message
		752	is lost, all following ones sent to the same port are lost as well, until
		753	monitoring raises an error, so there are no silent "holes" in the message
		754	sequence.
417		755
418	=item eval => $string[ @reply]	756	=item * Erlang can send messages to the wrong port, AEMP does not.
419		757
420	Evaluates the given string. If C<@reply> is given, then a message of the	758	In Erlang it is quite likely that a node that restarts reuses a process ID
421	form C<@reply, $@, @evalres> is sent.	759	known to other nodes for a completely different process, causing messages
		760	destined for that process to end up in an unrelated process.
422		761
423	Example: crash another node.	762	AEMP never reuses port IDs, so old messages or old port IDs floating
		763	around in the network will not be sent to an unrelated port.
424		764
425	snd $othernode, eval => "exit";	765	=item * Erlang uses unprotected connections, AEMP uses secure
		766	authentication and can use TLS.
426		767
427	=cut	768	AEMP can use a proven protocol - TLS - to protect connections and
		769	securely authenticate nodes.
428		770
429	rcv "", eval => sub {	771	=item * The AEMP protocol is optimised for both text-based and binary
430	my (undef, $string, @reply) = @_;	772	communications.
431	my @res = eval $string;
432	snd @reply, "$@", @res if @reply;
433	()
434	};
435		773
436	=item time => @reply	774	The AEMP protocol, unlike the Erlang protocol, supports both programming
		775	language independent text-only protocols (good for debugging) and binary,
		776	language-specific serialisers (e.g. Storable). By default, unless TLS is
		777	used, the protocol is actually completely text-based.
437		778
438	Replies the the current node time to C<@reply>.	779	It has also been carefully designed to be implementable in other languages
		780	with a minimum of work while gracefully degrading functionality to make the
		781	protocol simple.
439		782
440	Example: tell the current node to send the current time to C<$myport> in a	783	=item * AEMP has more flexible monitoring options than Erlang.
441	C<timereply> message.
442		784
443	snd $NODE, time => $myport, timereply => 1, 2;	785	In Erlang, you can chose to receive I<all> exit signals as messages
444	# => snd $myport, timereply => 1, 2, <time>	786	or I<none>, there is no in-between, so monitoring single processes is
		787	difficult to implement. Monitoring in AEMP is more flexible than in
		788	Erlang, as one can choose between automatic kill, exit message or callback
		789	on a per-process basis.
445		790
446	=cut	791	=item * Erlang tries to hide remote/local connections, AEMP does not.
447		792
448	rcv "", time => sub { shift; snd @_, AE::time; () };	793	Monitoring in Erlang is not an indicator of process death/crashes, in the
		794	same way as linking is (except linking is unreliable in Erlang).
		795
		796	In AEMP, you don't "look up" registered port names or send to named ports
		797	that might or might not be persistent. Instead, you normally spawn a port
		798	on the remote node. The init function monitors you, and you monitor the
		799	remote port. Since both monitors are local to the node, they are much more
		800	reliable (no need for C<spawn_link>).
		801
		802	This also saves round-trips and avoids sending messages to the wrong port
		803	(hard to do in Erlang).
449		804
450	=back	805	=back
451		806
		807	=head1 RATIONALE
		808
		809	=over 4
		810
		811	=item Why strings for port and node IDs, why not objects?
		812
		813	We considered "objects", but found that the actual number of methods
		814	that can be called are quite low. Since port and node IDs travel over
		815	the network frequently, the serialising/deserialising would add lots of
		816	overhead, as well as having to keep a proxy object everywhere.
		817
		818	Strings can easily be printed, easily serialised etc. and need no special
		819	procedures to be "valid".
		820
		821	And as a result, a miniport consists of a single closure stored in a
		822	global hash - it can't become much cheaper.
		823
		824	=item Why favour JSON, why not a real serialising format such as Storable?
		825
		826	In fact, any AnyEvent::MP node will happily accept Storable as framing
		827	format, but currently there is no way to make a node use Storable by
		828	default (although all nodes will accept it).
		829
		830	The default framing protocol is JSON because a) JSON::XS is many times
		831	faster for small messages and b) most importantly, after years of
		832	experience we found that object serialisation is causing more problems
		833	than it solves: Just like function calls, objects simply do not travel
		834	easily over the network, mostly because they will always be a copy, so you
		835	always have to re-think your design.
		836
		837	Keeping your messages simple, concentrating on data structures rather than
		838	objects, will keep your messages clean, tidy and efficient.
		839
		840	=back
		841
452	=head1 SEE ALSO	842	=head1 SEE ALSO
		843
		844	L<AnyEvent::MP::Intro> - a gentle introduction.
		845
		846	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.
		847
		848	L<AnyEvent::MP::Global> - network maintainance and port groups, to find
		849	your applications.
453		850
454	L<AnyEvent>.	851	L<AnyEvent>.
455		852
456	=head1 AUTHOR	853	=head1 AUTHOR
457		854

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.7 by root, Sat Aug 1 15:04:30 2009 UTC vs. Revision 1.78 by root, Thu Sep 3 20:16:36 2009 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.7 by root, Sat Aug 1 15:04:30 2009 UTC vs.
Revision 1.78 by root, Thu Sep 3 20:16:36 2009 UTC