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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.95 by root, Wed Sep 23 11:57:16 2009 UTC vs.
Revision 1.121 by root, Tue Feb 28 18:37:24 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<#>) as
74	separator, and a port name (a printable string of unspecified format).	88	separator, and a port name (a printable string of unspecified format).
75		89
…		…
79	which enables nodes to manage each other remotely, and to create new	93	which enables nodes to manage each other remotely, and to create new
80	ports.	94	ports.
81		95
82	Nodes are either public (have one or more listening ports) or private	96	Nodes are either public (have one or more listening ports) or private
83	(no listening ports). Private nodes cannot talk to other private nodes	97	(no listening ports). Private nodes cannot talk to other private nodes
84	currently.	98	currently, but all nodes can talk to public nodes.
85		99
		100	Nodes is represented by (printable) strings called "node IDs".
		101
86	=item node ID - C<[A-Z_][a-zA-Z0-9_\-.:]*>	102	=item node ID - C<[A-Za-z0-9_\-.:]*>
87		103
88	A node ID is a string that uniquely identifies the node within a	104	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	105	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	106	hostname, a hostname and a port, or a random string. AnyEvent::MP itself
91	doesn't interpret node IDs in any way.	107	doesn't interpret node IDs in any way except to uniquely identify a node.
92		108
93	=item binds - C<ip:port>	109	=item binds - C<ip:port>
94		110
95	Nodes can only talk to each other by creating some kind of connection to	111	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	112	each other. To do this, nodes should listen on one or more local transport
		113	endpoints - binds.
		114
97	endpoints - binds. Currently, only standard C<ip:port> specifications can	115	Currently, only standard C<ip:port> specifications can be used, which
98	be used, which specify TCP ports to listen on.	116	specify TCP ports to listen on. So a bind is basically just a tcp socket
		117	in listening mode thta accepts conenctions form other nodes.
99		118
100	=item seed nodes	119	=item seed nodes
101		120
102	When a node starts, it knows nothing about the network. To teach the node	121	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	122	needs to connect to at least one other node that is already in the
104	network. This node is called a seed.	123	network. These other nodes are called "seed nodes".
105		124
106	Apart from the fact that other nodes know them as seed nodes and they have	125	Seed nodes themselves are not special - they are seed nodes only because
107	to have fixed listening addresses, seed nodes are perfectly normal nodes -	126	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.	127	node for other nodes, and eahc node cna use a different set of seed nodes.
109		128
110	In addition to discovering the network, seed nodes are also used to	129	In addition to discovering the network, seed nodes are also used to
111	maintain the network and to connect nodes that otherwise would have	130	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.	131	the same network. If a network is split into multiple subnets because e.g.
		132	the network link between the parts goes down, then using the same seed
		133	nodes for all nodes ensures that eventually the subnets get merged again.
113		134
114	Seed nodes are expected to be long-running, and at least one seed node	135	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	136	should always be available. They should also be relatively responsive - a
116	seed node that blocks for long periods will slow down everybody else.	137	seed node that blocks for long periods will slow down everybody else.
117		138
		139	For small networks, it's best if every node uses the same set of seed
		140	nodes. For large networks, it can be useful to specify "regional" seed
		141	nodes for most nodes in an area, and use all seed nodes as seed nodes for
		142	each other. What's important is that all seed nodes connections form a
		143	complete graph, so that the network cannot split into separate subnets
		144	forever.
		145
		146	Seed nodes are represented by seed IDs.
		147
118	=item seeds - C<host:port>	148	=item seed IDs - C<host:port>
119		149
120	Seeds are transport endpoint(s) (usually a hostname/IP address and a	150	Seed IDs are transport endpoint(s) (usually a hostname/IP address and a
121	TCP port) of nodes thta should be used as seed nodes.	151	TCP port) of nodes that should be used as seed nodes.
122		152
123	The nodes listening on those endpoints are expected to be long-running,	153	=item global nodes
124	and at least one of those should always be available. When nodes run out	154
125	of connections (e.g. due to a network error), they try to re-establish	155	An AEMP network needs a discovery service - nodes need to know how to
126	connections to some seednodes again to join the network.	156	connect to other nodes they only know by name. In addition, AEMP offers a
		157	distributed "group database", which maps group names to a list of strings
		158	- for example, to register worker ports.
		159
		160	A network needs at least one global node to work, and allows every node to
		161	be a global node.
		162
		163	Any node that loads the L<AnyEvent::MP::Global> module becomes a global
		164	node and tries to keep connections to all other nodes. So while it can
		165	make sense to make every node "global" in small networks, it usually makes
		166	sense to only make seed nodes into global nodes in large networks (nodes
		167	keep connections to seed nodes and global nodes, so makign them the same
		168	reduces overhead).
