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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.69 by root, Sun Aug 30 18:51:49 2009 UTC vs.
Revision 1.93 by root, Tue Sep 22 14:14:29 2009 UTC

…		…
1	=head1 NAME	1	=head1 NAME
2		2
3	AnyEvent::MP - multi-processing/message-passing framework	3	AnyEvent::MP - erlang-style multi-processing/message-passing framework
4		4
5	=head1 SYNOPSIS	5	=head1 SYNOPSIS
6		6
7	use AnyEvent::MP;	7	use AnyEvent::MP;
8		8
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;	15	configure;
17		16
18	# ports are message endpoints	17	# ports are message destinations
19		18
20	# sending messages	19	# sending messages
21	snd $port, type => data...;	20	snd $port, type => data...;
22	snd $port, @msg;	21	snd $port, @msg;
23	snd @msg_with_first_element_being_a_port;	22	snd @msg_with_first_element_being_a_port;
24		23
25	# creating/using ports, the simple way	24	# creating/using ports, the simple way
26	my $simple_port = port { my @msg = @_; 0 };	25	my $simple_port = port { my @msg = @_ };
27		26
28	# creating/using ports, tagged message matching	27	# creating/using ports, tagged message matching
29	my $port = port;	28	my $port = port;
30	rcv $port, ping => sub { snd $_[0], "pong"; 0 };	29	rcv $port, ping => sub { snd $_[0], "pong" };
31	rcv $port, pong => sub { warn "pong received\n"; 0 };	30	rcv $port, pong => sub { warn "pong received\n" };
32		31
33	# create a port on another node	32	# create a port on another node
34	my $port = spawn $node, $initfunc, @initdata;	33	my $port = spawn $node, $initfunc, @initdata;
35		34
36	# monitoring	35	# monitoring
37	mon $port, $cb->(@msg) # callback is invoked on death	36	mon $localport, $cb->(@msg) # callback is invoked on death
38	mon $port, $otherport # kill otherport on abnormal death	37	mon $localport, $otherport # kill otherport on abnormal death
39	mon $port, $otherport, @msg # send message on death	38	mon $localport, $otherport, @msg # send message on death
40		39
41	=head1 CURRENT STATUS	40	=head1 CURRENT STATUS
42		41
		42	bin/aemp - stable.
43	AnyEvent::MP - stable API, should work	43	AnyEvent::MP - stable API, should work.
44	AnyEvent::MP::Intro - outdated	44	AnyEvent::MP::Intro - explains most concepts.
45	AnyEvent::MP::Kernel - mostly stable	45	AnyEvent::MP::Kernel - mostly stable API.
46	AnyEvent::MP::Global - mostly stable	46	AnyEvent::MP::Global - stable API.
47	AnyEvent::MP::Node - mostly stable, but internal anyways
48	AnyEvent::MP::Transport - mostly stable, but internal anyways
49
50	stay tuned.
51		47
52	=head1 DESCRIPTION	48	=head1 DESCRIPTION
53		49
54	This module (-family) implements a simple message passing framework.	50	This module (-family) implements a simple message passing framework.
55		51
57	on the same or other hosts, and you can supervise entities remotely.	53	on the same or other hosts, and you can supervise entities remotely.
58		54
59	For an introduction to this module family, see the L<AnyEvent::MP::Intro>	55	For an introduction to this module family, see the L<AnyEvent::MP::Intro>
60	manual page and the examples under F<eg/>.	56	manual page and the examples under F<eg/>.
61		57
62	At the moment, this module family is a bit underdocumented.
63
64	=head1 CONCEPTS	58	=head1 CONCEPTS
65		59
66	=over 4	60	=over 4
67		61
68	=item port	62	=item port
69		63
70	A port is something you can send messages to (with the C<snd> function).	64	Not to be confused with a TCP port, a "port" is something you can send
		65	messages to (with the C<snd> function).
