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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.65 by root, Fri Aug 28 01:00:34 2009 UTC vs.
Revision 1.70 by root, Sun Aug 30 19:49:47 2009 UTC

…		…
40		40
41	=head1 CURRENT STATUS	41	=head1 CURRENT STATUS
42		42
43	AnyEvent::MP - stable API, should work	43	AnyEvent::MP - stable API, should work
44	AnyEvent::MP::Intro - outdated	44	AnyEvent::MP::Intro - outdated
45	AnyEvent::MP::Kernel - WIP
46	AnyEvent::MP::Transport - mostly stable	45	AnyEvent::MP::Kernel - mostly stable
		46	AnyEvent::MP::Global - mostly stable
		47	AnyEvent::MP::Node - mostly stable, but internal anyways
		48	AnyEvent::MP::Transport - mostly stable, but internal anyways
47		49
48	stay tuned.	50	stay tuned.
49		51
50	=head1 DESCRIPTION	52	=head1 DESCRIPTION
51		53
52	This module (-family) implements a simple message passing framework.	54	This module (-family) implements a simple message passing framework.
53		55
54	Despite its simplicity, you can securely message other processes running	56	Despite its simplicity, you can securely message other processes running
55	on the same or other hosts.	57	on the same or other hosts, and you can supervise entities remotely.
56		58
57	For an introduction to this module family, see the L<AnyEvent::MP::Intro>	59	For an introduction to this module family, see the L<AnyEvent::MP::Intro>
58	manual page.	60	manual page and the examples under F<eg/>.
59		61
60	At the moment, this module family is severly broken and underdocumented,	62	At the moment, this module family is a bit underdocumented.
61	so do not use. This was uploaded mainly to reserve the CPAN namespace -
62	stay tuned!
63		63
64	=head1 CONCEPTS	64	=head1 CONCEPTS
65		65
66	=over 4	66	=over 4
67		67
…		…
71		71
72	Ports allow you to register C<rcv> handlers that can match all or just	72	Ports allow you to register C<rcv> handlers that can match all or just
73	some messages. Messages send to ports will not be queued, regardless of	73	some messages. Messages send to ports will not be queued, regardless of
74	anything was listening for them or not.	74	anything was listening for them or not.
75		75
76	=item port ID - C<noderef#portname>	76	=item port ID - C<nodeid#portname>
77		77
78	A port ID is the concatenation of a noderef, a hash-mark (C<#>) as	78	A port ID is the concatenation of a node ID, a hash-mark (C<#>) as
79	separator, and a port name (a printable string of unspecified format). An	79	separator, and a port name (a printable string of unspecified format).
80	exception is the the node port, whose ID is identical to its node
81	reference.
82		80
83	=item node	81	=item node
84		82
85	A node is a single process containing at least one port - the node port,	83	A node is a single process containing at least one port - the node port,
86	which provides nodes to manage each other remotely, and to create new	84	which enables nodes to manage each other remotely, and to create new
87	ports.	85	ports.
88		86
89	Nodes are either private (single-process only), slaves (can only talk to	87	Nodes are either public (have one or more listening ports) or private
90	public nodes, but do not need an open port) or public nodes (connectable	88	(no listening ports). Private nodes cannot talk to other private nodes
91	from any other node).	89	currently.
92		90
93	=item node ID - C<[a-za-Z0-9_\-.:]+>	91	=item node ID - C<[a-za-Z0-9_\-.:]+>
94		92
95	A node ID is a string that uniquely identifies the node within a	93	A node ID is a string that uniquely identifies the node within a
96	network. Depending on the configuration used, node IDs can look like a	94	network. Depending on the configuration used, node IDs can look like a
…		…
114	are expected to be long-running, and at least one of those should always	112	are expected to be long-running, and at least one of those should always
115	be available. When nodes run out of connections (e.g. due to a network	113	be available. When nodes run out of connections (e.g. due to a network
116	error), they try to re-establish connections to some seednodes again to	114	error), they try to re-establish connections to some seednodes again to
117	join the network.	115	join the network.
118		116
		117	Apart from being sued for seeding, seednodes are not special in any way -
		118	every public node can be a seednode.
		119
119	=back	120	=back
120		121
121	=head1 VARIABLES/FUNCTIONS	122	=head1 VARIABLES/FUNCTIONS
122		123
123	=over 4	124	=over 4
…		…
138		139
139	our $VERSION = $AnyEvent::MP::Kernel::VERSION;	140	our $VERSION = $AnyEvent::MP::Kernel::VERSION;
140		141
141	our @EXPORT = qw(	142	our @EXPORT = qw(
142	NODE $NODE *SELF node_of after	143	NODE $NODE *SELF node_of after
143	resolve_node initialise_node	144	initialise_node
144	snd rcv mon mon_guard kil reg psub spawn	145	snd rcv mon mon_guard kil reg psub spawn
145	port	146	port
146	);	147	);
147		148
148	our $SELF;	149	our $SELF;
…		…
153	kil $SELF, die => $msg;	154	kil $SELF, die => $msg;
154	}	155	}
155		156
156	=item $thisnode = NODE / $NODE	157	=item $thisnode = NODE / $NODE
157		158
158	The C<NODE> function returns, and the C<$NODE> variable contains the node	159	The C<NODE> function returns, and the C<$NODE> variable contains, the node
159	ID of the node running in the current process. This value is initialised by	160	ID of the node running in the current process. This value is initialised by
160	a call to C<initialise_node>.	161	a call to C<initialise_node>.
161		162
162	=item $nodeid = node_of $port	163	=item $nodeid = node_of $port
163		164
164	Extracts and returns the node ID part from a port ID or a node ID.	165	Extracts and returns the node ID from a port ID or a node ID.
165		166
166	=item initialise_node $profile_name	167	=item initialise_node $profile_name, key => value...
167		168
168	Before a node can talk to other nodes on the network (i.e. enter	169	Before a node can talk to other nodes on the network (i.e. enter
169	"distributed mode") it has to initialise itself - the minimum a node needs	170	"distributed mode") it has to initialise itself - the minimum a node needs
170	to know is its own name, and optionally it should know the addresses of	171	to know is its own name, and optionally it should know the addresses of
171	some other nodes in the network to discover other nodes.	172	some other nodes in the network to discover other nodes.
…		…
174	never) before calling other AnyEvent::MP functions.	175	never) before calling other AnyEvent::MP functions.
175		176
176	The first argument is a profile name. If it is C<undef> or missing, then	177	The first argument is a profile name. If it is C<undef> or missing, then
177	the current nodename will be used instead (i.e. F<uname -n>).	178	the current nodename will be used instead (i.e. F<uname -n>).
178		179
179	The function then looks up the profile in the aemp configuration (see the	180	The function first looks up the profile in the aemp configuration (see the
180	L<aemp> commandline utility).	181	L<aemp> commandline utility). the profile is calculated as follows:
		182
		183	First, all remaining key => value pairs (all of which are conviniently
		184	undocumented at the moment) will be used. Then they will be overwritten by
		185	any values specified in the global default configuration (see the F<aemp>
		186	utility), then the chain of profiles selected, if any. That means that
		187	the values specified in the profile have highest priority and the values
		188	specified via C<initialise_node> have lowest priority.