127		169
128	=back	170	=back
129		171
130	=head1 VARIABLES/FUNCTIONS	172	=head1 VARIABLES/FUNCTIONS
131		173
…		…
133		175
134	=cut	176	=cut
135		177
136	package AnyEvent::MP;	178	package AnyEvent::MP;
137		179
		180	use AnyEvent::MP::Config ();
138	use AnyEvent::MP::Kernel;	181	use AnyEvent::MP::Kernel;
		182	use AnyEvent::MP::Kernel qw(%NODE %PORT %PORT_DATA $UNIQ $RUNIQ $ID);
139		183
140	use common::sense;	184	use common::sense;
141		185
142	use Carp ();	186	use Carp ();
143		187
144	use AE ();	188	use AE ();
145		189
146	use base "Exporter";	190	use base "Exporter";
147		191
148	our $VERSION = $AnyEvent::MP::Kernel::VERSION;	192	our $VERSION = $AnyEvent::MP::Config::VERSION;
149		193
150	our @EXPORT = qw(	194	our @EXPORT = qw(
151	NODE $NODE *SELF node_of after	195	NODE $NODE *SELF node_of after
152	configure	196	configure
153	snd rcv mon mon_guard kil psub spawn cal	197	snd rcv mon mon_guard kil psub peval spawn cal
154	port	198	port
155	);	199	);
156		200
157	our $SELF;	201	our $SELF;
158		202
…		…
181	to know is its own name, and optionally it should know the addresses of	225	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.	226	some other nodes in the network to discover other nodes.
183		227
184	This function configures a node - it must be called exactly once (or	228	This function configures a node - it must be called exactly once (or
185	never) before calling other AnyEvent::MP functions.	229	never) before calling other AnyEvent::MP functions.
		230
		231	The key/value pairs are basically the same ones as documented for the
		232	F<aemp> command line utility (sans the set/del prefix), with two additions:
		233
		234	=over 4
		235
		236	=item norc => $boolean (default false)
		237
		238	If true, then the rc file (e.g. F<~/.perl-anyevent-mp>) will I<not>
		239	be consulted - all configuraiton options must be specified in the
		240	C<configure> call.
		241
		242	=item force => $boolean (default false)
		243
		244	IF true, then the values specified in the C<configure> will take
		245	precedence over any values configured via the rc file. The default is for
		246	the rc file to override any options specified in the program.
		247
		248	=back