71		66
72	Ports allow you to register C<rcv> handlers that can match all or just	67	Ports allow you to register C<rcv> handlers that can match all or just
73	some messages. Messages send to ports will not be queued, regardless of	68	some messages. Messages send to ports will not be queued, regardless of
74	anything was listening for them or not.	69	anything was listening for them or not.
75		70
…		…
86		81
87	Nodes are either public (have one or more listening ports) or private	82	Nodes are either public (have one or more listening ports) or private
88	(no listening ports). Private nodes cannot talk to other private nodes	83	(no listening ports). Private nodes cannot talk to other private nodes
89	currently.	84	currently.
90		85
91	=item node ID - C<[a-za-Z0-9_\-.:]+>	86	=item node ID - C<[A-Z_][a-zA-Z0-9_\-.:]*>
92		87
93	A node ID is a string that uniquely identifies the node within a	88	A node ID is a string that uniquely identifies the node within a
94	network. Depending on the configuration used, node IDs can look like a	89	network. Depending on the configuration used, node IDs can look like a
95	hostname, a hostname and a port, or a random string. AnyEvent::MP itself	90	hostname, a hostname and a port, or a random string. AnyEvent::MP itself
96	doesn't interpret node IDs in any way.	91	doesn't interpret node IDs in any way.
…		…
100	Nodes can only talk to each other by creating some kind of connection to	95	Nodes can only talk to each other by creating some kind of connection to
101	each other. To do this, nodes should listen on one or more local transport	96	each other. To do this, nodes should listen on one or more local transport
102	endpoints - binds. Currently, only standard C<ip:port> specifications can	97	endpoints - binds. Currently, only standard C<ip:port> specifications can
103	be used, which specify TCP ports to listen on.	98	be used, which specify TCP ports to listen on.
104		99
105	=item seeds - C<host:port>	100	=item seed nodes
106		101
107	When a node starts, it knows nothing about the network. To teach the node	102	When a node starts, it knows nothing about the network. To teach the node
108	about the network it first has to contact some other node within the	103	about the network it first has to contact some other node within the
109	network. This node is called a seed.	104	network. This node is called a seed.
110		105
111	Seeds are transport endpoint(s) of as many nodes as one wants. Those nodes	106	Apart from the fact that other nodes know them as seed nodes and they have
		107	to have fixed listening addresses, seed nodes are perfectly normal nodes -
		108	any node can function as a seed node for others.
		109
		110	In addition to discovering the network, seed nodes are also used to
		111	maintain the network and to connect nodes that otherwise would have
		112	trouble connecting. They form the backbone of an AnyEvent::MP network.
		113
112	are expected to be long-running, and at least one of those should always	114	Seed nodes are expected to be long-running, and at least one seed node
113	be available. When nodes run out of connections (e.g. due to a network	115	should always be available. They should also be relatively responsive - a
114	error), they try to re-establish connections to some seednodes again to	116	seed node that blocks for long periods will slow down everybody else.
115	join the network.
116		117
117	Apart from being sued for seeding, seednodes are not special in any way -	118	=item seeds - C<host:port>
118	every public node can be a seednode.	119
		120	Seeds are transport endpoint(s) (usually a hostname/IP address and a
		121	TCP port) of nodes thta should be used as seed nodes.
		122
		123	The nodes listening on those endpoints are expected to be long-running,
		124	and at least one of those should always be available. When nodes run out
		125	of connections (e.g. due to a network error), they try to re-establish
		126	connections to some seednodes again to join the network.
