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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.33 by root, Wed Aug 5 22:40:51 2009 UTC vs.
Revision 1.43 by root, Sun Aug 9 16:08:16 2009 UTC

…		…
8		8
9	$NODE # contains this node's noderef	9	$NODE # contains this node's noderef
10	NODE # returns this node's noderef	10	NODE # returns this node's noderef
11	NODE $port # returns the noderef of the port	11	NODE $port # returns the noderef of the port
12		12
		13	$SELF # receiving/own port id in rcv callbacks
		14
		15	# ports are message endpoints
		16
		17	# sending messages
13	snd $port, type => data...;	18	snd $port, type => data...;
		19	snd $port, @msg;
		20	snd @msg_with_first_element_being_a_port;
14		21
15	$SELF # receiving/own port id in rcv callbacks	22	# miniports
		23	my $miniport = port { my @msg = @_; 0 };
16		24
		25	# full ports
		26	my $port = port;
17	rcv $port, smartmatch => $cb->($port, @msg);	27	rcv $port, smartmatch => $cb->(@msg);
18
19	# examples:
20	rcv $port2, ping => sub { snd $_[0], "pong"; 0 };	28	rcv $port, ping => sub { snd $_[0], "pong"; 0 };
21	rcv $port1, pong => sub { warn "pong received\n" };	29	rcv $port, pong => sub { warn "pong received\n"; 0 };
22	snd $port2, ping => $port1;	30
		31	# remote ports
		32	my $port = spawn $node, $initfunc, @initdata;