181		189
182	If the profile specifies a node ID, then this will become the node ID of	190	If the profile specifies a node ID, then this will become the node ID of
183	this process. If not, then the profile name will be used as node ID. The	191	this process. If not, then the profile name will be used as node ID. The
184	special node ID of C<anon/> will be replaced by a random node ID.	192	special node ID of C<anon/> will be replaced by a random node ID.
185		193
…		…
187	aemp protocol listeners on all binds specified (it is possible and valid	195	aemp protocol listeners on all binds specified (it is possible and valid
188	to have no binds, meaning that the node cannot be contacted form the	196	to have no binds, meaning that the node cannot be contacted form the
189	outside. This means the node cannot talk to other nodes that also have no	197	outside. This means the node cannot talk to other nodes that also have no
190	binds, but it can still talk to all "normal" nodes).	198	binds, but it can still talk to all "normal" nodes).
191		199
192	If the profile does not specify a binds list, then the node ID will be	200	If the profile does not specify a binds list, then a default of C<*> is
193	treated as if it were of the form C<host:port>, which will be resolved and	201	used.
194	used as binds list.
195		202
196	Lastly, the seeds list from the profile is passed to the	203	Lastly, the seeds list from the profile is passed to the
197	L<AnyEvent::MP::Global> module, which will then use it to keep	204	L<AnyEvent::MP::Global> module, which will then use it to keep
198	connectivity with at least on of those seed nodes at any point in time.	205	connectivity with at least on of those seed nodes at any point in time.
199		206
…		…
217	=item $SELF	224	=item $SELF
218		225
219	Contains the current port id while executing C<rcv> callbacks or C<psub>	226	Contains the current port id while executing C<rcv> callbacks or C<psub>
220	blocks.	227	blocks.
221		228
222	=item SELF, %SELF, @SELF...	229	=item *SELF, SELF, %SELF, @SELF...
223		230
224	Due to some quirks in how perl exports variables, it is impossible to	231	Due to some quirks in how perl exports variables, it is impossible to
225	just export C<$SELF>, all the symbols called C<SELF> are exported by this	232	just export C<$SELF>, all the symbols named C<SELF> are exported by this
226	module, but only C<$SELF> is currently used.	233	module, but only C<$SELF> is currently used.
227		234
228	=item snd $port, type => @data	235	=item snd $port, type => @data
229		236
230	=item snd $port, @msg	237	=item snd $port, @msg
231		238
232	Send the given message to the given port ID, which can identify either	239	Send the given message to the given port, which can identify either a
233	a local or a remote port, and must be a port ID.	240	local or a remote port, and must be a port ID.
234		241
235	While the message can be about anything, it is highly recommended to use a	242	While the message can be almost anything, it is highly recommended to
236	string as first element (a port ID, or some word that indicates a request	243	use a string as first element (a port ID, or some word that indicates a
237	type etc.).	244	request type etc.) and to consist if only simple perl values (scalars,
		245	arrays, hashes) - if you think you need to pass an object, think again.