119		127
120	=back	128	=back
121		129
122	=head1 VARIABLES/FUNCTIONS	130	=head1 VARIABLES/FUNCTIONS
123		131
…		…
139		147
140	our $VERSION = $AnyEvent::MP::Kernel::VERSION;	148	our $VERSION = $AnyEvent::MP::Kernel::VERSION;
141		149
142	our @EXPORT = qw(	150	our @EXPORT = qw(
143	NODE $NODE *SELF node_of after	151	NODE $NODE *SELF node_of after
144	initialise_node	152	configure
145	snd rcv mon mon_guard kil reg psub spawn	153	snd rcv mon mon_guard kil psub spawn cal
146	port	154	port
147	);	155	);
148		156
149	our $SELF;	157	our $SELF;
150		158
…		…
156		164
157	=item $thisnode = NODE / $NODE	165	=item $thisnode = NODE / $NODE
158		166
159	The C<NODE> function returns, and the C<$NODE> variable contains, the node	167	The C<NODE> function returns, and the C<$NODE> variable contains, the node
160	ID of the node running in the current process. This value is initialised by	168	ID of the node running in the current process. This value is initialised by
161	a call to C<initialise_node>.	169	a call to C<configure>.
162		170
163	=item $nodeid = node_of $port	171	=item $nodeid = node_of $port
164		172
165	Extracts and returns the node ID from a port ID or a node ID.	173	Extracts and returns the node ID from a port ID or a node ID.
166		174
167	=item initialise_node $profile_name, key => value...	175	=item configure $profile, key => value...
		176
		177	=item configure key => value...
168		178
169	Before a node can talk to other nodes on the network (i.e. enter	179	Before a node can talk to other nodes on the network (i.e. enter
170	"distributed mode") it has to initialise itself - the minimum a node needs	180	"distributed mode") it has to configure itself - the minimum a node needs
171	to know is its own name, and optionally it should know the addresses of	181	to know is its own name, and optionally it should know the addresses of
172	some other nodes in the network to discover other nodes.	182	some other nodes in the network to discover other nodes.
173		183
174	This function initialises a node - it must be called exactly once (or	184	This function configures a node - it must be called exactly once (or
175	never) before calling other AnyEvent::MP functions.	185	never) before calling other AnyEvent::MP functions.
176		186
177	The first argument is a profile name. If it is C<undef> or missing, then	187	=over 4
178	the current nodename will be used instead (i.e. F<uname -n>).
179		188
		189	=item step 1, gathering configuration from profiles
		190
180	The function first looks up the profile in the aemp configuration (see the	191	The function first looks up a profile in the aemp configuration (see the
181	L<aemp> commandline utility). the profile is calculated as follows:	192	L<aemp> commandline utility). The profile name can be specified via the
		193	named C<profile> parameter or can simply be the first parameter). If it is
		194	missing, then the nodename (F<uname -n>) will be used as profile name.
182		195
183	First, all remaining key => value pairs will be used. Then they will be	196	The profile data is then gathered as follows:
184	overwritten by any values specified in the global default configuration	197
185	(see the F<aemp> utility), then the chain of profiles selected, if	198	First, all remaining key => value pairs (all of which are conveniently
		199	undocumented at the moment) will be interpreted as configuration
		200	data. Then they will be overwritten by any values specified in the global
		201	default configuration (see the F<aemp> utility), then the chain of
		202	profiles chosen by the profile name (and any C<parent> attributes).
		203
186	any. That means that the values specified in the profile have highest	204	That means that the values specified in the profile have highest priority
187	priority and the values specified via C<initialise_node> have lowest	205	and the values specified directly via C<configure> have lowest priority,
188	priority.	206	and can only be used to specify defaults.
189		207
190	If the profile specifies a node ID, then this will become the node ID of	208	If the profile specifies a node ID, then this will become the node ID of
191	this process. If not, then the profile name will be used as node ID. The	209	this process. If not, then the profile name will be used as node ID. The
192	special node ID of C<anon/> will be replaced by a random node ID.	210	special node ID of C<anon/> will be replaced by a random node ID.
		211
		212	=item step 2, bind listener sockets
193		213
194	The next step is to look up the binds in the profile, followed by binding	214	The next step is to look up the binds in the profile, followed by binding
195	aemp protocol listeners on all binds specified (it is possible and valid	215	aemp protocol listeners on all binds specified (it is possible and valid
196	to have no binds, meaning that the node cannot be contacted form the	216	to have no binds, meaning that the node cannot be contacted form the
197	outside. This means the node cannot talk to other nodes that also have no	217	outside. This means the node cannot talk to other nodes that also have no
198	binds, but it can still talk to all "normal" nodes).	218	binds, but it can still talk to all "normal" nodes).
199		219
200	If the profile does not specify a binds list, then the node ID will be	220	If the profile does not specify a binds list, then a default of C<*> is
201	treated as if it were of the form C<host:port>, which will be resolved and	221	used, meaning the node will bind on a dynamically-assigned port on every
202	used as binds list.	222	local IP address it finds.
203		223
		224	=item step 3, connect to seed nodes
		225