186		249
187	=over 4	250	=over 4
188		251
189	=item step 1, gathering configuration from profiles	252	=item step 1, gathering configuration from profiles
190		253
…		…
221	used, meaning the node will bind on a dynamically-assigned port on every	284	used, meaning the node will bind on a dynamically-assigned port on every
222	local IP address it finds.	285	local IP address it finds.
223		286
224	=item step 3, connect to seed nodes	287	=item step 3, connect to seed nodes
225		288
226	As the last step, the seeds list from the profile is passed to the	289	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	290	L<AnyEvent::MP::Global> module, which will then use it to keep
228	connectivity with at least one node at any point in time.	291	connectivity with at least one node at any point in time.
229		292
230	=back	293	=back
231		294
…		…
237	Example: become an anonymous node. This form is often used for commandline	300	Example: become an anonymous node. This form is often used for commandline
238	clients.	301	clients.
239		302
240	configure nodeid => "anon/";	303	configure nodeid => "anon/";
241		304
242	Example: configure a node using a profile called seed, which si suitable	305	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,	306	for a seed node as it binds on all local addresses on a fixed port (4040,
244	customary for aemp).	307	customary for aemp).
245		308
246	# use the aemp commandline utility	309	# use the aemp commandline utility
247	# aemp profile seed nodeid anon/ binds '*:4040'	310	# aemp profile seed nodeid anon/ binds '*:4040'
…		…
322	sub _kilme {	385	sub _kilme {
323	die "received message on port without callback";	386	die "received message on port without callback";
324	}	387	}
325		388
326	sub port(;&) {	389	sub port(;&) {
327	my $id = "$UNIQ." . $ID++;	390	my $id = "$UNIQ." . ++$ID;
328	my $port = "$NODE#$id";	391	my $port = "$NODE#$id";
329		392
330	rcv $port, shift \|\| \&_kilme;	393	rcv $port, shift \|\| \&_kilme;
331		394
332	$port	395	$port
…		…
371	msg1 => sub { ... },	434	msg1 => sub { ... },
372	...	435	...
373	;	436	;
374		437
375	Example: temporarily register a rcv callback for a tag matching some port	438	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.	439	(e.g. for an rpc reply) and unregister it after a message was received.
377		440
378	rcv $port, $otherport => sub {	441	rcv $port, $otherport => sub {
379	my @reply = @_;	442	my @reply = @_;
380		443
381	rcv $SELF, $otherport;	444	rcv $SELF, $otherport;
…		…
394	if (ref $_[0]) {	457	if (ref $_[0]) {
395	if (my $self = $PORT_DATA{$portid}) {	458	if (my $self = $PORT_DATA{$portid}) {
396	"AnyEvent::MP::Port" eq ref $self	459	"AnyEvent::MP::Port" eq ref $self
397	or Carp::croak "$port: rcv can only be called on message matching ports, caught";	460	or Carp::croak "$port: rcv can only be called on message matching ports, caught";
398		461
399	$self->[2] = shift;	462	$self->[0] = shift;
400	} else {	463	} else {
401	my $cb = shift;	464	my $cb = shift;
402	$PORT{$portid} = sub {	465	$PORT{$portid} = sub {
403	local $SELF = $port;	466	local $SELF = $port;
404	eval { &$cb }; _self_die if $@;	467	eval { &$cb }; _self_die if $@;
405	};	468	};
406	}	469	}
407	} elsif (defined $_[0]) {	470	} elsif (defined $_[0]) {
408	my $self = $PORT_DATA{$portid} \|\|= do {	471	my $self = $PORT_DATA{$portid} \|\|= do {
409	my $self = bless [$PORT{$port} \|\| sub { }, { }, $port], "AnyEvent::MP::Port";	472	my $self = bless [$PORT{$portid} \|\| sub { }, { }, $port], "AnyEvent::MP::Port";
410		473
411	$PORT{$portid} = sub {	474	$PORT{$portid} = sub {
412	local $SELF = $port;	475	local $SELF = $port;
413		476
414	if (my $cb = $self->[1]{$_[0]}) {	477	if (my $cb = $self->[1]{$_[0]}) {
…		…
436	}	499	}
437		500
438	$port	501	$port
439	}	502	}
440		503
		504	=item peval $port, $coderef[, @args]
		505
		506	Evaluates the given C<$codref> within the contetx of C<$port>, that is,
		507	when the code throews an exception the C<$port> will be killed.
		508
		509	Any remaining args will be passed to the callback. Any return values will
		510	be returned to the caller.
		511
		512	This is useful when you temporarily want to execute code in the context of
		513	a port.
		514
		515	Example: create a port and run some initialisation code in it's context.
		516
		517	my $port = port { ... };
		518
		519	peval $port, sub {
		520	init
		521	or die "unable to init";
		522	};
		523
		524	=cut
		525
		526	sub peval($$) {
		527	local $SELF = shift;
		528	my $cb = shift;
		529
		530	if (wantarray) {
		531	my @res = eval { &$cb };
		532	_self_die if $@;
		533	@res
		534	} else {
		535	my $res = eval { &$cb };
		536	_self_die if $@;
		537	$res
		538	}
		539	}
		540
441	=item $closure = psub { BLOCK }	541	=item $closure = psub { BLOCK }
442		542
443	Remembers C<$SELF> and creates a closure out of the BLOCK. When the	543	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>	544	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.	545	callbacks, i.e. runtime errors will cause the port to get C<kil>ed.
		546
		547	The effect is basically as if it returned C<< sub { peval $SELF, sub {
		548	BLOCK }, @_ } >>.
446		549
447	This is useful when you register callbacks from C<rcv> callbacks:	550	This is useful when you register callbacks from C<rcv> callbacks:
448		551
449	rcv delayed_reply => sub {	552	rcv delayed_reply => sub {
450	my ($delay, @reply) = @_;	553	my ($delay, @reply) = @_;
…		…
523	delivered again.	626	delivered again.
524		627
525	Inter-host-connection timeouts and monitoring depend on the transport	628	Inter-host-connection timeouts and monitoring depend on the transport
526	used. The only transport currently implemented is TCP, and AnyEvent::MP	629	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	630	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).	631	non-idle connection, and usually around two hours for idle connections).
529		632
530	This means that monitoring is good for program errors and cleaning up	633	This means that monitoring is good for program errors and cleaning up
531	stuff eventually, but they are no replacement for a timeout when you need	634	stuff eventually, but they are no replacement for a timeout when you need
532	to ensure some maximum latency.	635	to ensure some maximum latency.
533		636
…		…
598		701
599	=item kil $port[, @reason]	702	=item kil $port[, @reason]
600		703
601	Kill the specified port with the given C<@reason>.	704	Kill the specified port with the given C<@reason>.
602		705
603	If no C<@reason> is specified, then the port is killed "normally" (ports	706	If no C<@reason> is specified, then the port is killed "normally" -
604	monitoring other ports will not necessarily die because a port dies	707	monitor callback will be invoked, but the kil will not cause linked ports
605	"normally").	708	(C<mon $mport, $lport> form) to get killed.
606		709
607	Otherwise, linked ports get killed with the same reason (second form of	710	If a C<@reason> is specified, then linked ports (C<mon $mport, $lport>
608	C<mon>, see above).	711	form) get killed with the same reason.
609		712
610	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks	713	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
611	will be reported as reason C<< die => $@ >>.	714	will be reported as reason C<< die => $@ >>.
612		715
613	Transport/communication errors are reported as C<< transport_error =>	716	Transport/communication errors are reported as C<< transport_error =>
…		…
679	}	782	}
680		783
681	sub spawn(@) {	784	sub spawn(@) {
682	my ($nodeid, undef) = split /#/, shift, 2;	785	my ($nodeid, undef) = split /#/, shift, 2;
683		786
684	my $id = "$RUNIQ." . $ID++;	787	my $id = "$RUNIQ." . ++$ID;
685		788
686	$_[0] =~ /::/	789	$_[0] =~ /::/
687	or Carp::croak "spawn init function must be a fully-qualified name, caught";	790	or Carp::croak "spawn init function must be a fully-qualified name, caught";
688		791
689	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;	792	snd_to_func $nodeid, "AnyEvent::MP::_spawn" => $id, @_;
690		793
691	"$nodeid#$id"	794	"$nodeid#$id"
692	}	795	}
		796
693		797
694	=item after $timeout, @msg	798	=item after $timeout, @msg
695		799
696	=item after $timeout, $callback	800	=item after $timeout, $callback
697		801
…		…
727		831
728	If an optional time-out (in seconds) is given and it is not C<undef>,	832	If an optional time-out (in seconds) is given and it is not C<undef>,
729	then the callback will be called without any arguments after the time-out	833	then the callback will be called without any arguments after the time-out
730	elapsed and the port is C<kil>ed.	834	elapsed and the port is C<kil>ed.
731		835
732	If no time-out is given, then the local port will monitor the remote port	836	If no time-out is given (or it is C<undef>), then the local port will
733	instead, so it eventually gets cleaned-up.	837	monitor the remote port instead, so it eventually gets cleaned-up.
734		838
735	Currently this function returns the temporary port, but this "feature"	839	Currently this function returns the temporary port, but this "feature"
736	might go in future versions unless you can make a convincing case that	840	might go in future versions unless you can make a convincing case that
737	this is indeed useful for something.	841	this is indeed useful for something.
738		842
…		…
787		891
788	=item * Node IDs are arbitrary strings in AEMP.	892	=item * Node IDs are arbitrary strings in AEMP.
789		893
790	Erlang relies on special naming and DNS to work everywhere in the same	894	Erlang relies on special naming and DNS to work everywhere in the same
791	way. AEMP relies on each node somehow knowing its own address(es) (e.g. by	895	way. AEMP relies on each node somehow knowing its own address(es) (e.g. by
792	configuration or DNS), but will otherwise discover other odes itself.	896	configuration or DNS), and possibly the addresses of some seed nodes, but
		897	will otherwise discover other nodes (and their IDs) itself.
793		898
794	=item * Erlang has a "remote ports are like local ports" philosophy, AEMP	899	=item * Erlang has a "remote ports are like local ports" philosophy, AEMP
795	uses "local ports are like remote ports".	900	uses "local ports are like remote ports".
796		901
797	The failure modes for local ports are quite different (runtime errors	902	The failure modes for local ports are quite different (runtime errors
…		…
806	ports being the special case/exception, where transport errors cannot	911	ports being the special case/exception, where transport errors cannot
807	occur.	912	occur.
808		913
809	=item * Erlang uses processes and a mailbox, AEMP does not queue.	914	=item * Erlang uses processes and a mailbox, AEMP does not queue.
810		915
811	Erlang uses processes that selectively receive messages, and therefore	916	Erlang uses processes that selectively receive messages out of order, and
812	needs a queue. AEMP is event based, queuing messages would serve no	917	therefore needs a queue. AEMP is event based, queuing messages would serve
813	useful purpose. For the same reason the pattern-matching abilities of	918	no useful purpose. For the same reason the pattern-matching abilities
814	AnyEvent::MP are more limited, as there is little need to be able to	919	of AnyEvent::MP are more limited, as there is little need to be able to
815	filter messages without dequeuing them.	920	filter messages without dequeuing them.
816		921
817	(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).	922	This is not a philosophical difference, but simply stems from AnyEvent::MP
		923	being event-based, while Erlang is process-based.
		924
		925	You cna have a look at L<Coro::MP> for a more Erlang-like process model on
		926	top of AEMP and Coro threads.
818		927
819	=item * Erlang sends are synchronous, AEMP sends are asynchronous.	928	=item * Erlang sends are synchronous, AEMP sends are asynchronous.
820		929
821	Sending messages in Erlang is synchronous and blocks the process (and	930	Sending messages in Erlang is synchronous and blocks the process until
		931	a conenction has been established and the message sent (and so does not
822	so does not need a queue that can overflow). AEMP sends are immediate,	932	need a queue that can overflow). AEMP sends return immediately, connection
823	connection establishment is handled in the background.	933	establishment is handled in the background.
824		934
825	=item * Erlang suffers from silent message loss, AEMP does not.	935	=item * Erlang suffers from silent message loss, AEMP does not.
826		936
827	Erlang makes few guarantees on messages delivery - messages can get lost	937	Erlang implements few guarantees on messages delivery - messages can get
828	without any of the processes realising it (i.e. you send messages a, b,	938	lost without any of the processes realising it (i.e. you send messages a,
829	and c, and the other side only receives messages a and c).	939	b, and c, and the other side only receives messages a and c).
830		940
831	AEMP guarantees correct ordering, and the guarantee that after one message	941	AEMP guarantees (modulo hardware errors) correct ordering, and the
832	is lost, all following ones sent to the same port are lost as well, until	942	guarantee that after one message is lost, all following ones sent to the
833	monitoring raises an error, so there are no silent "holes" in the message	943	same port are lost as well, until monitoring raises an error, so there are
834	sequence.	944	no silent "holes" in the message sequence.
		945
		946	If you want your software to be very reliable, you have to cope with
		947	corrupted and even out-of-order messages in both Erlang and AEMP. AEMP
		948	simply tries to work better in common error cases, such as when a network
		949	link goes down.
835		950
836	=item * Erlang can send messages to the wrong port, AEMP does not.	951	=item * Erlang can send messages to the wrong port, AEMP does not.
837		952
838	In Erlang it is quite likely that a node that restarts reuses a process ID	953	In Erlang it is quite likely that a node that restarts reuses an Erlang
839	known to other nodes for a completely different process, causing messages	954	process ID known to other nodes for a completely different process,
840	destined for that process to end up in an unrelated process.	955	causing messages destined for that process to end up in an unrelated
		956	process.
841		957
842	AEMP never reuses port IDs, so old messages or old port IDs floating	958	AEMP does not reuse port IDs, so old messages or old port IDs floating
843	around in the network will not be sent to an unrelated port.	959	around in the network will not be sent to an unrelated port.
844		960
845	=item * Erlang uses unprotected connections, AEMP uses secure	961	=item * Erlang uses unprotected connections, AEMP uses secure
846	authentication and can use TLS.	962	authentication and can use TLS.
847		963
…		…
850		966
851	=item * The AEMP protocol is optimised for both text-based and binary	967	=item * The AEMP protocol is optimised for both text-based and binary
852	communications.	968	communications.
853		969
854	The AEMP protocol, unlike the Erlang protocol, supports both programming	970	The AEMP protocol, unlike the Erlang protocol, supports both programming
855	language independent text-only protocols (good for debugging) and binary,	971	language independent text-only protocols (good for debugging), and binary,
856	language-specific serialisers (e.g. Storable). By default, unless TLS is	972	language-specific serialisers (e.g. Storable). By default, unless TLS is
857	used, the protocol is actually completely text-based.	973	used, the protocol is actually completely text-based.
858		974
859	It has also been carefully designed to be implementable in other languages	975	It has also been carefully designed to be implementable in other languages
860	with a minimum of work while gracefully degrading functionality to make the	976	with a minimum of work while gracefully degrading functionality to make the
861	protocol simple.	977	protocol simple.
862		978
863	=item * AEMP has more flexible monitoring options than Erlang.	979	=item * AEMP has more flexible monitoring options than Erlang.
864		980
865	In Erlang, you can chose to receive I<all> exit signals as messages	981	In Erlang, you can chose to receive I<all> exit signals as messages or
866	or I<none>, there is no in-between, so monitoring single processes is	982	I<none>, there is no in-between, so monitoring single Erlang processes is
867	difficult to implement. Monitoring in AEMP is more flexible than in	983	difficult to implement.
868	Erlang, as one can choose between automatic kill, exit message or callback	984
869	on a per-process basis.	985	Monitoring in AEMP is more flexible than in Erlang, as one can choose
		986	between automatic kill, exit message or callback on a per-port basis.
870		987
871	=item * Erlang tries to hide remote/local connections, AEMP does not.	988	=item * Erlang tries to hide remote/local connections, AEMP does not.
872		989
873	Monitoring in Erlang is not an indicator of process death/crashes, in the	990	Monitoring in Erlang is not an indicator of process death/crashes, in the
874	same way as linking is (except linking is unreliable in Erlang).	991	same way as linking is (except linking is unreliable in Erlang).
…		…
896	overhead, as well as having to keep a proxy object everywhere.	1013	overhead, as well as having to keep a proxy object everywhere.
897		1014
898	Strings can easily be printed, easily serialised etc. and need no special	1015	Strings can easily be printed, easily serialised etc. and need no special
899	procedures to be "valid".	1016	procedures to be "valid".
900		1017
901	And as a result, a miniport consists of a single closure stored in a	1018	And as a result, a port with just a default receiver consists of a single
902	global hash - it can't become much cheaper.	1019	code reference stored in a global hash - it can't become much cheaper.
903		1020
904	=item Why favour JSON, why not a real serialising format such as Storable?	1021	=item Why favour JSON, why not a real serialising format such as Storable?
905		1022
906	In fact, any AnyEvent::MP node will happily accept Storable as framing	1023	In fact, any AnyEvent::MP node will happily accept Storable as framing
907	format, but currently there is no way to make a node use Storable by	1024	format, but currently there is no way to make a node use Storable by
…		…
923		1040
924	L<AnyEvent::MP::Intro> - a gentle introduction.	1041	L<AnyEvent::MP::Intro> - a gentle introduction.
925		1042
926	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.	1043	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.
927		1044
928	L<AnyEvent::MP::Global> - network maintainance and port groups, to find	1045	L<AnyEvent::MP::Global> - network maintenance and port groups, to find
929	your applications.	1046	your applications.
		1047
		1048	L<AnyEvent::MP::DataConn> - establish data connections between nodes.
930		1049
931	L<AnyEvent::MP::LogCatcher> - simple service to display log messages from	1050	L<AnyEvent::MP::LogCatcher> - simple service to display log messages from
932	all nodes.	1051	all nodes.
933		1052
934	L<AnyEvent>.	1053	L<AnyEvent>.

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.95 by root, Wed Sep 23 11:57:16 2009 UTC vs. Revision 1.121 by root, Tue Feb 28 18:37:24 2012 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.95 by root, Wed Sep 23 11:57:16 2009 UTC vs.
Revision 1.121 by root, Tue Feb 28 18:37:24 2012 UTC