23		33
24	# more, smarter, matches (_any_ is exported by this module)	34	# more, smarter, matches (_any_ is exported by this module)
25	rcv $port, [child_died => $pid] => sub { ...	35	rcv $port, [child_died => $pid] => sub { ...
26	rcv $port, [_any_, _any_, 3] => sub { .. $_[2] is 3	36	rcv $port, [_any_, _any_, 3] => sub { .. $_[2] is 3
		37
		38	# monitoring
		39	mon $port, $cb->(@msg) # callback is invoked on death
		40	mon $port, $otherport # kill otherport on abnormal death
		41	mon $port, $otherport, @msg # send message on death
27		42
28	=head1 DESCRIPTION	43	=head1 DESCRIPTION
29		44
30	This module (-family) implements a simple message passing framework.	45	This module (-family) implements a simple message passing framework.
31		46
…		…
100		115
101	use AE ();	116	use AE ();
102		117
103	use base "Exporter";	118	use base "Exporter";
104		119
105	our $VERSION = '0.1';	120	our $VERSION = $AnyEvent::MP::Base::VERSION;
		121
106	our @EXPORT = qw(	122	our @EXPORT = qw(
107	NODE $NODE *SELF node_of _any_	123	NODE $NODE *SELF node_of _any_
108	resolve_node initialise_node	124	resolve_node initialise_node
109	snd rcv mon kil reg psub	125	snd rcv mon kil reg psub spawn
110	port	126	port
111	);	127	);
112		128
113	our $SELF;	129	our $SELF;
114		130
…		…
127		143
128	=item $noderef = node_of $port	144	=item $noderef = node_of $port
129		145
130	Extracts and returns the noderef from a portid or a noderef.	146	Extracts and returns the noderef from a portid or a noderef.
131		147
		148	=item initialise_node $noderef, $seednode, $seednode...
		149
		150	=item initialise_node "slave/", $master, $master...
		151
		152	Before a node can talk to other nodes on the network it has to initialise
		153	itself - the minimum a node needs to know is it's own name, and optionally
		154	it should know the noderefs of some other nodes in the network.
		155
		156	This function initialises a node - it must be called exactly once (or
		157	never) before calling other AnyEvent::MP functions.
		158
		159	All arguments are noderefs, which can be either resolved or unresolved.
		160
		161	There are two types of networked nodes, public nodes and slave nodes:
		162
		163	=over 4
		164
		165	=item public nodes
		166
		167	For public nodes, C<$noderef> must either be a (possibly unresolved)
		168	noderef, in which case it will be resolved, or C<undef> (or missing), in
		169	which case the noderef will be guessed.
		170
		171	Afterwards, the node will bind itself on all endpoints and try to connect
		172	to all additional C<$seednodes> that are specified. Seednodes are optional
		173	and can be used to quickly bootstrap the node into an existing network.
		174
		175	=item slave nodes
		176
		177	When the C<$noderef> is the special string C<slave/>, then the node will
		178	become a slave node. Slave nodes cannot be contacted from outside and will
		179	route most of their traffic to the master node that they attach to.
		180
		181	At least one additional noderef is required: The node will try to connect
		182	to all of them and will become a slave attached to the first node it can
		183	successfully connect to.
		184
		185	=back
		186
		187	This function will block until all nodes have been resolved and, for slave
		188	nodes, until it has successfully established a connection to a master
		189	server.
		190
		191	Example: become a public node listening on the default node.
		192
		193	initialise_node;
		194
		195	Example: become a public node, and try to contact some well-known master
		196	servers to become part of the network.
		197
		198	initialise_node undef, "master1", "master2";
		199
		200	Example: become a public node listening on port C<4041>.
		201
		202	initialise_node 4041;
		203
		204	Example: become a public node, only visible on localhost port 4044.
		205
		206	initialise_node "locahost:4044";
		207
		208	Example: become a slave node to any of the specified master servers.
		209
		210	initialise_node "slave/", "master1", "192.168.13.17", "mp.example.net";
		211
132	=item $cv = resolve_node $noderef	212	=item $cv = resolve_node $noderef
133		213
134	Takes an unresolved node reference that may contain hostnames and	214	Takes an unresolved node reference that may contain hostnames and
135	abbreviated IDs, resolves all of them and returns a resolved node	215	abbreviated IDs, resolves all of them and returns a resolved node
136	reference.	216	reference.
…		…
233	$port	313	$port
234	}	314	}
235		315
236	=item reg $port, $name	316	=item reg $port, $name
237		317
238	Registers the given port under the name C<$name>. If the name already	318	=item reg $name
239	exists it is replaced.	319
		320	Registers the given port (or C<$SELF><<< if missing) under the name
		321	C<$name>. If the name already exists it is replaced.
240		322
241	A port can only be registered under one well known name.	323	A port can only be registered under one well known name.
242		324
243	A port automatically becomes unregistered when it is killed.	325	A port automatically becomes unregistered when it is killed.
244		326
245	=cut	327	=cut
246		328
247	sub reg(@) {	329	sub reg(@) {
248	my ($port, $name) = @_;	330	my $port = @_ > 1 ? shift : $SELF \|\| Carp::croak 'reg: called with one argument only, but $SELF not set,';
249		331
250	$REG{$name} = $port;	332	$REG{$_[0]} = $port;
251	}	333	}
252		334
253	=item rcv $port, $callback->(@msg)	335	=item rcv $port, $callback->(@msg)
254		336
255	Replaces the callback on the specified miniport (after converting it to	337	Replaces the callback on the specified miniport (after converting it to
…		…
260	=item rcv $port, $smartmatch => $callback->(@msg), ...	342	=item rcv $port, $smartmatch => $callback->(@msg), ...
261		343
262	=item rcv $port, [$smartmatch...] => $callback->(@msg), ...	344	=item rcv $port, [$smartmatch...] => $callback->(@msg), ...
263		345
264	Register callbacks to be called on matching messages on the given full	346	Register callbacks to be called on matching messages on the given full
265	port (after converting it to one if required).	347	port (after converting it to one if required) and return the port.
266		348
267	The callback has to return a true value when its work is done, after	349	The callback has to return a true value when its work is done, after
268	which is will be removed, or a false value in which case it will stay	350	which is will be removed, or a false value in which case it will stay
269	registered.	351	registered.
270		352
271	The global C<$SELF> (exported by this module) contains C<$port> while	353	The global C<$SELF> (exported by this module) contains C<$port> while
272	executing the callback.	354	executing the callback.
273		355
274	Runtime errors wdurign callback execution will result in the port being	356	Runtime errors during callback execution will result in the port being
275	C<kil>ed.	357	C<kil>ed.
276		358
277	If the match is an array reference, then it will be matched against the	359	If the match is an array reference, then it will be matched against the
278	first elements of the message, otherwise only the first element is being	360	first elements of the message, otherwise only the first element is being
279	matched.	361	matched.
…		…
282	exported by this module) matches any single element of the message.	364	exported by this module) matches any single element of the message.
283		365
284	While not required, it is highly recommended that the first matching	366	While not required, it is highly recommended that the first matching
285	element is a string identifying the message. The one-string-only match is	367	element is a string identifying the message. The one-string-only match is
286	also the most efficient match (by far).	368	also the most efficient match (by far).
		369
		370	Example: create a port and bind receivers on it in one go.
		371
		372	my $port = rcv port,
		373	msg1 => sub { ...; 0 },
		374	msg2 => sub { ...; 0 },
		375	;
		376
		377	Example: create a port, bind receivers and send it in a message elsewhere
		378	in one go:
		379
		380	snd $otherport, reply =>
		381	rcv port,
		382	msg1 => sub { ...; 0 },
		383	...
		384	;
287		385
288	=cut	386	=cut
289		387
290	sub rcv($@) {	388	sub rcv($@) {
291	my $port = shift;	389	my $port = shift;
…		…
398	}	496	}
399	}	497	}
400		498
401	=item $guard = mon $port, $cb->(@reason)	499	=item $guard = mon $port, $cb->(@reason)
402		500
403	=item $guard = mon $port, $otherport	501	=item $guard = mon $port, $rcvport
404		502
		503	=item $guard = mon $port
		504