204	Lastly, the seeds list from the profile is passed to the	226	As the last step, the seeds list from the profile is passed to the
205	L<AnyEvent::MP::Global> module, which will then use it to keep	227	L<AnyEvent::MP::Global> module, which will then use it to keep
206	connectivity with at least on of those seed nodes at any point in time.	228	connectivity with at least one node at any point in time.
207		229
208	Example: become a distributed node listening on the guessed noderef, or	230	=back
209	the one specified via C<aemp> for the current node. This should be the	231
		232	Example: become a distributed node using the local node name as profile.
210	most common form of invocation for "daemon"-type nodes.	233	This should be the most common form of invocation for "daemon"-type nodes.
211		234
212	initialise_node;	235	configure
213		236
214	Example: become an anonymous node. This form is often used for commandline	237	Example: become an anonymous node. This form is often used for commandline
215	clients.	238	clients.
216		239
217	initialise_node "anon/";	240	configure nodeid => "anon/";
218		241
219	Example: become a distributed node. If there is no profile of the given	242	Example: configure a node using a profile called seed, which si suitable
220	name, or no binds list was specified, resolve C<localhost:4044> and bind	243	for a seed node as it binds on all local addresses on a fixed port (4040,
221	on the resulting addresses.	244	customary for aemp).
222		245
223	initialise_node "localhost:4044";	246	# use the aemp commandline utility
		247	# aemp profile seed nodeid anon/ binds '*:4040'
		248
		249	# then use it
		250	configure profile => "seed";
		251
		252	# or simply use aemp from the shell again:
		253	# aemp run profile seed
		254
		255	# or provide a nicer-to-remember nodeid
		256	# aemp run profile seed nodeid "$(hostname)"
