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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.111 by root, Sat Mar 20 20:12:18 2010 UTC vs.
Revision 1.127 by root, Sat Mar 3 20:35:10 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 prot again	35	# destroy a port again
36	kil $port; # "normal" kill	36	kil $port; # "normal" kill
37	kil $port, my_error => "everything is broken"; # error kill	37	kil $port, my_error => "everything is broken"; # error kill
38		38
39	# monitoring	39	# monitoring
40	mon $localport, $cb->(@msg) # callback is invoked on death	40	mon $localport, $cb->(@msg) # callback is invoked on death
…		…
78		78
79	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
80	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
81	anything was listening for them or not.	81	anything was listening for them or not.
82		82
		83	Ports are represented by (printable) strings called "port IDs".
		84
83	=item port ID - C<nodeid#portname>	85	=item port ID - C<nodeid#portname>
84		86
85	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<#>)
86	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).
87		90
88	=item node	91	=item node
89		92
90	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,
91	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
92	ports.	95	ports.
93		96
94	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
95	(no listening ports). Private nodes cannot talk to other private nodes	98	(no listening ports). Private nodes cannot talk to other private nodes
96	currently.	99	currently, but all nodes can talk to public nodes.
97		100
		101	Nodes is represented by (printable) strings called "node IDs".
		102
98	=item node ID - C<[A-Z_][a-zA-Z0-9_\-.:]*>	103	=item node ID - C<[A-Za-z0-9_\-.:]*>
99		104
100	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
101	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
102	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
103	doesn't interpret node IDs in any way.	108	doesn't interpret node IDs in any way except to uniquely identify a node.
104		109
105	=item binds - C<ip:port>	110	=item binds - C<ip:port>
106		111
107	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
108	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
109	endpoints - binds. Currently, only standard C<ip:port> specifications can	116	Currently, only standard C<ip:port> specifications can be used, which
110	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.
111		119
112	=item seed nodes	120	=item seed nodes
113		121
114	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
115	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
116	network. This node is called a seed.	124	network. These other nodes are called "seed nodes".
117		125
118	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
119	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
120	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.
121		129
122	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
123	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
124	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.
125		135
126	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
127	should always be available. They should also be relatively responsive - a	137	should always be available. They should also be relatively responsive - a
128	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.
129		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
130	=item seeds - C<host:port>	149	=item seed IDs - C<host:port>
131		150
132	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
133	TCP port) of nodes that should be used as seed nodes.	152	TCP port) of nodes that should be used as seed nodes.
134		153
135	The nodes listening on those endpoints are expected to be long-running,	154	=item global nodes
136	and at least one of those should always be available. When nodes run out	155
137	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
138	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).
139		170
140	=back	171	=back
141		172
142	=head1 VARIABLES/FUNCTIONS	173	=head1 VARIABLES/FUNCTIONS
143		174
…		…
145		176
146	=cut	177	=cut
147		178
148	package AnyEvent::MP;	179	package AnyEvent::MP;
149		180
		181	use AnyEvent::MP::Config ();
150	use AnyEvent::MP::Kernel;	182	use AnyEvent::MP::Kernel;
		183	use AnyEvent::MP::Kernel qw(%NODE %PORT %PORT_DATA $UNIQ $RUNIQ $ID);
151		184
152	use common::sense;	185	use common::sense;
153		186
154	use Carp ();	187	use Carp ();
155		188
156	use AE ();	189	use AE ();
		190	use Guard ();