405	=item $guard = mon $port, $otherport, @msg	505	=item $guard = mon $port, $rcvport, @msg
406		506
407	Monitor the given port and do something when the port is killed.	507	Monitor the given port and do something when the port is killed or
		508	messages to it were lost, and optionally return a guard that can be used
		509	to stop monitoring again.
408		510
		511	C<mon> effectively guarantees that, in the absence of hardware failures,
		512	that after starting the monitor, either all messages sent to the port
		513	will arrive, or the monitoring action will be invoked after possible
		514	message loss has been detected. No messages will be lost "in between"
		515	(after the first lost message no further messages will be received by the
		516	port). After the monitoring action was invoked, further messages might get
		517	delivered again.
		518
409	In the first form, the callback is simply called with any number	519	In the first form (callback), the callback is simply called with any
410	of C<@reason> elements (no @reason means that the port was deleted	520	number of C<@reason> elements (no @reason means that the port was deleted
411	"normally"). Note also that I<< the callback B<must> never die >>, so use	521	"normally"). Note also that I<< the callback B<must> never die >>, so use
412	C<eval> if unsure.	522	C<eval> if unsure.
413		523
414	In the second form, the other port will be C<kil>'ed with C<@reason>, iff	524	In the second form (another port given), the other port (C<$rcvport>)
415	a @reason was specified, i.e. on "normal" kils nothing happens, while	525	will be C<kil>'ed with C<@reason>, iff a @reason was specified, i.e. on
416	under all other conditions, the other port is killed with the same reason.	526	"normal" kils nothing happens, while under all other conditions, the other
		527	port is killed with the same reason.
417		528
		529	The third form (kill self) is the same as the second form, except that
		530	C<$rvport> defaults to C<$SELF>.
		531
418	In the last form, a message of the form C<@msg, @reason> will be C<snd>.	532	In the last form (message), a message of the form C<@msg, @reason> will be
		533	C<snd>.
		534
		535	As a rule of thumb, monitoring requests should always monitor a port from
		536	a local port (or callback). The reason is that kill messages might get
		537	lost, just like any other message. Another less obvious reason is that
		538	even monitoring requests can get lost (for exmaple, when the connection
		539	to the other node goes down permanently). When monitoring a port locally
		540	these problems do not exist.
