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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.100 by root, Fri Oct 2 20:41:56 2009 UTC vs.
Revision 1.123 by root, Thu Mar 1 19:37:59 2012 UTC

…		…
30	rcv $port, pong => sub { warn "pong received\n" };	30	rcv $port, pong => sub { warn "pong received\n" };
31		31
32	# create a port on another node	32	# create a port on another node
33	my $port = spawn $node, $initfunc, @initdata;	33	my $port = spawn $node, $initfunc, @initdata;
34		34
		35	# destroy a port again
		36	kil $port; # "normal" kill
		37	kil $port, my_error => "everything is broken"; # error kill
		38
35	# monitoring	39	# monitoring
36	mon $localport, $cb->(@msg) # callback is invoked on death	40	mon $localport, $cb->(@msg) # callback is invoked on death
37	mon $localport, $otherport # kill otherport on abnormal death	41	mon $localport, $otherport # kill otherport on abnormal death
38	mon $localport, $otherport, @msg # send message on death	42	mon $localport, $otherport, @msg # send message on death
		43
		44	# temporarily execute code in port context
		45	peval $port, sub { die "kill the port!" };
		46
		47	# execute callbacks in $SELF port context
		48	my $timer = AE::timer 1, 0, psub {
		49	die "kill the port, delayed";
		50	};
39		51
40	=head1 CURRENT STATUS	52	=head1 CURRENT STATUS
41		53
42	bin/aemp - stable.	54	bin/aemp - stable.
43	AnyEvent::MP - stable API, should work.	55	AnyEvent::MP - stable API, should work.
…		…
66		78
67	Ports allow you to register C<rcv> handlers that can match all or just	79	Ports allow you to register C<rcv> handlers that can match all or just
68	some messages. Messages send to ports will not be queued, regardless of	80	some messages. Messages send to ports will not be queued, regardless of
69	anything was listening for them or not.	81	anything was listening for them or not.
70		82
		83	Ports are represented by (printable) strings called "port IDs".
		84