157		191
158	use base "Exporter";	192	use base "Exporter";
159		193
160	our $VERSION = 1.27;	194	our $VERSION = $AnyEvent::MP::Config::VERSION;
161		195
162	our @EXPORT = qw(	196	our @EXPORT = qw(
163	NODE $NODE *SELF node_of after	197	NODE $NODE *SELF node_of after
164	configure	198	configure
165	snd rcv mon mon_guard kil psub peval spawn cal	199	snd rcv mon mon_guard kil psub peval spawn cal
166	port	200	port
		201	db_set db_del db_reg
167	);	202	);
168		203
169	our $SELF;	204	our $SELF;
170		205
171	sub _self_die() {	206	sub _self_die() {
…		…
191	Before a node can talk to other nodes on the network (i.e. enter	226	Before a node can talk to other nodes on the network (i.e. enter
192	"distributed mode") it has to configure itself - the minimum a node needs	227	"distributed mode") it has to configure itself - the minimum a node needs
193	to know is its own name, and optionally it should know the addresses of	228	to know is its own name, and optionally it should know the addresses of
194	some other nodes in the network to discover other nodes.	229	some other nodes in the network to discover other nodes.
195		230
196	The key/value pairs are basically the same ones as documented for the
197	F<aemp> command line utility (sans the set/del prefix).
198
199	This function configures a node - it must be called exactly once (or	231	This function configures a node - it must be called exactly once (or
200	never) before calling other AnyEvent::MP functions.	232	never) before calling other AnyEvent::MP functions.
		233
		234	The key/value pairs are basically the same ones as documented for the
		235	F<aemp> command line utility (sans the set/del prefix), with these additions:
		236
		237	=over 4
		238
		239	=item norc => $boolean (default false)
		240
		241	If true, then the rc file (e.g. F<~/.perl-anyevent-mp>) will I<not>
		242	be consulted - all configuraiton options must be specified in the
		243	C<configure> call.
		244
		245	=item force => $boolean (default false)
		246
		247	IF true, then the values specified in the C<configure> will take
		248	precedence over any values configured via the rc file. The default is for
		249	the rc file to override any options specified in the program.
		250
		251	=item secure => $pass->($nodeid)
		252
		253	In addition to specifying a boolean, you can specify a code reference that
		254	is called for every remote execution attempt - the execution request is
		255	granted iff the callback returns a true value.
		256
		257	See F<semp setsecure> for more info.
		258
		259	=back
201		260
202	=over 4	261	=over 4
203		262
204	=item step 1, gathering configuration from profiles	263	=item step 1, gathering configuration from profiles
205		264
…		…
219	That means that the values specified in the profile have highest priority	278	That means that the values specified in the profile have highest priority
220	and the values specified directly via C<configure> have lowest priority,	279	and the values specified directly via C<configure> have lowest priority,
221	and can only be used to specify defaults.	280	and can only be used to specify defaults.
222		281
223	If the profile specifies a node ID, then this will become the node ID of	282	If the profile specifies a node ID, then this will become the node ID of
224	this process. If not, then the profile name will be used as node ID. The	283	this process. If not, then the profile name will be used as node ID, with
225	special node ID of C<anon/> will be replaced by a random node ID.	284	a unique randoms tring (C</%u>) appended.
		285
		286	The node ID can contain some C<%> sequences that are expanded: C<%n>
		287	is expanded to the local nodename, C<%u> is replaced by a random
		288	strign to make the node unique. For example, the F<aemp> commandline
		289	utility uses C<aemp/%n/%u> as nodename, which might expand to
		290	C<aemp/cerebro/ZQDGSIkRhEZQDGSIkRhE>.
226		291
227	=item step 2, bind listener sockets	292	=item step 2, bind listener sockets
228		293
229	The next step is to look up the binds in the profile, followed by binding	294	The next step is to look up the binds in the profile, followed by binding
230	aemp protocol listeners on all binds specified (it is possible and valid	295	aemp protocol listeners on all binds specified (it is possible and valid
…		…
236	used, meaning the node will bind on a dynamically-assigned port on every	301	used, meaning the node will bind on a dynamically-assigned port on every
237	local IP address it finds.	302	local IP address it finds.
238		303
239	=item step 3, connect to seed nodes	304	=item step 3, connect to seed nodes
240		305
241	As the last step, the seeds list from the profile is passed to the	306	As the last step, the seed ID list from the profile is passed to the
242	L<AnyEvent::MP::Global> module, which will then use it to keep	307	L<AnyEvent::MP::Global> module, which will then use it to keep
243	connectivity with at least one node at any point in time.	308	connectivity with at least one node at any point in time.
244		309
245	=back	310	=back
246		311
247	Example: become a distributed node using the local node name as profile.	312	Example: become a distributed node using the local node name as profile.
248	This should be the most common form of invocation for "daemon"-type nodes.	313	This should be the most common form of invocation for "daemon"-type nodes.
249		314
250	configure	315	configure
251		316
252	Example: become an anonymous node. This form is often used for commandline	317	Example: become a semi-anonymous node. This form is often used for
253	clients.	318	commandline clients.
254		319
255	configure nodeid => "anon/";	320	configure nodeid => "myscript/%n/%u";
256		321
257	Example: configure a node using a profile called seed, which si suitable	322	Example: configure a node using a profile called seed, which is suitable
258	for a seed node as it binds on all local addresses on a fixed port (4040,	323	for a seed node as it binds on all local addresses on a fixed port (4040,
259	customary for aemp).	324	customary for aemp).
260		325
261	# use the aemp commandline utility	326	# use the aemp commandline utility
262	# aemp profile seed nodeid anon/ binds '*:4040'	327	# aemp profile seed binds '*:4040'
263		328
264	# then use it	329	# then use it
265	configure profile => "seed";	330	configure profile => "seed";
266		331
267	# or simply use aemp from the shell again:	332	# or simply use aemp from the shell again:
…		…
337	sub _kilme {	402	sub _kilme {
338	die "received message on port without callback";	403	die "received message on port without callback";
339	}	404	}
340		405
341	sub port(;&) {	406	sub port(;&) {
342	my $id = "$UNIQ." . $ID++;	407	my $id = $UNIQ . ++$ID;
343	my $port = "$NODE#$id";	408	my $port = "$NODE#$id";
344		409
345	rcv $port, shift \|\| \&_kilme;	410	rcv $port, shift \|\| \&_kilme;
346		411
347	$port	412	$port
…		…
495	Remembers C<$SELF> and creates a closure out of the BLOCK. When the	560	Remembers C<$SELF> and creates a closure out of the BLOCK. When the
496	closure is executed, sets up the environment in the same way as in C<rcv>	561	closure is executed, sets up the environment in the same way as in C<rcv>
497	callbacks, i.e. runtime errors will cause the port to get C<kil>ed.	562	callbacks, i.e. runtime errors will cause the port to get C<kil>ed.
498		563
499	The effect is basically as if it returned C<< sub { peval $SELF, sub {	564	The effect is basically as if it returned C<< sub { peval $SELF, sub {
500	BLOCK } } >>.	565	BLOCK }, @_ } >>.
501		566
502	This is useful when you register callbacks from C<rcv> callbacks:	567	This is useful when you register callbacks from C<rcv> callbacks:
503		568
504	rcv delayed_reply => sub {	569	rcv delayed_reply => sub {
505	my ($delay, @reply) = @_;	570	my ($delay, @reply) = @_;
…		…
620	}	685	}
621		686
622	$node->monitor ($port, $cb);	687	$node->monitor ($port, $cb);
623		688
624	defined wantarray	689	defined wantarray
625	and ($cb += 0, AnyEvent::Util::guard { $node->unmonitor ($port, $cb) })	690	and ($cb += 0, Guard::guard { $node->unmonitor ($port, $cb) })
626	}	691	}
627		692
628	=item $guard = mon_guard $port, $ref, $ref...	693	=item $guard = mon_guard $port, $ref, $ref...
629		694
630	Monitors the given C<$port> and keeps the passed references. When the port	695	Monitors the given C<$port> and keeps the passed references. When the port
…		…
734	}	799	}
735		800
736	sub spawn(@) {	801	sub spawn(@) {
737	my ($nodeid, undef) = split /#/, shift, 2;	802	my ($nodeid, undef) = split /#/, shift, 2;
738		803
739	my $id = "$RUNIQ." . $ID++;	804	my $id = $RUNIQ . ++$ID;
740		805
741	$_[0] =~ /::/	806	$_[0] =~ /::/
742	or Carp::croak "spawn init function must be a fully-qualified name, caught";	807	or Carp::croak "spawn init function must be a fully-qualified name, caught";
743		808
744	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;	809	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;
745		810
746	"$nodeid#$id"	811	"$nodeid#$id"
747	}	812	}
		813
748		814
749	=item after $timeout, @msg	815	=item after $timeout, @msg
750		816
751	=item after $timeout, $callback	817	=item after $timeout, $callback
752		818
…		…
822	$port	888	$port
823	}	889	}
824		890
825	=back	891	=back
826		892
		893	=head1 DISTRIBUTED DATABASE
		894
		895	AnyEvent::MP comes with a simple distributed database. The database will
		896	be mirrored asynchronously at all global nodes. Other nodes bind to one of
		897	the global nodes for their needs.
		898
		899	The database consists of a two-level hash - a hash contains a hash which
		900	contains values.
		901
		902	The top level hash key is called "family", and the second-level hash key
		903	is called "subkey" or simply "key".
		904
		905	The family must be alphanumeric, i.e. start with a letter and consist
		906	of letters, digits, underscores and colons (C<[A-Za-z][A-Za-z0-9_:]*>,
		907	pretty much like Perl module names.
		908
		909	As the family namespace is global, it is recommended to prefix family names
		910	with the name of the application or module using it.
		911
		912	The subkeys must be non-empty strings, with no further restrictions.
		913
		914	The values should preferably be strings, but other perl scalars should
		915	work as well (such as undef, arrays and hashes).
		916
		917	Every database entry is owned by one node - adding the same family/subkey
		918	combination on multiple nodes will not cause discomfort for AnyEvent::MP,
		919	but the result might be nondeterministic, i.e. the key might have
		920	different values on different nodes.
		921
		922	Different subkeys in the same family can be owned by different nodes
		923	without problems, and in fact, this is the common method to create worker
		924	pools. For example, a worker port for image scaling might do this:
		925
		926	db_set my_image_scalers => $port;
		927
		928	And clients looking for an image scaler will want to get the
		929	C<my_image_scalers> keys:
		930
		931	db_keys "my_image_scalers" => 60 => sub {
		932	#d##TODO#
		933
		934	=over
		935
		936	=item db_set $family => $subkey [=> $value]
		937
		938	Sets (or replaces) a key to the database - if C<$value> is omitted,
		939	C<undef> is used instead.
		940
		941	=item db_del $family => $subkey
		942
		943	Deletes a key from the database.
		944
		945	=item $guard = db_reg $family => $subkey [=> $value]
		946
		947	Sets the key on the database and returns a guard. When the guard is
		948	destroyed, the key is deleted from the database. If C<$value> is missing,
		949	then C<undef> is used.
		950
		951	=cut
		952
		953	=back
		954
827	=head1 AnyEvent::MP vs. Distributed Erlang	955	=head1 AnyEvent::MP vs. Distributed Erlang
828		956
829	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node	957	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
830	== aemp node, Erlang process == aemp port), so many of the documents and	958	== aemp node, Erlang process == aemp port), so many of the documents and
831	programming techniques employed by Erlang apply to AnyEvent::MP. Here is a	959	programming techniques employed by Erlang apply to AnyEvent::MP. Here is a
…		…
862	ports being the special case/exception, where transport errors cannot	990	ports being the special case/exception, where transport errors cannot
863	occur.	991	occur.
864		992
865	=item * Erlang uses processes and a mailbox, AEMP does not queue.	993	=item * Erlang uses processes and a mailbox, AEMP does not queue.
866		994
867	Erlang uses processes that selectively receive messages, and therefore	995	Erlang uses processes that selectively receive messages out of order, and
868	needs a queue. AEMP is event based, queuing messages would serve no	996	therefore needs a queue. AEMP is event based, queuing messages would serve
869	useful purpose. For the same reason the pattern-matching abilities of	997	no useful purpose. For the same reason the pattern-matching abilities
870	AnyEvent::MP are more limited, as there is little need to be able to	998	of AnyEvent::MP are more limited, as there is little need to be able to
871	filter messages without dequeuing them.	999	filter messages without dequeuing them.
872		1000
873	(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).	1001	This is not a philosophical difference, but simply stems from AnyEvent::MP
		1002	being event-based, while Erlang is process-based.
		1003
		1004	You cna have a look at L<Coro::MP> for a more Erlang-like process model on
		1005	top of AEMP and Coro threads.