419		541
420	Example: call a given callback when C<$port> is killed.	542	Example: call a given callback when C<$port> is killed.
421		543
422	mon $port, sub { warn "port died because of <@_>\n" };	544	mon $port, sub { warn "port died because of <@_>\n" };
423		545
424	Example: kill ourselves when C<$port> is killed abnormally.	546	Example: kill ourselves when C<$port> is killed abnormally.
425		547
426	mon $port, $self;	548	mon $port;
427		549
428	Example: send us a restart message another C<$port> is killed.	550	Example: send us a restart message when another C<$port> is killed.
429		551
430	mon $port, $self => "restart";	552	mon $port, $self => "restart";
431		553
432	=cut	554	=cut
433		555
434	sub mon {	556	sub mon {
435	my ($noderef, $port) = split /#/, shift, 2;	557	my ($noderef, $port) = split /#/, shift, 2;
436		558
437	my $node = $NODE{$noderef} \|\| add_node $noderef;	559	my $node = $NODE{$noderef} \|\| add_node $noderef;
438		560
439	my $cb = shift;	561	my $cb = @_ ? shift : $SELF \|\| Carp::croak 'mon: called with one argument only, but $SELF not set,';
440		562
441	unless (ref $cb) {	563	unless (ref $cb) {
442	if (@_) {	564	if (@_) {
443	# send a kill info message	565	# send a kill info message
444	my (@msg) = ($cb, @_);	566	my (@msg) = ($cb, @_);
…		…
475	=cut	597	=cut
476		598
477	sub mon_guard {	599	sub mon_guard {
478	my ($port, @refs) = @_;	600	my ($port, @refs) = @_;
479		601
		602	#TODO: mon-less form?
		603
480	mon $port, sub { 0 && @refs }	604	mon $port, sub { 0 && @refs }
481	}	605	}
482		606
483	=item lnk $port1, $port2
484
485	Link two ports. This is simply a shorthand for:
486
487	mon $port1, $port2;
488	mon $port2, $port1;
489
490	It means that if either one is killed abnormally, the other one gets
491	killed as well.
492
493	=item kil $port[, @reason]	607	=item kil $port[, @reason]
494		608
495	Kill the specified port with the given C<@reason>.	609	Kill the specified port with the given C<@reason>.
496		610
497	If no C<@reason> is specified, then the port is killed "normally" (linked	611	If no C<@reason> is specified, then the port is killed "normally" (linked
…		…
504	will be reported as reason C<< die => $@ >>.	618	will be reported as reason C<< die => $@ >>.
505		619
506	Transport/communication errors are reported as C<< transport_error =>	620	Transport/communication errors are reported as C<< transport_error =>
507	$message >>.	621	$message >>.
508		622
509	=back
510
511	=head1 FUNCTIONS FOR NODES
512
513	=over 4
514
515	=item initialise_node $noderef, $seednode, $seednode...
516
517	=item initialise_node "slave/", $master, $master...
518
519	Initialises a node - must be called exactly once before calling other
520	AnyEvent::MP functions when talking to other nodes is required.
521
522	All arguments are noderefs, which can be either resolved or unresolved.
523
524	There are two types of networked nodes, public nodes and slave nodes:
525
526	=over 4
527
528	=item public nodes
529
530	For public nodes, C<$noderef> must either be a (possibly unresolved)
531	noderef, in which case it will be resolved, or C<undef> (or missing), in
532	which case the noderef will be guessed.
533
534	Afterwards, the node will bind itself on all endpoints and try to connect
535	to all additional C<$seednodes> that are specified. Seednodes are optional
536	and can be used to quickly bootstrap the node into an existing network.
537
538	=item slave nodes
539
540	When the C<$noderef> is the special string C<slave/>, then the node will
541	become a slave node. Slave nodes cannot be contacted from outside and will
542	route most of their traffic to the master node that they attach to.
543
544	At least one additional noderef is required: The node will try to connect
545	to all of them and will become a slave attached to the first node it can
546	successfully connect to.
547
548	=back
549
550	This function will block until all nodes have been resolved and, for slave
551	nodes, until it has successfully established a connection to a master
552	server.
553
554	Example: become a public node listening on the default node.
555
556	initialise_node;
557
558	Example: become a public node, and try to contact some well-known master
559	servers to become part of the network.
560
561	initialise_node undef, "master1", "master2";
562
563	Example: become a public node listening on port C<4041>.
564
565	initialise_node 4041;
566
567	Example: become a public node, only visible on localhost port 4044.
568
569	initialise_node "locahost:4044";
570
571	Example: become a slave node to any of the specified master servers.
572
573	initialise_node "slave/", "master1", "192.168.13.17", "mp.example.net";
574
575	=cut	623	=cut
		624
		625	=item $port = spawn $node, $initfunc[, @initdata]
		626
		627	Creates a port on the node C<$node> (which can also be a port ID, in which
		628	case it's the node where that port resides).
		629
		630	The port ID of the newly created port is return immediately, and it is
		631	permissible to immediately start sending messages or monitor the port.
		632
		633	After the port has been created, the init function is
		634	called. This function must be a fully-qualified function name
		635	(e.g. C<MyApp::Chat::Server::init>). To specify a function in the main
		636	program, use C<::name>.
		637
		638	If the function doesn't exist, then the node tries to C<require>
		639	the package, then the package above the package and so on (e.g.
		640	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
		641	exists or it runs out of package names.
		642
		643	The init function is then called with the newly-created port as context
		644	object (C<$SELF>) and the C<@initdata> values as arguments.
		645
		646	A common idiom is to pass your own port, monitor the spawned port, and
		647	in the init function, monitor the original port. This two-way monitoring
		648	ensures that both ports get cleaned up when there is a problem.
		649
		650	Example: spawn a chat server port on C<$othernode>.
		651
		652	# this node, executed from within a port context:
		653	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;
		654	mon $server;
		655
		656	# init function on C<$othernode>
		657	sub connect {
		658	my ($srcport) = @_;
		659
		660	mon $srcport;
		661
		662	rcv $SELF, sub {
		663	...
		664	};
		665	}
		666
		667	=cut
		668
		669	sub _spawn {
		670	my $port = shift;
		671	my $init = shift;
		672
		673	local $SELF = "$NODE#$port";
		674	eval {
		675	&{ load_func $init }
		676	};
		677	_self_die if $@;
		678	}
		679
		680	sub spawn(@) {
		681	my ($noderef, undef) = split /#/, shift, 2;
		682
		683	my $id = "$RUNIQ." . $ID++;
		684
		685	$_[0] =~ /::/
		686	or Carp::croak "spawn init function must be a fully-qualified name, caught";
		687
		688	($NODE{$noderef} \|\| add_node $noderef)
		689	->send (["", "AnyEvent::MP::_spawn" => $id, @_]);
		690
		691	"$noderef#$id"
		692	}
576		693
577	=back	694	=back
578		695
579	=head1 NODE MESSAGES	696	=head1 NODE MESSAGES
580		697
…		…
622		739
623	=back	740	=back
624		741
625	=head1 AnyEvent::MP vs. Distributed Erlang	742	=head1 AnyEvent::MP vs. Distributed Erlang
626		743
627	AnyEvent::MP got lots of its ideas from distributed erlang (erlang node	744	AnyEvent::MP got lots of its ideas from distributed Erlang (Erlang node
628	== aemp node, erlang process == aemp port), so many of the documents and	745	== aemp node, Erlang process == aemp port), so many of the documents and
629	programming techniques employed by erlang apply to AnyEvent::MP. Here is a	746	programming techniques employed by Erlang apply to AnyEvent::MP. Here is a
630	sample:	747	sample:
631		748
632	http://www.erlang.se/doc/programming_rules.shtml	749	http://www.Erlang.se/doc/programming_rules.shtml
633	http://erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4	750	http://Erlang.org/doc/getting_started/part_frame.html # chapters 3 and 4
634	http://erlang.org/download/erlang-book-part1.pdf # chapters 5 and 6	751	http://Erlang.org/download/Erlang-book-part1.pdf # chapters 5 and 6
635	http://erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5	752	http://Erlang.org/download/armstrong_thesis_2003.pdf # chapters 4 and 5
636		753
637	Despite the similarities, there are also some important differences:	754	Despite the similarities, there are also some important differences:
638		755
639	=over 4	756	=over 4
640		757
…		…
651		768
652	Erlang uses processes that selctively receive messages, and therefore	769	Erlang uses processes that selctively receive messages, and therefore
653	needs a queue. AEMP is event based, queuing messages would serve no useful	770	needs a queue. AEMP is event based, queuing messages would serve no useful
654	purpose.	771	purpose.
655		772
656	(But see L<Coro::MP> for a more erlang-like process model on top of AEMP).	773	(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).
657		774
658	=item * Erlang sends are synchronous, AEMP sends are asynchronous.	775	=item * Erlang sends are synchronous, AEMP sends are asynchronous.
659		776
660	Sending messages in erlang is synchronous and blocks the process. AEMP	777	Sending messages in Erlang is synchronous and blocks the process. AEMP
661	sends are immediate, connection establishment is handled in the	778	sends are immediate, connection establishment is handled in the
662	background.	779	background.
663		780
664	=item * Erlang can silently lose messages, AEMP cannot.	781	=item * Erlang can silently lose messages, AEMP cannot.
665		782
…		…
668	and c, and the other side only receives messages a and c).	785	and c, and the other side only receives messages a and c).
669		786
670	AEMP guarantees correct ordering, and the guarantee that there are no	787	AEMP guarantees correct ordering, and the guarantee that there are no
671	holes in the message sequence.	788	holes in the message sequence.
672		789
673	=item * In erlang, processes can be declared dead and later be found to be	790	=item * In Erlang, processes can be declared dead and later be found to be
674	alive.	791	alive.
675		792
676	In erlang it can happen that a monitored process is declared dead and	793	In Erlang it can happen that a monitored process is declared dead and
677	linked processes get killed, but later it turns out that the process is	794	linked processes get killed, but later it turns out that the process is
678	still alive - and can receive messages.	795	still alive - and can receive messages.
679		796
680	In AEMP, when port monitoring detects a port as dead, then that port will	797	In AEMP, when port monitoring detects a port as dead, then that port will
681	eventually be killed - it cannot happen that a node detects a port as dead	798	eventually be killed - it cannot happen that a node detects a port as dead
682	and then later sends messages to it, finding it is still alive.	799	and then later sends messages to it, finding it is still alive.
683		800
684	=item * Erlang can send messages to the wrong port, AEMP does not.	801	=item * Erlang can send messages to the wrong port, AEMP does not.
685		802
686	In erlang it is quite possible that a node that restarts reuses a process	803	In Erlang it is quite possible that a node that restarts reuses a process
687	ID known to other nodes for a completely different process, causing	804	ID known to other nodes for a completely different process, causing
688	messages destined for that process to end up in an unrelated process.	805	messages destined for that process to end up in an unrelated process.
689		806
690	AEMP never reuses port IDs, so old messages or old port IDs floating	807	AEMP never reuses port IDs, so old messages or old port IDs floating
691	around in the network will not be sent to an unrelated port.	808	around in the network will not be sent to an unrelated port.
…		…
697	securely authenticate nodes.	814	securely authenticate nodes.
698		815
699	=item * The AEMP protocol is optimised for both text-based and binary	816	=item * The AEMP protocol is optimised for both text-based and binary
700	communications.	817	communications.
701		818
702	The AEMP protocol, unlike the erlang protocol, supports both	819	The AEMP protocol, unlike the Erlang protocol, supports both
703	language-independent text-only protocols (good for debugging) and binary,	820	language-independent text-only protocols (good for debugging) and binary,
704	language-specific serialisers (e.g. Storable).	821	language-specific serialisers (e.g. Storable).
705		822
706	It has also been carefully designed to be implementable in other languages	823	It has also been carefully designed to be implementable in other languages
707	with a minimum of work while gracefully degrading fucntionality to make the	824	with a minimum of work while gracefully degrading fucntionality to make the
708	protocol simple.	825	protocol simple.
709		826
		827	=item * AEMP has more flexible monitoring options than Erlang.
		828
		829	In Erlang, you can chose to receive I<all> exit signals as messages
		830	or I<none>, there is no in-between, so monitoring single processes is
		831	difficult to implement. Monitoring in AEMP is more flexible than in
		832	Erlang, as one can choose between automatic kill, exit message or callback
		833	on a per-process basis.
		834
		835	=item * Erlang tries to hide remote/local connections, AEMP does not.
		836
		837	Monitoring in Erlang is not an indicator of process death/crashes,
		838	as linking is (except linking is unreliable in Erlang).
		839
		840	In AEMP, you don't "look up" registered port names or send to named ports
		841	that might or might not be persistent. Instead, you normally spawn a port
		842	on the remote node. The init function monitors the you, and you monitor
		843	the remote port. Since both monitors are local to the node, they are much
		844	more reliable.
		845
		846	This also saves round-trips and avoids sending messages to the wrong port
		847	(hard to do in Erlang).
		848
710	=back	849	=back
711		850
712	=head1 SEE ALSO	851	=head1 SEE ALSO
713		852
714	L<AnyEvent>.	853	L<AnyEvent>.

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.33 by root, Wed Aug 5 22:40:51 2009 UTC vs. Revision 1.43 by root, Sun Aug 9 16:08:16 2009 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.33 by root, Wed Aug 5 22:40:51 2009 UTC vs.
Revision 1.43 by root, Sun Aug 9 16:08:16 2009 UTC