71	=item port ID - C<nodeid#portname>	85	=item port ID - C<nodeid#portname>
72		86
73	A port ID is the concatenation of a node ID, a hash-mark (C<#>) as	87	A port ID is the concatenation of a node ID, a hash-mark (C<#>)
74	separator, and a port name (a printable string of unspecified format).	88	as separator, and a port name (a printable string of unspecified
		89	format created by AnyEvent::MP).
75		90
76	=item node	91	=item node
77		92
78	A node is a single process containing at least one port - the node port,	93	A node is a single process containing at least one port - the node port,
79	which enables nodes to manage each other remotely, and to create new	94	which enables nodes to manage each other remotely, and to create new
80	ports.	95	ports.
81		96
82	Nodes are either public (have one or more listening ports) or private	97	Nodes are either public (have one or more listening ports) or private
83	(no listening ports). Private nodes cannot talk to other private nodes	98	(no listening ports). Private nodes cannot talk to other private nodes
84	currently.	99	currently, but all nodes can talk to public nodes.
85		100
		101	Nodes is represented by (printable) strings called "node IDs".
		102
86	=item node ID - C<[A-Z_][a-zA-Z0-9_\-.:]*>	103	=item node ID - C<[A-Za-z0-9_\-.:]*>
87		104
88	A node ID is a string that uniquely identifies the node within a	105	A node ID is a string that uniquely identifies the node within a
89	network. Depending on the configuration used, node IDs can look like a	106	network. Depending on the configuration used, node IDs can look like a
90	hostname, a hostname and a port, or a random string. AnyEvent::MP itself	107	hostname, a hostname and a port, or a random string. AnyEvent::MP itself
91	doesn't interpret node IDs in any way.	108	doesn't interpret node IDs in any way except to uniquely identify a node.
92		109
93	=item binds - C<ip:port>	110	=item binds - C<ip:port>
94		111
95	Nodes can only talk to each other by creating some kind of connection to	112	Nodes can only talk to each other by creating some kind of connection to
96	each other. To do this, nodes should listen on one or more local transport	113	each other. To do this, nodes should listen on one or more local transport
		114	endpoints - binds.
		115
97	endpoints - binds. Currently, only standard C<ip:port> specifications can	116	Currently, only standard C<ip:port> specifications can be used, which
98	be used, which specify TCP ports to listen on.	117	specify TCP ports to listen on. So a bind is basically just a tcp socket
		118	in listening mode thta accepts conenctions form other nodes.
99		119
100	=item seed nodes	120	=item seed nodes
101		121
102	When a node starts, it knows nothing about the network. To teach the node	122	When a node starts, it knows nothing about the network it is in - it
103	about the network it first has to contact some other node within the	123	needs to connect to at least one other node that is already in the
104	network. This node is called a seed.	124	network. These other nodes are called "seed nodes".
105		125
106	Apart from the fact that other nodes know them as seed nodes and they have	126	Seed nodes themselves are not special - they are seed nodes only because
107	to have fixed listening addresses, seed nodes are perfectly normal nodes -	127	some other node I<uses> them as such, but any node can be used as seed
108	any node can function as a seed node for others.	128	node for other nodes, and eahc node cna use a different set of seed nodes.
109		129
110	In addition to discovering the network, seed nodes are also used to	130	In addition to discovering the network, seed nodes are also used to
111	maintain the network and to connect nodes that otherwise would have	131	maintain the network - all nodes using the same seed node form are part of
112	trouble connecting. They form the backbone of an AnyEvent::MP network.	132	the same network. If a network is split into multiple subnets because e.g.
		133	the network link between the parts goes down, then using the same seed
		134	nodes for all nodes ensures that eventually the subnets get merged again.
113		135
114	Seed nodes are expected to be long-running, and at least one seed node	136	Seed nodes are expected to be long-running, and at least one seed node
115	should always be available. They should also be relatively responsive - a	137	should always be available. They should also be relatively responsive - a
116	seed node that blocks for long periods will slow down everybody else.	138	seed node that blocks for long periods will slow down everybody else.
117		139
		140	For small networks, it's best if every node uses the same set of seed
		141	nodes. For large networks, it can be useful to specify "regional" seed
		142	nodes for most nodes in an area, and use all seed nodes as seed nodes for
		143	each other. What's important is that all seed nodes connections form a
		144	complete graph, so that the network cannot split into separate subnets
		145	forever.
		146
		147	Seed nodes are represented by seed IDs.
		148
118	=item seeds - C<host:port>	149	=item seed IDs - C<host:port>
119		150
120	Seeds are transport endpoint(s) (usually a hostname/IP address and a	151	Seed IDs are transport endpoint(s) (usually a hostname/IP address and a
121	TCP port) of nodes that should be used as seed nodes.	152	TCP port) of nodes that should be used as seed nodes.
122		153
123	The nodes listening on those endpoints are expected to be long-running,	154	=item global nodes
124	and at least one of those should always be available. When nodes run out	155
125	of connections (e.g. due to a network error), they try to re-establish	156	An AEMP network needs a discovery service - nodes need to know how to
126	connections to some seednodes again to join the network.	157	connect to other nodes they only know by name. In addition, AEMP offers a
		158	distributed "group database", which maps group names to a list of strings
		159	- for example, to register worker ports.
		160
		161	A network needs at least one global node to work, and allows every node to
		162	be a global node.
		163
		164	Any node that loads the L<AnyEvent::MP::Global> module becomes a global
		165	node and tries to keep connections to all other nodes. So while it can
		166	make sense to make every node "global" in small networks, it usually makes
		167	sense to only make seed nodes into global nodes in large networks (nodes
		168	keep connections to seed nodes and global nodes, so makign them the same
		169	reduces overhead).
127		170
128	=back	171	=back
129		172
130	=head1 VARIABLES/FUNCTIONS	173	=head1 VARIABLES/FUNCTIONS
131		174
…		…
133		176
134	=cut	177	=cut
135		178
136	package AnyEvent::MP;	179	package AnyEvent::MP;
137		180
		181	use AnyEvent::MP::Config ();
138	use AnyEvent::MP::Kernel;	182	use AnyEvent::MP::Kernel;
		183	use AnyEvent::MP::Kernel qw(%NODE %PORT %PORT_DATA $UNIQ $RUNIQ $ID);
139		184
140	use common::sense;	185	use common::sense;
141		186
142	use Carp ();	187	use Carp ();
143		188
144	use AE ();	189	use AE ();
145		190
146	use base "Exporter";	191	use base "Exporter";
147		192
148	our $VERSION = 1.21;	193	our $VERSION = $AnyEvent::MP::Config::VERSION;
149		194
150	our @EXPORT = qw(	195	our @EXPORT = qw(
151	NODE $NODE *SELF node_of after	196	NODE $NODE *SELF node_of after
152	configure	197	configure
153	snd rcv mon mon_guard kil psub spawn cal	198	snd rcv mon mon_guard kil psub peval spawn cal
154	port	199	port
155	);	200	);
156		201
157	our $SELF;	202	our $SELF;
158		203
…		…
181	to know is its own name, and optionally it should know the addresses of	226	to know is its own name, and optionally it should know the addresses of
182	some other nodes in the network to discover other nodes.	227	some other nodes in the network to discover other nodes.
183		228
184	This function configures a node - it must be called exactly once (or	229	This function configures a node - it must be called exactly once (or
185	never) before calling other AnyEvent::MP functions.	230	never) before calling other AnyEvent::MP functions.
		231
		232	The key/value pairs are basically the same ones as documented for the
		233	F<aemp> command line utility (sans the set/del prefix), with two additions:
		234
		235	=over 4
		236
		237	=item norc => $boolean (default false)
		238
		239	If true, then the rc file (e.g. F<~/.perl-anyevent-mp>) will I<not>
		240	be consulted - all configuraiton options must be specified in the
		241	C<configure> call.
		242
		243	=item force => $boolean (default false)
		244
		245	IF true, then the values specified in the C<configure> will take
		246	precedence over any values configured via the rc file. The default is for
		247	the rc file to override any options specified in the program.
		248
		249	=back
186		250
187	=over 4	251	=over 4
188		252
189	=item step 1, gathering configuration from profiles	253	=item step 1, gathering configuration from profiles
190		254
…		…
204	That means that the values specified in the profile have highest priority	268	That means that the values specified in the profile have highest priority
205	and the values specified directly via C<configure> have lowest priority,	269	and the values specified directly via C<configure> have lowest priority,
206	and can only be used to specify defaults.	270	and can only be used to specify defaults.
207		271
208	If the profile specifies a node ID, then this will become the node ID of	272	If the profile specifies a node ID, then this will become the node ID of
209	this process. If not, then the profile name will be used as node ID. The	273	this process. If not, then the profile name will be used as node ID, with
210	special node ID of C<anon/> will be replaced by a random node ID.	274	a slash (C</>) attached.
		275
		276	If the node ID (or profile name) ends with a slash (C</>), then a random
		277	string is appended to make it unique.
211		278
212	=item step 2, bind listener sockets	279	=item step 2, bind listener sockets
213		280
214	The next step is to look up the binds in the profile, followed by binding	281	The next step is to look up the binds in the profile, followed by binding
215	aemp protocol listeners on all binds specified (it is possible and valid	282	aemp protocol listeners on all binds specified (it is possible and valid
…		…
221	used, meaning the node will bind on a dynamically-assigned port on every	288	used, meaning the node will bind on a dynamically-assigned port on every
222	local IP address it finds.	289	local IP address it finds.
223		290
224	=item step 3, connect to seed nodes	291	=item step 3, connect to seed nodes
225		292
226	As the last step, the seeds list from the profile is passed to the	293	As the last step, the seed ID list from the profile is passed to the
227	L<AnyEvent::MP::Global> module, which will then use it to keep	294	L<AnyEvent::MP::Global> module, which will then use it to keep
228	connectivity with at least one node at any point in time.	295	connectivity with at least one node at any point in time.
229		296
230	=back	297	=back
231		298
…		…
237	Example: become an anonymous node. This form is often used for commandline	304	Example: become an anonymous node. This form is often used for commandline
238	clients.	305	clients.
239		306
240	configure nodeid => "anon/";	307	configure nodeid => "anon/";
241		308
242	Example: configure a node using a profile called seed, which si suitable	309	Example: configure a node using a profile called seed, which is suitable
243	for a seed node as it binds on all local addresses on a fixed port (4040,	310	for a seed node as it binds on all local addresses on a fixed port (4040,
244	customary for aemp).	311	customary for aemp).
245		312
246	# use the aemp commandline utility	313	# use the aemp commandline utility
247	# aemp profile seed nodeid anon/ binds '*:4040'	314	# aemp profile seed binds '*:4040'
248		315
249	# then use it	316	# then use it
250	configure profile => "seed";	317	configure profile => "seed";
251		318
252	# or simply use aemp from the shell again:	319	# or simply use aemp from the shell again:
…		…
322	sub _kilme {	389	sub _kilme {
323	die "received message on port without callback";	390	die "received message on port without callback";
324	}	391	}
325		392
326	sub port(;&) {	393	sub port(;&) {
327	my $id = "$UNIQ." . $ID++;	394	my $id = $UNIQ . ++$ID;
328	my $port = "$NODE#$id";	395	my $port = "$NODE#$id";
329		396
330	rcv $port, shift \|\| \&_kilme;	397	rcv $port, shift \|\| \&_kilme;
331		398
332	$port	399	$port
…		…
371	msg1 => sub { ... },	438	msg1 => sub { ... },
372	...	439	...
373	;	440	;
374		441
375	Example: temporarily register a rcv callback for a tag matching some port	442	Example: temporarily register a rcv callback for a tag matching some port
376	(e.g. for a rpc reply) and unregister it after a message was received.	443	(e.g. for an rpc reply) and unregister it after a message was received.
377		444
378	rcv $port, $otherport => sub {	445	rcv $port, $otherport => sub {
379	my @reply = @_;	446	my @reply = @_;
380		447
381	rcv $SELF, $otherport;	448	rcv $SELF, $otherport;
…		…
394	if (ref $_[0]) {	461	if (ref $_[0]) {
395	if (my $self = $PORT_DATA{$portid}) {	462	if (my $self = $PORT_DATA{$portid}) {
396	"AnyEvent::MP::Port" eq ref $self	463	"AnyEvent::MP::Port" eq ref $self
397	or Carp::croak "$port: rcv can only be called on message matching ports, caught";	464	or Carp::croak "$port: rcv can only be called on message matching ports, caught";
398		465
399	$self->[2] = shift;	466	$self->[0] = shift;
400	} else {	467	} else {
401	my $cb = shift;	468	my $cb = shift;
402	$PORT{$portid} = sub {	469	$PORT{$portid} = sub {
403	local $SELF = $port;	470	local $SELF = $port;
404	eval { &$cb }; _self_die if $@;	471	eval { &$cb }; _self_die if $@;
405	};	472	};
406	}	473	}
407	} elsif (defined $_[0]) {	474	} elsif (defined $_[0]) {
408	my $self = $PORT_DATA{$portid} \|\|= do {	475	my $self = $PORT_DATA{$portid} \|\|= do {
409	my $self = bless [$PORT{$port} \|\| sub { }, { }, $port], "AnyEvent::MP::Port";	476	my $self = bless [$PORT{$portid} \|\| sub { }, { }, $port], "AnyEvent::MP::Port";
410		477
411	$PORT{$portid} = sub {	478	$PORT{$portid} = sub {
412	local $SELF = $port;	479	local $SELF = $port;
413		480
414	if (my $cb = $self->[1]{$_[0]}) {	481	if (my $cb = $self->[1]{$_[0]}) {
…		…
436	}	503	}
437		504
438	$port	505	$port
439	}	506	}
440		507
		508	=item peval $port, $coderef[, @args]
		509
		510	Evaluates the given C<$codref> within the contetx of C<$port>, that is,
		511	when the code throews an exception the C<$port> will be killed.
		512
		513	Any remaining args will be passed to the callback. Any return values will
		514	be returned to the caller.
		515
		516	This is useful when you temporarily want to execute code in the context of
		517	a port.
		518
		519	Example: create a port and run some initialisation code in it's context.
		520
		521	my $port = port { ... };
		522
		523	peval $port, sub {
		524	init
		525	or die "unable to init";
		526	};
		527
		528	=cut
		529
		530	sub peval($$) {
		531	local $SELF = shift;
		532	my $cb = shift;
		533
		534	if (wantarray) {
		535	my @res = eval { &$cb };
		536	_self_die if $@;
		537	@res
		538	} else {
		539	my $res = eval { &$cb };
		540	_self_die if $@;
		541	$res
		542	}
		543	}
		544
441	=item $closure = psub { BLOCK }	545	=item $closure = psub { BLOCK }
442		546
443	Remembers C<$SELF> and creates a closure out of the BLOCK. When the	547	Remembers C<$SELF> and creates a closure out of the BLOCK. When the
444	closure is executed, sets up the environment in the same way as in C<rcv>	548	closure is executed, sets up the environment in the same way as in C<rcv>
445	callbacks, i.e. runtime errors will cause the port to get C<kil>ed.	549	callbacks, i.e. runtime errors will cause the port to get C<kil>ed.
		550
		551	The effect is basically as if it returned C<< sub { peval $SELF, sub {
		552	BLOCK }, @_ } >>.
446		553
447	This is useful when you register callbacks from C<rcv> callbacks:	554	This is useful when you register callbacks from C<rcv> callbacks:
448		555
449	rcv delayed_reply => sub {	556	rcv delayed_reply => sub {
450	my ($delay, @reply) = @_;	557	my ($delay, @reply) = @_;
…		…
598		705
599	=item kil $port[, @reason]	706	=item kil $port[, @reason]
600		707
601	Kill the specified port with the given C<@reason>.	708	Kill the specified port with the given C<@reason>.
602		709
603	If no C<@reason> is specified, then the port is killed "normally" (ports	710	If no C<@reason> is specified, then the port is killed "normally" -
604	monitoring other ports will not necessarily die because a port dies	711	monitor callback will be invoked, but the kil will not cause linked ports
605	"normally").	712	(C<mon $mport, $lport> form) to get killed.
606		713
607	Otherwise, linked ports get killed with the same reason (second form of	714	If a C<@reason> is specified, then linked ports (C<mon $mport, $lport>
608	C<mon>, see above).	715	form) get killed with the same reason.
609		716
610	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks	717	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
611	will be reported as reason C<< die => $@ >>.	718	will be reported as reason C<< die => $@ >>.
612		719
613	Transport/communication errors are reported as C<< transport_error =>	720	Transport/communication errors are reported as C<< transport_error =>
…		…
679	}	786	}
680		787
681	sub spawn(@) {	788	sub spawn(@) {
682	my ($nodeid, undef) = split /#/, shift, 2;	789	my ($nodeid, undef) = split /#/, shift, 2;
683		790
684	my $id = "$RUNIQ." . $ID++;	791	my $id = $RUNIQ . ++$ID;
685		792
686	$_[0] =~ /::/	793	$_[0] =~ /::/
687	or Carp::croak "spawn init function must be a fully-qualified name, caught";	794	or Carp::croak "spawn init function must be a fully-qualified name, caught";
688		795
689	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;	796	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;
690		797
691	"$nodeid#$id"	798	"$nodeid#$id"
692	}	799	}
		800
693		801
694	=item after $timeout, @msg	802	=item after $timeout, @msg
695		803
696	=item after $timeout, $callback	804	=item after $timeout, $callback
697		805
…		…
807	ports being the special case/exception, where transport errors cannot	915	ports being the special case/exception, where transport errors cannot
808	occur.	916	occur.
809		917
810	=item * Erlang uses processes and a mailbox, AEMP does not queue.	918	=item * Erlang uses processes and a mailbox, AEMP does not queue.
811		919
812	Erlang uses processes that selectively receive messages, and therefore	920	Erlang uses processes that selectively receive messages out of order, and
813	needs a queue. AEMP is event based, queuing messages would serve no	921	therefore needs a queue. AEMP is event based, queuing messages would serve
814	useful purpose. For the same reason the pattern-matching abilities of	922	no useful purpose. For the same reason the pattern-matching abilities
815	AnyEvent::MP are more limited, as there is little need to be able to	923	of AnyEvent::MP are more limited, as there is little need to be able to
816	filter messages without dequeuing them.	924	filter messages without dequeuing them.
817		925
818	(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).	926	This is not a philosophical difference, but simply stems from AnyEvent::MP
		927	being event-based, while Erlang is process-based.
		928
		929	You cna have a look at L<Coro::MP> for a more Erlang-like process model on
		930	top of AEMP and Coro threads.
819		931
820	=item * Erlang sends are synchronous, AEMP sends are asynchronous.	932	=item * Erlang sends are synchronous, AEMP sends are asynchronous.
821		933
822	Sending messages in Erlang is synchronous and blocks the process (and	934	Sending messages in Erlang is synchronous and blocks the process until
		935	a conenction has been established and the message sent (and so does not
823	so does not need a queue that can overflow). AEMP sends are immediate,	936	need a queue that can overflow). AEMP sends return immediately, connection
824	connection establishment is handled in the background.	937	establishment is handled in the background.
825		938
826	=item * Erlang suffers from silent message loss, AEMP does not.	939	=item * Erlang suffers from silent message loss, AEMP does not.
827		940
828	Erlang implements few guarantees on messages delivery - messages can get	941	Erlang implements few guarantees on messages delivery - messages can get
829	lost without any of the processes realising it (i.e. you send messages a,	942	lost without any of the processes realising it (i.e. you send messages a,
830	b, and c, and the other side only receives messages a and c).	943	b, and c, and the other side only receives messages a and c).
831		944
832	AEMP guarantees correct ordering, and the guarantee that after one message	945	AEMP guarantees (modulo hardware errors) correct ordering, and the
833	is lost, all following ones sent to the same port are lost as well, until	946	guarantee that after one message is lost, all following ones sent to the
834	monitoring raises an error, so there are no silent "holes" in the message	947	same port are lost as well, until monitoring raises an error, so there are
835	sequence.	948	no silent "holes" in the message sequence.
		949
		950	If you want your software to be very reliable, you have to cope with
		951	corrupted and even out-of-order messages in both Erlang and AEMP. AEMP
		952	simply tries to work better in common error cases, such as when a network
		953	link goes down.
836		954
837	=item * Erlang can send messages to the wrong port, AEMP does not.	955	=item * Erlang can send messages to the wrong port, AEMP does not.
838		956
839	In Erlang it is quite likely that a node that restarts reuses a process ID	957	In Erlang it is quite likely that a node that restarts reuses an Erlang
840	known to other nodes for a completely different process, causing messages	958	process ID known to other nodes for a completely different process,
841	destined for that process to end up in an unrelated process.	959	causing messages destined for that process to end up in an unrelated
		960	process.
842		961
843	AEMP never reuses port IDs, so old messages or old port IDs floating	962	AEMP does not reuse port IDs, so old messages or old port IDs floating
844	around in the network will not be sent to an unrelated port.	963	around in the network will not be sent to an unrelated port.
845		964
846	=item * Erlang uses unprotected connections, AEMP uses secure	965	=item * Erlang uses unprotected connections, AEMP uses secure
847	authentication and can use TLS.	966	authentication and can use TLS.
848		967
…		…
851		970
852	=item * The AEMP protocol is optimised for both text-based and binary	971	=item * The AEMP protocol is optimised for both text-based and binary
853	communications.	972	communications.
854		973
855	The AEMP protocol, unlike the Erlang protocol, supports both programming	974	The AEMP protocol, unlike the Erlang protocol, supports both programming
856	language independent text-only protocols (good for debugging) and binary,	975	language independent text-only protocols (good for debugging), and binary,
857	language-specific serialisers (e.g. Storable). By default, unless TLS is	976	language-specific serialisers (e.g. Storable). By default, unless TLS is
858	used, the protocol is actually completely text-based.	977	used, the protocol is actually completely text-based.
859		978
860	It has also been carefully designed to be implementable in other languages	979	It has also been carefully designed to be implementable in other languages
861	with a minimum of work while gracefully degrading functionality to make the	980	with a minimum of work while gracefully degrading functionality to make the
862	protocol simple.	981	protocol simple.
863		982
864	=item * AEMP has more flexible monitoring options than Erlang.	983	=item * AEMP has more flexible monitoring options than Erlang.
865		984
866	In Erlang, you can chose to receive I<all> exit signals as messages	985	In Erlang, you can chose to receive I<all> exit signals as messages or
867	or I<none>, there is no in-between, so monitoring single processes is	986	I<none>, there is no in-between, so monitoring single Erlang processes is
868	difficult to implement. Monitoring in AEMP is more flexible than in	987	difficult to implement.
869	Erlang, as one can choose between automatic kill, exit message or callback	988
870	on a per-process basis.	989	Monitoring in AEMP is more flexible than in Erlang, as one can choose
		990	between automatic kill, exit message or callback on a per-port basis.
871		991
872	=item * Erlang tries to hide remote/local connections, AEMP does not.	992	=item * Erlang tries to hide remote/local connections, AEMP does not.
873		993
874	Monitoring in Erlang is not an indicator of process death/crashes, in the	994	Monitoring in Erlang is not an indicator of process death/crashes, in the
875	same way as linking is (except linking is unreliable in Erlang).	995	same way as linking is (except linking is unreliable in Erlang).
…		…
897	overhead, as well as having to keep a proxy object everywhere.	1017	overhead, as well as having to keep a proxy object everywhere.
898		1018
899	Strings can easily be printed, easily serialised etc. and need no special	1019	Strings can easily be printed, easily serialised etc. and need no special
900	procedures to be "valid".	1020	procedures to be "valid".
901		1021
902	And as a result, a miniport consists of a single closure stored in a	1022	And as a result, a port with just a default receiver consists of a single
903	global hash - it can't become much cheaper.	1023	code reference stored in a global hash - it can't become much cheaper.
904		1024
905	=item Why favour JSON, why not a real serialising format such as Storable?	1025	=item Why favour JSON, why not a real serialising format such as Storable?
906		1026
907	In fact, any AnyEvent::MP node will happily accept Storable as framing	1027	In fact, any AnyEvent::MP node will happily accept Storable as framing
908	format, but currently there is no way to make a node use Storable by	1028	format, but currently there is no way to make a node use Storable by
…		…
924		1044
925	L<AnyEvent::MP::Intro> - a gentle introduction.	1045	L<AnyEvent::MP::Intro> - a gentle introduction.
926		1046
927	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.	1047	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.
928		1048
929	L<AnyEvent::MP::Global> - network maintainance and port groups, to find	1049	L<AnyEvent::MP::Global> - network maintenance and port groups, to find
930	your applications.	1050	your applications.
		1051
		1052	L<AnyEvent::MP::DataConn> - establish data connections between nodes.
931		1053
932	L<AnyEvent::MP::LogCatcher> - simple service to display log messages from	1054	L<AnyEvent::MP::LogCatcher> - simple service to display log messages from
933	all nodes.	1055	all nodes.
934		1056
935	L<AnyEvent>.	1057	L<AnyEvent>.

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.100 by root, Fri Oct 2 20:41:56 2009 UTC vs. Revision 1.123 by root, Thu Mar 1 19:37:59 2012 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.100 by root, Fri Oct 2 20:41:56 2009 UTC vs.
Revision 1.123 by root, Thu Mar 1 19:37:59 2012 UTC