238		246
239	The message data effectively becomes read-only after a call to this	247	The message data logically becomes read-only after a call to this
240	function: modifying any argument is not allowed and can cause many	248	function: modifying any argument (or values referenced by them) is
241	problems.	249	forbidden, as there can be considerable time between the call to C<snd>
		250	and the time the message is actually being serialised - in fact, it might
		251	never be copied as within the same process it is simply handed to the
		252	receiving port.
242		253
243	The type of data you can transfer depends on the transport protocol: when	254	The type of data you can transfer depends on the transport protocol: when
244	JSON is used, then only strings, numbers and arrays and hashes consisting	255	JSON is used, then only strings, numbers and arrays and hashes consisting
245	of those are allowed (no objects). When Storable is used, then anything	256	of those are allowed (no objects). When Storable is used, then anything
246	that Storable can serialise and deserialise is allowed, and for the local	257	that Storable can serialise and deserialise is allowed, and for the local
247	node, anything can be passed.	258	node, anything can be passed. Best rely only on the common denominator of
		259	these.
248		260
249	=item $local_port = port	261	=item $local_port = port
250		262
251	Create a new local port object and returns its port ID. Initially it has	263	Create a new local port object and returns its port ID. Initially it has
252	no callbacks set and will throw an error when it receives messages.	264	no callbacks set and will throw an error when it receives messages.
…		…
428	$res	440	$res
429	}	441	}
430	}	442	}
431	}	443	}
432		444
433	=item $guard = mon $port, $cb->(@reason)	445	=item $guard = mon $port, $cb->(@reason) # call $cb when $port dies
434		446
435	=item $guard = mon $port, $rcvport	447	=item $guard = mon $port, $rcvport # kill $rcvport when $port dies
436		448
437	=item $guard = mon $port	449	=item $guard = mon $port # kill $SELF when $port dies
438		450
439	=item $guard = mon $port, $rcvport, @msg	451	=item $guard = mon $port, $rcvport, @msg # send a message when $port dies
440		452
441	Monitor the given port and do something when the port is killed or	453	Monitor the given port and do something when the port is killed or
442	messages to it were lost, and optionally return a guard that can be used	454	messages to it were lost, and optionally return a guard that can be used
443	to stop monitoring again.	455	to stop monitoring again.
444		456
445	C<mon> effectively guarantees that, in the absence of hardware failures,	457	C<mon> effectively guarantees that, in the absence of hardware failures,
446	that after starting the monitor, either all messages sent to the port	458	after starting the monitor, either all messages sent to the port will
447	will arrive, or the monitoring action will be invoked after possible	459	arrive, or the monitoring action will be invoked after possible message
448	message loss has been detected. No messages will be lost "in between"	460	loss has been detected. No messages will be lost "in between" (after
449	(after the first lost message no further messages will be received by the	461	the first lost message no further messages will be received by the
450	port). After the monitoring action was invoked, further messages might get	462	port). After the monitoring action was invoked, further messages might get
451	delivered again.	463	delivered again.
452		464
453	Note that monitoring-actions are one-shot: once released, they are removed	465	Note that monitoring-actions are one-shot: once messages are lost (and a
454	and will not trigger again.	466	monitoring alert was raised), they are removed and will not trigger again.
455		467
456	In the first form (callback), the callback is simply called with any	468	In the first form (callback), the callback is simply called with any
457	number of C<@reason> elements (no @reason means that the port was deleted	469	number of C<@reason> elements (no @reason means that the port was deleted
458	"normally"). Note also that I<< the callback B<must> never die >>, so use	470	"normally"). Note also that I<< the callback B<must> never die >>, so use
459	C<eval> if unsure.	471	C<eval> if unsure.
…		…
521	is killed, the references will be freed.	533	is killed, the references will be freed.
522		534
523	Optionally returns a guard that will stop the monitoring.	535	Optionally returns a guard that will stop the monitoring.
524		536
525	This function is useful when you create e.g. timers or other watchers and	537	This function is useful when you create e.g. timers or other watchers and
526	want to free them when the port gets killed:	538	want to free them when the port gets killed (note the use of C<psub>):
527		539
528	$port->rcv (start => sub {	540	$port->rcv (start => sub {
529	my $timer; $timer = mon_guard $port, AE::timer 1, 1, sub {	541	my $timer; $timer = mon_guard $port, AE::timer 1, 1, psub {
530	undef $timer if 0.9 < rand;	542	undef $timer if 0.9 < rand;
531	});	543	});
532	});	544	});
533		545
534	=cut	546	=cut
…		…
543		555
544	=item kil $port[, @reason]	556	=item kil $port[, @reason]
545		557
546	Kill the specified port with the given C<@reason>.	558	Kill the specified port with the given C<@reason>.
547		559
548	If no C<@reason> is specified, then the port is killed "normally" (linked	560	If no C<@reason> is specified, then the port is killed "normally" (ports
549	ports will not be kileld, or even notified).	561	monitoring other ports will not necessarily die because a port dies
		562	"normally").