874		1006
875	=item * Erlang sends are synchronous, AEMP sends are asynchronous.	1007	=item * Erlang sends are synchronous, AEMP sends are asynchronous.
876		1008
877	Sending messages in Erlang is synchronous and blocks the process (and	1009	Sending messages in Erlang is synchronous and blocks the process until
		1010	a conenction has been established and the message sent (and so does not
878	so does not need a queue that can overflow). AEMP sends are immediate,	1011	need a queue that can overflow). AEMP sends return immediately, connection
879	connection establishment is handled in the background.	1012	establishment is handled in the background.
880		1013
881	=item * Erlang suffers from silent message loss, AEMP does not.	1014	=item * Erlang suffers from silent message loss, AEMP does not.
882		1015
883	Erlang implements few guarantees on messages delivery - messages can get	1016	Erlang implements few guarantees on messages delivery - messages can get
884	lost without any of the processes realising it (i.e. you send messages a,	1017	lost without any of the processes realising it (i.e. you send messages a,
885	b, and c, and the other side only receives messages a and c).	1018	b, and c, and the other side only receives messages a and c).
886		1019
887	AEMP guarantees correct ordering, and the guarantee that after one message	1020	AEMP guarantees (modulo hardware errors) correct ordering, and the
888	is lost, all following ones sent to the same port are lost as well, until	1021	guarantee that after one message is lost, all following ones sent to the
889	monitoring raises an error, so there are no silent "holes" in the message	1022	same port are lost as well, until monitoring raises an error, so there are
890	sequence.	1023	no silent "holes" in the message sequence.
		1024
		1025	If you want your software to be very reliable, you have to cope with
		1026	corrupted and even out-of-order messages in both Erlang and AEMP. AEMP
		1027	simply tries to work better in common error cases, such as when a network
		1028	link goes down.
