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

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.78 by root, Thu Sep 3 20:16:36 2009 UTC vs.
Revision 1.85 by root, Tue Sep 8 01:54:13 2009 UTC

…		…
41		41
42	bin/aemp - stable.	42	bin/aemp - stable.
43	AnyEvent::MP - stable API, should work.	43	AnyEvent::MP - stable API, should work.
44	AnyEvent::MP::Intro - explains most concepts.	44	AnyEvent::MP::Intro - explains most concepts.
45	AnyEvent::MP::Kernel - mostly stable.	45	AnyEvent::MP::Kernel - mostly stable.
46	AnyEvent::MP::Global - stable API, protocol not yet final.	46	AnyEvent::MP::Global - stable but incomplete, protocol not yet final.
47		47
48	stay tuned.	48	stay tuned.
49		49
50	=head1 DESCRIPTION	50	=head1 DESCRIPTION
51		51
52	This module (-family) implements a simple message passing framework.	52	This module (-family) implements a simple message passing framework.
53		53
…		…
61		61
62	=over 4	62	=over 4
63		63
64	=item port	64	=item port
65		65
66	A port is something you can send messages to (with the C<snd> function).	66	Not to be confused with a TCP port, a "port" is something you can send
		67	messages to (with the C<snd> function).
67		68
68	Ports allow you to register C<rcv> handlers that can match all or just	69	Ports allow you to register C<rcv> handlers that can match all or just
69	some messages. Messages send to ports will not be queued, regardless of	70	some messages. Messages send to ports will not be queued, regardless of
70	anything was listening for them or not.	71	anything was listening for them or not.
71		72
…		…
82		83
83	Nodes are either public (have one or more listening ports) or private	84	Nodes are either public (have one or more listening ports) or private
84	(no listening ports). Private nodes cannot talk to other private nodes	85	(no listening ports). Private nodes cannot talk to other private nodes
85	currently.	86	currently.
86		87
87	=item node ID - C<[a-za-Z0-9_\-.:]+>	88	=item node ID - C<[A-Z_][a-zA-Z0-9_\-.:]*>
88		89
89	A node ID is a string that uniquely identifies the node within a	90	A node ID is a string that uniquely identifies the node within a
90	network. Depending on the configuration used, node IDs can look like a	91	network. Depending on the configuration used, node IDs can look like a
91	hostname, a hostname and a port, or a random string. AnyEvent::MP itself	92	hostname, a hostname and a port, or a random string. AnyEvent::MP itself
92	doesn't interpret node IDs in any way.	93	doesn't interpret node IDs in any way.
…		…
96	Nodes can only talk to each other by creating some kind of connection to	97	Nodes can only talk to each other by creating some kind of connection to
97	each other. To do this, nodes should listen on one or more local transport	98	each other. To do this, nodes should listen on one or more local transport
98	endpoints - binds. Currently, only standard C<ip:port> specifications can	99	endpoints - binds. Currently, only standard C<ip:port> specifications can
99	be used, which specify TCP ports to listen on.	100	be used, which specify TCP ports to listen on.
100		101
101	=item seeds - C<host:port>	102	=item seed nodes
102		103
103	When a node starts, it knows nothing about the network. To teach the node	104	When a node starts, it knows nothing about the network. To teach the node
104	about the network it first has to contact some other node within the	105	about the network it first has to contact some other node within the
105	network. This node is called a seed.	106	network. This node is called a seed.
106		107
107	Seeds are transport endpoint(s) of as many nodes as one wants. Those nodes	108	Apart from the fact that other nodes know them as seed nodes and they have
		109	to have fixed listening addresses, seed nodes are perfectly normal nodes -
		110	any node can function as a seed node for others.
		111
		112	In addition to discovering the network, seed nodes are also used to
		113	maintain the network and to connect nodes that otherwise would have
		114	trouble connecting. They form the backbone of the AnyEvent::MP network.
		115