224		257
225	=item $SELF	258	=item $SELF
226		259
227	Contains the current port id while executing C<rcv> callbacks or C<psub>	260	Contains the current port id while executing C<rcv> callbacks or C<psub>
228	blocks.	261	blocks.
…		…
350		383
351	=cut	384	=cut
352		385
353	sub rcv($@) {	386	sub rcv($@) {
354	my $port = shift;	387	my $port = shift;
355	my ($noderef, $portid) = split /#/, $port, 2;	388	my ($nodeid, $portid) = split /#/, $port, 2;
356		389
357	$NODE{$noderef} == $NODE{""}	390	$NODE{$nodeid} == $NODE{""}
358	or Carp::croak "$port: rcv can only be called on local ports, caught";	391	or Carp::croak "$port: rcv can only be called on local ports, caught";
359		392
360	while (@_) {	393	while (@_) {
361	if (ref $_[0]) {	394	if (ref $_[0]) {
362	if (my $self = $PORT_DATA{$portid}) {	395	if (my $self = $PORT_DATA{$portid}) {
…		…
453		486
454	Monitor the given port and do something when the port is killed or	487	Monitor the given port and do something when the port is killed or
455	messages to it were lost, and optionally return a guard that can be used	488	messages to it were lost, and optionally return a guard that can be used
456	to stop monitoring again.	489	to stop monitoring again.
457		490
		491	In the first form (callback), the callback is simply called with any
		492	number of C<@reason> elements (no @reason means that the port was deleted
		493	"normally"). Note also that I<< the callback B<must> never die >>, so use
		494	C<eval> if unsure.
		495
		496	In the second form (another port given), the other port (C<$rcvport>)
		497	will be C<kil>'ed with C<@reason>, if a @reason was specified, i.e. on
		498	"normal" kils nothing happens, while under all other conditions, the other
		499	port is killed with the same reason.
		500
		501	The third form (kill self) is the same as the second form, except that
		502	C<$rvport> defaults to C<$SELF>.
		503
		504	In the last form (message), a message of the form C<@msg, @reason> will be
		505	C<snd>.
		506
		507	Monitoring-actions are one-shot: once messages are lost (and a monitoring
		508	alert was raised), they are removed and will not trigger again.
		509
		510	As a rule of thumb, monitoring requests should always monitor a port from
		511	a local port (or callback). The reason is that kill messages might get
		512	lost, just like any other message. Another less obvious reason is that
		513	even monitoring requests can get lost (for example, when the connection
		514	to the other node goes down permanently). When monitoring a port locally
		515	these problems do not exist.
		516
458	C<mon> effectively guarantees that, in the absence of hardware failures,	517	C<mon> effectively guarantees that, in the absence of hardware failures,
459	after starting the monitor, either all messages sent to the port will	518	after starting the monitor, either all messages sent to the port will
460	arrive, or the monitoring action will be invoked after possible message	519	arrive, or the monitoring action will be invoked after possible message
461	loss has been detected. No messages will be lost "in between" (after	520	loss has been detected. No messages will be lost "in between" (after
462	the first lost message no further messages will be received by the	521	the first lost message no further messages will be received by the
463	port). After the monitoring action was invoked, further messages might get	522	port). After the monitoring action was invoked, further messages might get
464	delivered again.	523	delivered again.
465		524
466	Note that monitoring-actions are one-shot: once messages are lost (and a	525	Inter-host-connection timeouts and monitoring depend on the transport
467	monitoring alert was raised), they are removed and will not trigger again.	526	used. The only transport currently implemented is TCP, and AnyEvent::MP
		527	relies on TCP to detect node-downs (this can take 10-15 minutes on a
		528	non-idle connection, and usually around two hours for idle conenctions).
468		529
469	In the first form (callback), the callback is simply called with any	530	This means that monitoring is good for program errors and cleaning up
470	number of C<@reason> elements (no @reason means that the port was deleted	531	stuff eventually, but they are no replacement for a timeout when you need
471	"normally"). Note also that I<< the callback B<must> never die >>, so use	532	to ensure some maximum latency.
472	C<eval> if unsure.
473
474	In the second form (another port given), the other port (C<$rcvport>)
475	will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on
476	"normal" kils nothing happens, while under all other conditions, the other
477	port is killed with the same reason.
478
479	The third form (kill self) is the same as the second form, except that
480	C<$rvport> defaults to C<$SELF>.
481
482	In the last form (message), a message of the form C<@msg, @reason> will be
483	C<snd>.
484
485	As a rule of thumb, monitoring requests should always monitor a port from
486	a local port (or callback). The reason is that kill messages might get
487	lost, just like any other message. Another less obvious reason is that
488	even monitoring requests can get lost (for exmaple, when the connection
489	to the other node goes down permanently). When monitoring a port locally
490	these problems do not exist.
491		533
492	Example: call a given callback when C<$port> is killed.	534	Example: call a given callback when C<$port> is killed.
493		535
494	mon $port, sub { warn "port died because of <@_>\n" };	536	mon $port, sub { warn "port died because of <@_>\n" };
495		537
…		…
502	mon $port, $self => "restart";	544	mon $port, $self => "restart";
503		545
504	=cut	546	=cut
505		547
506	sub mon {	548	sub mon {
507	my ($noderef, $port) = split /#/, shift, 2;	549	my ($nodeid, $port) = split /#/, shift, 2;
508		550
509	my $node = $NODE{$noderef} \|\| add_node $noderef;	551	my $node = $NODE{$nodeid} \|\| add_node $nodeid;
510		552
511	my $cb = @_ ? shift : $SELF \|\| Carp::croak 'mon: called with one argument only, but $SELF not set,';	553	my $cb = @_ ? shift : $SELF \|\| Carp::croak 'mon: called with one argument only, but $SELF not set,';
512		554
513	unless (ref $cb) {	555	unless (ref $cb) {
514	if (@_) {	556	if (@_) {
…		…
523	}	565	}
524		566
525	$node->monitor ($port, $cb);	567	$node->monitor ($port, $cb);
526		568
527	defined wantarray	569	defined wantarray
		570	and $cb += 0
528	and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }	571	and AnyEvent::Util::guard { $node->unmonitor ($port, $cb) }
529	}	572	}
530		573
531	=item $guard = mon_guard $port, $ref, $ref...	574	=item $guard = mon_guard $port, $ref, $ref...
532		575
…		…
590	the package, then the package above the package and so on (e.g.	633	the package, then the package above the package and so on (e.g.
591	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function	634	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
592	exists or it runs out of package names.	635	exists or it runs out of package names.
593		636
594	The init function is then called with the newly-created port as context	637	The init function is then called with the newly-created port as context
595	object (C<$SELF>) and the C<@initdata> values as arguments.	638	object (C<$SELF>) and the C<@initdata> values as arguments. It I<must>
		639	call one of the C<rcv> functions to set callbacks on C<$SELF>, otherwise
		640	the port might not get created.
596		641
597	A common idiom is to pass a local port, immediately monitor the spawned	642	A common idiom is to pass a local port, immediately monitor the spawned
598	port, and in the remote init function, immediately monitor the passed	643	port, and in the remote init function, immediately monitor the passed
599	local port. This two-way monitoring ensures that both ports get cleaned up	644	local port. This two-way monitoring ensures that both ports get cleaned up
600	when there is a problem.	645	when there is a problem.
601		646
		647	C<spawn> guarantees that the C<$initfunc> has no visible effects on the
		648	caller before C<spawn> returns (by delaying invocation when spawn is
		649	called for the local node).
		650
602	Example: spawn a chat server port on C<$othernode>.	651	Example: spawn a chat server port on C<$othernode>.
603		652
604	# this node, executed from within a port context:	653	# this node, executed from within a port context:
605	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;	654	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;
606	mon $server;	655	mon $server;
…		…
620		669
621	sub _spawn {	670	sub _spawn {
622	my $port = shift;	671	my $port = shift;
623	my $init = shift;	672	my $init = shift;
624		673
		674	# rcv will create the actual port
625	local $SELF = "$NODE#$port";	675	local $SELF = "$NODE#$port";
626	eval {	676	eval {
627	&{ load_func $init }	677	&{ load_func $init }
628	};	678	};
629	_self_die if $@;	679	_self_die if $@;
630	}	680	}
631		681
632	sub spawn(@) {	682	sub spawn(@) {
633	my ($noderef, undef) = split /#/, shift, 2;	683	my ($nodeid, undef) = split /#/, shift, 2;
634		684
635	my $id = "$RUNIQ." . $ID++;	685	my $id = "$RUNIQ." . $ID++;
636		686
637	$_[0] =~ /::/	687	$_[0] =~ /::/
638	or Carp::croak "spawn init function must be a fully-qualified name, caught";	688	or Carp::croak "spawn init function must be a fully-qualified name, caught";
639		689
640	snd_to_func $noderef, "AnyEvent::MP::_spawn" => $id, @_;	690	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;
641		691
642	"$noderef#$id"	692	"$nodeid#$id"
643	}	693	}
644		694
645	=item after $timeout, @msg	695	=item after $timeout, @msg
646		696
647	=item after $timeout, $callback	697	=item after $timeout, $callback
…		…
664	? $action[0]()	714	? $action[0]()
665	: snd @action;	715	: snd @action;
666	};	716	};
667	}	717	}
668		718
		719	=item cal $port, @msg, $callback[, $timeout]
		720
		721	A simple form of RPC - sends a message to the given C<$port> with the
		722	given contents (C<@msg>), but adds a reply port to the message.
		723
		724	The reply port is created temporarily just for the purpose of receiving
		725	the reply, and will be C<kil>ed when no longer needed.
		726
		727	A reply message sent to the port is passed to the C<$callback> as-is.
		728
		729	If an optional time-out (in seconds) is given and it is not C<undef>,
		730	then the callback will be called without any arguments after the time-out
		731	elapsed and the port is C<kil>ed.
		732
		733	If no time-out is given, then the local port will monitor the remote port
		734	instead, so it eventually gets cleaned-up.
		735
		736	Currently this function returns the temporary port, but this "feature"
		737	might go in future versions unless you can make a convincing case that
		738	this is indeed useful for something.
		739
		740	=cut
		741
		742	sub cal(@) {
		743	my $timeout = ref $_[-1] ? undef : pop;
		744	my $cb = pop;
		745
		746	my $port = port {
		747	undef $timeout;
		748	kil $SELF;
		749	&$cb;
		750	};
		751
		752	if (defined $timeout) {
		753	$timeout = AE::timer $timeout, 0, sub {
		754	undef $timeout;
		755	kil $port;
		756	$cb->();
		757	};
		758	} else {
		759	mon $_[0], sub {
		760	kil $port;
		761	$cb->();
		762	};
		763	}
		764
		765	push @_, $port;
		766	&snd;
		767
		768	$port
		769	}
		770
669	=back	771	=back
670		772
671	=head1 AnyEvent::MP vs. Distributed Erlang	773	=head1 AnyEvent::MP vs. Distributed Erlang
672		774
673	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node	775	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
…		…
686		788
687	=item * Node IDs are arbitrary strings in AEMP.	789	=item * Node IDs are arbitrary strings in AEMP.
688		790
689	Erlang relies on special naming and DNS to work everywhere in the same	791	Erlang relies on special naming and DNS to work everywhere in the same
690	way. AEMP relies on each node somehow knowing its own address(es) (e.g. by	792	way. AEMP relies on each node somehow knowing its own address(es) (e.g. by
691	configuraiton or DNS), but will otherwise discover other odes itself.	793	configuration or DNS), but will otherwise discover other odes itself.
692		794
693	=item * Erlang has a "remote ports are like local ports" philosophy, AEMP	795	=item * Erlang has a "remote ports are like local ports" philosophy, AEMP
694	uses "local ports are like remote ports".	796	uses "local ports are like remote ports".
695		797
696	The failure modes for local ports are quite different (runtime errors	798	The failure modes for local ports are quite different (runtime errors
…		…
709		811
710	Erlang uses processes that selectively receive messages, and therefore	812	Erlang uses processes that selectively receive messages, and therefore
711	needs a queue. AEMP is event based, queuing messages would serve no	813	needs a queue. AEMP is event based, queuing messages would serve no
712	useful purpose. For the same reason the pattern-matching abilities of	814	useful purpose. For the same reason the pattern-matching abilities of
713	AnyEvent::MP are more limited, as there is little need to be able to	815	AnyEvent::MP are more limited, as there is little need to be able to
714	filter messages without dequeing them.	816	filter messages without dequeuing them.
715		817
716	(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).	818	(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).
717		819
718	=item * Erlang sends are synchronous, AEMP sends are asynchronous.	820	=item * Erlang sends are synchronous, AEMP sends are asynchronous.
719		821
…		…
825	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.	927	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.
826		928
827	L<AnyEvent::MP::Global> - network maintainance and port groups, to find	929	L<AnyEvent::MP::Global> - network maintainance and port groups, to find
828	your applications.	930	your applications.
829		931
		932	L<AnyEvent::MP::LogCatcher> - simple service to display log messages from
		933	all nodes.
		934
830	L<AnyEvent>.	935	L<AnyEvent>.
831		936
832	=head1 AUTHOR	937	=head1 AUTHOR
833		938
834	Marc Lehmann <schmorp@schmorp.de>	939	Marc Lehmann <schmorp@schmorp.de>

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.69 by root, Sun Aug 30 18:51:49 2009 UTC vs. Revision 1.93 by root, Tue Sep 22 14:14:29 2009 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.69 by root, Sun Aug 30 18:51:49 2009 UTC vs.
Revision 1.93 by root, Tue Sep 22 14:14:29 2009 UTC