891		1029
892	=item * Erlang can send messages to the wrong port, AEMP does not.	1030	=item * Erlang can send messages to the wrong port, AEMP does not.
893		1031
894	In Erlang it is quite likely that a node that restarts reuses a process ID	1032	In Erlang it is quite likely that a node that restarts reuses an Erlang
895	known to other nodes for a completely different process, causing messages	1033	process ID known to other nodes for a completely different process,
896	destined for that process to end up in an unrelated process.	1034	causing messages destined for that process to end up in an unrelated
		1035	process.
897		1036
898	AEMP never reuses port IDs, so old messages or old port IDs floating	1037	AEMP does not reuse port IDs, so old messages or old port IDs floating
899	around in the network will not be sent to an unrelated port.	1038	around in the network will not be sent to an unrelated port.
900		1039
901	=item * Erlang uses unprotected connections, AEMP uses secure	1040	=item * Erlang uses unprotected connections, AEMP uses secure
902	authentication and can use TLS.	1041	authentication and can use TLS.
903		1042
…		…
906		1045
907	=item * The AEMP protocol is optimised for both text-based and binary	1046	=item * The AEMP protocol is optimised for both text-based and binary
908	communications.	1047	communications.
909		1048
910	The AEMP protocol, unlike the Erlang protocol, supports both programming	1049	The AEMP protocol, unlike the Erlang protocol, supports both programming
911	language independent text-only protocols (good for debugging) and binary,	1050	language independent text-only protocols (good for debugging), and binary,
912	language-specific serialisers (e.g. Storable). By default, unless TLS is	1051	language-specific serialisers (e.g. Storable). By default, unless TLS is
913	used, the protocol is actually completely text-based.	1052	used, the protocol is actually completely text-based.
914		1053
915	It has also been carefully designed to be implementable in other languages	1054	It has also been carefully designed to be implementable in other languages
916	with a minimum of work while gracefully degrading functionality to make the	1055	with a minimum of work while gracefully degrading functionality to make the
917	protocol simple.	1056	protocol simple.
918		1057
919	=item * AEMP has more flexible monitoring options than Erlang.	1058	=item * AEMP has more flexible monitoring options than Erlang.
920		1059
921	In Erlang, you can chose to receive I<all> exit signals as messages	1060	In Erlang, you can chose to receive I<all> exit signals as messages or
922	or I<none>, there is no in-between, so monitoring single processes is	1061	I<none>, there is no in-between, so monitoring single Erlang processes is
923	difficult to implement. Monitoring in AEMP is more flexible than in	1062	difficult to implement.
924	Erlang, as one can choose between automatic kill, exit message or callback	1063
925	on a per-process basis.	1064	Monitoring in AEMP is more flexible than in Erlang, as one can choose
		1065	between automatic kill, exit message or callback on a per-port basis.
