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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.68 by root, Fri Aug 28 23:06:33 2009 UTC vs.
Revision 1.87 by root, Fri Sep 11 02:32:23 2009 UTC

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

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.68 by root, Fri Aug 28 23:06:33 2009 UTC vs. Revision 1.87 by root, Fri Sep 11 02:32:23 2009 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.68 by root, Fri Aug 28 23:06:33 2009 UTC vs.
Revision 1.87 by root, Fri Sep 11 02:32:23 2009 UTC