108	are expected to be long-running, and at least one of those should always	116	Seed nodes are expected to be long-running, and at least one seed node
109	be available. When nodes run out of connections (e.g. due to a network	117	should always be available. They should also be relatively responsive - a
110	error), they try to re-establish connections to some seednodes again to	118	seed node that blocks for long periods will slow down everybody else.
111	join the network.
112		119
113	Apart from being sued for seeding, seednodes are not special in any way -	120	=item seeds - C<host:port>
114	every public node can be a seednode.	121
		122	Seeds are transport endpoint(s) (usually a hostname/IP address and a
		123	TCP port) of nodes thta should be used as seed nodes.
		124
		125	The nodes listening on those endpoints are expected to be long-running,
		126	and at least one of those should always be available. When nodes run out
		127	of connections (e.g. due to a network error), they try to re-establish
		128	connections to some seednodes again to join the network.
115		129
116	=back	130	=back
117		131
118	=head1 VARIABLES/FUNCTIONS	132	=head1 VARIABLES/FUNCTIONS
119		133
…		…
474		488
475	Monitor the given port and do something when the port is killed or	489	Monitor the given port and do something when the port is killed or
476	messages to it were lost, and optionally return a guard that can be used	490	messages to it were lost, and optionally return a guard that can be used
477	to stop monitoring again.	491	to stop monitoring again.
478		492
		493	In the first form (callback), the callback is simply called with any
		494	number of C<@reason> elements (no @reason means that the port was deleted
		495	"normally"). Note also that I<< the callback B<must> never die >>, so use
		496	C<eval> if unsure.
		497
		498	In the second form (another port given), the other port (C<$rcvport>)
		499	will be C<kil>'ed with C<@reason>, if a @reason was specified, i.e. on
		500	"normal" kils nothing happens, while under all other conditions, the other
		501	port is killed with the same reason.
		502
		503	The third form (kill self) is the same as the second form, except that
		504	C<$rvport> defaults to C<$SELF>.
		505
		506	In the last form (message), a message of the form C<@msg, @reason> will be
		507	C<snd>.
		508
		509	Monitoring-actions are one-shot: once messages are lost (and a monitoring
		510	alert was raised), they are removed and will not trigger again.
		511
		512	As a rule of thumb, monitoring requests should always monitor a port from
		513	a local port (or callback). The reason is that kill messages might get
		514	lost, just like any other message. Another less obvious reason is that
		515	even monitoring requests can get lost (for example, when the connection
		516	to the other node goes down permanently). When monitoring a port locally
		517	these problems do not exist.
		518
479	C<mon> effectively guarantees that, in the absence of hardware failures,	519	C<mon> effectively guarantees that, in the absence of hardware failures,
480	after starting the monitor, either all messages sent to the port will	520	after starting the monitor, either all messages sent to the port will
481	arrive, or the monitoring action will be invoked after possible message	521	arrive, or the monitoring action will be invoked after possible message
482	loss has been detected. No messages will be lost "in between" (after	522	loss has been detected. No messages will be lost "in between" (after
483	the first lost message no further messages will be received by the	523	the first lost message no further messages will be received by the
484	port). After the monitoring action was invoked, further messages might get	524	port). After the monitoring action was invoked, further messages might get
485	delivered again.	525	delivered again.
486		526
487	Note that monitoring-actions are one-shot: once messages are lost (and a	527	Inter-host-connection timeouts and monitoring depend on the transport
488	monitoring alert was raised), they are removed and will not trigger again.	528	used. The only transport currently implemented is TCP, and AnyEvent::MP
		529	relies on TCP to detect node-downs (this can take 10-15 minutes on a
		530	non-idle connection, and usually around two hours for idle conenctions).