926		1066
927	=item * Erlang tries to hide remote/local connections, AEMP does not.	1067	=item * Erlang tries to hide remote/local connections, AEMP does not.
928		1068
929	Monitoring in Erlang is not an indicator of process death/crashes, in the	1069	Monitoring in Erlang is not an indicator of process death/crashes, in the
930	same way as linking is (except linking is unreliable in Erlang).	1070	same way as linking is (except linking is unreliable in Erlang).
…		…
953		1093
954	Strings can easily be printed, easily serialised etc. and need no special	1094	Strings can easily be printed, easily serialised etc. and need no special
955	procedures to be "valid".	1095	procedures to be "valid".
956		1096
957	And as a result, a port with just a default receiver consists of a single	1097	And as a result, a port with just a default receiver consists of a single
958	closure stored in a global hash - it can't become much cheaper.	1098	code reference stored in a global hash - it can't become much cheaper.
959		1099
960	=item Why favour JSON, why not a real serialising format such as Storable?	1100	=item Why favour JSON, why not a real serialising format such as Storable?
961		1101
962	In fact, any AnyEvent::MP node will happily accept Storable as framing	1102	In fact, any AnyEvent::MP node will happily accept Storable as framing
963	format, but currently there is no way to make a node use Storable by	1103	format, but currently there is no way to make a node use Storable by
…		…
979		1119
980	L<AnyEvent::MP::Intro> - a gentle introduction.	1120	L<AnyEvent::MP::Intro> - a gentle introduction.
981		1121
982	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.	1122	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.
983		1123
984	L<AnyEvent::MP::Global> - network maintainance and port groups, to find	1124	L<AnyEvent::MP::Global> - network maintenance and port groups, to find
985	your applications.	1125	your applications.
986		1126
987	L<AnyEvent::MP::DataConn> - establish data connections between nodes.	1127	L<AnyEvent::MP::DataConn> - establish data connections between nodes.
988		1128
989	L<AnyEvent::MP::LogCatcher> - simple service to display log messages from	1129	L<AnyEvent::MP::LogCatcher> - simple service to display log messages from

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.111 by root, Sat Mar 20 20:12:18 2010 UTC vs. Revision 1.127 by root, Sat Mar 3 20:35:10 2012 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.111 by root, Sat Mar 20 20:12:18 2010 UTC vs.
Revision 1.127 by root, Sat Mar 3 20:35:10 2012 UTC