550		563
551	Otherwise, linked ports get killed with the same reason (second form of	564	Otherwise, linked ports get killed with the same reason (second form of
552	C<mon>, see below).	565	C<mon>, see above).
553		566
554	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks	567	Runtime errors while evaluating C<rcv> callbacks or inside C<psub> blocks
555	will be reported as reason C<< die => $@ >>.	568	will be reported as reason C<< die => $@ >>.
556		569
557	Transport/communication errors are reported as C<< transport_error =>	570	Transport/communication errors are reported as C<< transport_error =>
…		…
562	=item $port = spawn $node, $initfunc[, @initdata]	575	=item $port = spawn $node, $initfunc[, @initdata]
563		576
564	Creates a port on the node C<$node> (which can also be a port ID, in which	577	Creates a port on the node C<$node> (which can also be a port ID, in which
565	case it's the node where that port resides).	578	case it's the node where that port resides).
566		579
567	The port ID of the newly created port is return immediately, and it is	580	The port ID of the newly created port is returned immediately, and it is
568	permissible to immediately start sending messages or monitor the port.	581	possible to immediately start sending messages or to monitor the port.
569		582
570	After the port has been created, the init function is	583	After the port has been created, the init function is called on the remote
571	called. This function must be a fully-qualified function name	584	node, in the same context as a C<rcv> callback. This function must be a
572	(e.g. C<MyApp::Chat::Server::init>). To specify a function in the main	585	fully-qualified function name (e.g. C<MyApp::Chat::Server::init>). To
573	program, use C<::name>.	586	specify a function in the main program, use C<::name>.
574		587
575	If the function doesn't exist, then the node tries to C<require>	588	If the function doesn't exist, then the node tries to C<require>
576	the package, then the package above the package and so on (e.g.	589	the package, then the package above the package and so on (e.g.
577	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function	590	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
578	exists or it runs out of package names.	591	exists or it runs out of package names.
579		592
580	The init function is then called with the newly-created port as context	593	The init function is then called with the newly-created port as context
581	object (C<$SELF>) and the C<@initdata> values as arguments.	594	object (C<$SELF>) and the C<@initdata> values as arguments.
582		595
583	A common idiom is to pass your own port, monitor the spawned port, and	596	A common idiom is to pass a local port, immediately monitor the spawned
584	in the init function, monitor the original port. This two-way monitoring	597	port, and in the remote init function, immediately monitor the passed
585	ensures that both ports get cleaned up when there is a problem.	598	local port. This two-way monitoring ensures that both ports get cleaned up
		599	when there is a problem.
586		600
587	Example: spawn a chat server port on C<$othernode>.	601	Example: spawn a chat server port on C<$othernode>.
588		602
589	# this node, executed from within a port context:	603	# this node, executed from within a port context:
590	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;	604	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;
…		…
632	=item after $timeout, $callback	646	=item after $timeout, $callback
633		647
634	Either sends the given message, or call the given callback, after the	648	Either sends the given message, or call the given callback, after the
635	specified number of seconds.	649	specified number of seconds.
636		650
637	This is simply a utility function that come sin handy at times.	651	This is simply a utility function that comes in handy at times - the
		652	AnyEvent::MP author is not convinced of the wisdom of having it, though,
		653	so it may go away in the future.
638		654
639	=cut	655	=cut
640		656
641	sub after($@) {	657	sub after($@) {
642	my ($timeout, @action) = @_;	658	my ($timeout, @action) = @_;
…		…
708		724
709	Erlang makes few guarantees on messages delivery - messages can get lost	725	Erlang makes few guarantees on messages delivery - messages can get lost
710	without any of the processes realising it (i.e. you send messages a, b,	726	without any of the processes realising it (i.e. you send messages a, b,
711	and c, and the other side only receives messages a and c).	727	and c, and the other side only receives messages a and c).
712		728
713	AEMP guarantees correct ordering, and the guarantee that there are no	729	AEMP guarantees correct ordering, and the guarantee that after one message
714	holes in the message sequence.	730	is lost, all following ones sent to the same port are lost as well, until
715		731	monitoring raises an error, so there are no silent "holes" in the message
716	=item * In Erlang, processes can be declared dead and later be found to be	732	sequence.
717	alive.
718
719	In Erlang it can happen that a monitored process is declared dead and
720	linked processes get killed, but later it turns out that the process is
721	still alive - and can receive messages.
722
723	In AEMP, when port monitoring detects a port as dead, then that port will
724	eventually be killed - it cannot happen that a node detects a port as dead
725	and then later sends messages to it, finding it is still alive.
726		733
727	=item * Erlang can send messages to the wrong port, AEMP does not.	734	=item * Erlang can send messages to the wrong port, AEMP does not.
728		735
729	In Erlang it is quite likely that a node that restarts reuses a process ID	736	In Erlang it is quite likely that a node that restarts reuses a process ID
730	known to other nodes for a completely different process, causing messages	737	known to other nodes for a completely different process, causing messages
…		…
734	around in the network will not be sent to an unrelated port.	741	around in the network will not be sent to an unrelated port.
735		742
736	=item * Erlang uses unprotected connections, AEMP uses secure	743	=item * Erlang uses unprotected connections, AEMP uses secure
737	authentication and can use TLS.	744	authentication and can use TLS.
738		745
739	AEMP can use a proven protocol - SSL/TLS - to protect connections and	746	AEMP can use a proven protocol - TLS - to protect connections and
740	securely authenticate nodes.	747	securely authenticate nodes.
741		748
742	=item * The AEMP protocol is optimised for both text-based and binary	749	=item * The AEMP protocol is optimised for both text-based and binary
743	communications.	750	communications.
744		751
745	The AEMP protocol, unlike the Erlang protocol, supports both	752	The AEMP protocol, unlike the Erlang protocol, supports both programming
746	language-independent text-only protocols (good for debugging) and binary,	753	language independent text-only protocols (good for debugging) and binary,
747	language-specific serialisers (e.g. Storable).	754	language-specific serialisers (e.g. Storable). By default, unless TLS is
		755	used, the protocol is actually completely text-based.
748		756
749	It has also been carefully designed to be implementable in other languages	757	It has also been carefully designed to be implementable in other languages
750	with a minimum of work while gracefully degrading fucntionality to make the	758	with a minimum of work while gracefully degrading functionality to make the
751	protocol simple.	759	protocol simple.
752		760
753	=item * AEMP has more flexible monitoring options than Erlang.	761	=item * AEMP has more flexible monitoring options than Erlang.
754		762
755	In Erlang, you can chose to receive I<all> exit signals as messages	763	In Erlang, you can chose to receive I<all> exit signals as messages
…		…
758	Erlang, as one can choose between automatic kill, exit message or callback	766	Erlang, as one can choose between automatic kill, exit message or callback
759	on a per-process basis.	767	on a per-process basis.
760		768
761	=item * Erlang tries to hide remote/local connections, AEMP does not.	769	=item * Erlang tries to hide remote/local connections, AEMP does not.
762		770
763	Monitoring in Erlang is not an indicator of process death/crashes,	771	Monitoring in Erlang is not an indicator of process death/crashes, in the
764	as linking is (except linking is unreliable in Erlang).	772	same way as linking is (except linking is unreliable in Erlang).
765		773
766	In AEMP, you don't "look up" registered port names or send to named ports	774	In AEMP, you don't "look up" registered port names or send to named ports
767	that might or might not be persistent. Instead, you normally spawn a port	775	that might or might not be persistent. Instead, you normally spawn a port
768	on the remote node. The init function monitors the you, and you monitor	776	on the remote node. The init function monitors you, and you monitor the
769	the remote port. Since both monitors are local to the node, they are much	777	remote port. Since both monitors are local to the node, they are much more
770	more reliable.	778	reliable (no need for C<spawn_link>).
771		779
772	This also saves round-trips and avoids sending messages to the wrong port	780	This also saves round-trips and avoids sending messages to the wrong port
773	(hard to do in Erlang).	781	(hard to do in Erlang).
774		782
775	=back	783	=back
776		784
777	=head1 RATIONALE	785	=head1 RATIONALE
778		786
779	=over 4	787	=over 4
780		788
781	=item Why strings for ports and noderefs, why not objects?	789	=item Why strings for port and node IDs, why not objects?
782		790
783	We considered "objects", but found that the actual number of methods	791	We considered "objects", but found that the actual number of methods
784	thatc an be called are very low. Since port IDs and noderefs travel over	792	that can be called are quite low. Since port and node IDs travel over
785	the network frequently, the serialising/deserialising would add lots of	793	the network frequently, the serialising/deserialising would add lots of
786	overhead, as well as having to keep a proxy object.	794	overhead, as well as having to keep a proxy object everywhere.
787		795
788	Strings can easily be printed, easily serialised etc. and need no special	796	Strings can easily be printed, easily serialised etc. and need no special
789	procedures to be "valid".	797	procedures to be "valid".
790		798
791	And a a miniport consists of a single closure stored in a global hash - it	799	And as a result, a miniport consists of a single closure stored in a
792	can't become much cheaper.	800	global hash - it can't become much cheaper.
793		801
794	=item Why favour JSON, why not real serialising format such as Storable?	802	=item Why favour JSON, why not a real serialising format such as Storable?
795		803
796	In fact, any AnyEvent::MP node will happily accept Storable as framing	804	In fact, any AnyEvent::MP node will happily accept Storable as framing
797	format, but currently there is no way to make a node use Storable by	805	format, but currently there is no way to make a node use Storable by
798	default.	806	default (although all nodes will accept it).
799		807
800	The default framing protocol is JSON because a) JSON::XS is many times	808	The default framing protocol is JSON because a) JSON::XS is many times
801	faster for small messages and b) most importantly, after years of	809	faster for small messages and b) most importantly, after years of
802	experience we found that object serialisation is causing more problems	810	experience we found that object serialisation is causing more problems
803	than it gains: Just like function calls, objects simply do not travel	811	than it solves: Just like function calls, objects simply do not travel
804	easily over the network, mostly because they will always be a copy, so you	812	easily over the network, mostly because they will always be a copy, so you
805	always have to re-think your design.	813	always have to re-think your design.
806		814
807	Keeping your messages simple, concentrating on data structures rather than	815	Keeping your messages simple, concentrating on data structures rather than
808	objects, will keep your messages clean, tidy and efficient.	816	objects, will keep your messages clean, tidy and efficient.
809		817
810	=back	818	=back
811		819
812	=head1 SEE ALSO	820	=head1 SEE ALSO
813		821
		822	L<AnyEvent::MP::Intro> - a gentle introduction.
		823
		824	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.
		825
		826	L<AnyEvent::MP::Global> - network maintainance and port groups, to find
		827	your applications.
		828
814	L<AnyEvent>.	829	L<AnyEvent>.
815		830
816	=head1 AUTHOR	831	=head1 AUTHOR
817		832
818	Marc Lehmann <schmorp@schmorp.de>	833	Marc Lehmann <schmorp@schmorp.de>

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.65 by root, Fri Aug 28 01:00:34 2009 UTC vs. Revision 1.70 by root, Sun Aug 30 19:49:47 2009 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.65 by root, Fri Aug 28 01:00:34 2009 UTC vs.
Revision 1.70 by root, Sun Aug 30 19:49:47 2009 UTC