489		531
490	In the first form (callback), the callback is simply called with any	532	This means that monitoring is good for program errors and cleaning up
491	number of C<@reason> elements (no @reason means that the port was deleted	533	stuff eventually, but they are no replacement for a timeout when you need
492	"normally"). Note also that I<< the callback B<must> never die >>, so use	534	to ensure some maximum latency.
493	C<eval> if unsure.
494
495	In the second form (another port given), the other port (C<$rcvport>)
496	will be C<kil>'ed with C<@reason>, if a @reason was specified, i.e. on
497	"normal" kils nothing happens, while under all other conditions, the other
498	port is killed with the same reason.
499
500	The third form (kill self) is the same as the second form, except that
501	C<$rvport> defaults to C<$SELF>.
502
503	In the last form (message), a message of the form C<@msg, @reason> will be
504	C<snd>.
505
506	As a rule of thumb, monitoring requests should always monitor a port from
507	a local port (or callback). The reason is that kill messages might get
508	lost, just like any other message. Another less obvious reason is that
509	even monitoring requests can get lost (for example, when the connection
510	to the other node goes down permanently). When monitoring a port locally
511	these problems do not exist.
512		535
513	Example: call a given callback when C<$port> is killed.	536	Example: call a given callback when C<$port> is killed.
514		537
515	mon $port, sub { warn "port died because of <@_>\n" };	538	mon $port, sub { warn "port died because of <@_>\n" };
516		539
…		…
611	the package, then the package above the package and so on (e.g.	634	the package, then the package above the package and so on (e.g.
612	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function	635	C<MyApp::Chat::Server>, C<MyApp::Chat>, C<MyApp>) until the function
613	exists or it runs out of package names.	636	exists or it runs out of package names.
614		637
615	The init function is then called with the newly-created port as context	638	The init function is then called with the newly-created port as context
616	object (C<$SELF>) and the C<@initdata> values as arguments.	639	object (C<$SELF>) and the C<@initdata> values as arguments. It I<must>
		640	call one of the C<rcv> functions to set callbacks on C<$SELF>, otherwise
		641	the port might not get created.
617		642
618	A common idiom is to pass a local port, immediately monitor the spawned	643	A common idiom is to pass a local port, immediately monitor the spawned
619	port, and in the remote init function, immediately monitor the passed	644	port, and in the remote init function, immediately monitor the passed
620	local port. This two-way monitoring ensures that both ports get cleaned up	645	local port. This two-way monitoring ensures that both ports get cleaned up
621	when there is a problem.	646	when there is a problem.
622		647
		648	C<spawn> guarantees that the C<$initfunc> has no visible effects on the
		649	caller before C<spawn> returns (by delaying invocation when spawn is
		650	called for the local node).
		651
623	Example: spawn a chat server port on C<$othernode>.	652	Example: spawn a chat server port on C<$othernode>.
624		653
625	# this node, executed from within a port context:	654	# this node, executed from within a port context:
626	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;	655	my $server = spawn $othernode, "MyApp::Chat::Server::connect", $SELF;
627	mon $server;	656	mon $server;
…		…
641		670
642	sub _spawn {	671	sub _spawn {
643	my $port = shift;	672	my $port = shift;
644	my $init = shift;	673	my $init = shift;
645		674
		675	# rcv will create the actual port
646	local $SELF = "$NODE#$port";	676	local $SELF = "$NODE#$port";
647	eval {	677	eval {
648	&{ load_func $init }	678	&{ load_func $init }
649	};	679	};
650	_self_die if $@;	680	_self_die if $@;
…		…
846	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.	876	L<AnyEvent::MP::Kernel> - more, lower-level, stuff.
847		877
848	L<AnyEvent::MP::Global> - network maintainance and port groups, to find	878	L<AnyEvent::MP::Global> - network maintainance and port groups, to find
849	your applications.	879	your applications.
850		880
		881	L<AnyEvent::MP::LogCatcher> - simple service to display log messages from
		882	all nodes.
		883
851	L<AnyEvent>.	884	L<AnyEvent>.
852		885
853	=head1 AUTHOR	886	=head1 AUTHOR
854		887
855	Marc Lehmann <schmorp@schmorp.de>	888	Marc Lehmann <schmorp@schmorp.de>

Diff Legend

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

Comparing AnyEvent-MP/MP.pm (file contents): Revision 1.78 by root, Thu Sep 3 20:16:36 2009 UTC vs. Revision 1.85 by root, Tue Sep 8 01:54:13 2009 UTC

Diff Legend

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.78 by root, Thu Sep 3 20:16:36 2009 UTC vs.
Revision 1.85 by root, Tue Sep 8 01:54:13 2009 UTC