[ViewVC] Diff of: cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.47 by root, Mon Apr 14 16:09:33 2008 UTC vs.
Revision 1.106 by root, Thu May 1 13:45:22 2008 UTC

…		…
1	=head1 NAME	1	=head1 NAME
2		2
3	AnyEvent - provide framework for multiple event loops	3	AnyEvent - provide framework for multiple event loops
4		4
5	Event, Coro, Glib, Tk, Perl - various supported event loops	5	EV, Event, Coro::EV, Coro::Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops
6		6
7	=head1 SYNOPSIS	7	=head1 SYNOPSIS
8		8
9	use AnyEvent;	9	use AnyEvent;
10		10
14		14
15	my $w = AnyEvent->timer (after => $seconds, cb => sub {	15	my $w = AnyEvent->timer (after => $seconds, cb => sub {
16	...	16	...
17	});	17	});
18		18
19	my $w = AnyEvent->condvar; # stores wether a condition was flagged	19	my $w = AnyEvent->condvar; # stores whether a condition was flagged
20	$w->wait; # enters "main loop" till $condvar gets ->broadcast	20	$w->wait; # enters "main loop" till $condvar gets ->send
21	$w->broadcast; # wake up current and all future wait's	21	$w->send; # wake up current and all future wait's
22		22
23	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)	23	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
24		24
25	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen	25	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
26	nowadays. So what is different about AnyEvent?	26	nowadays. So what is different about AnyEvent?
…		…
29	policy> and AnyEvent is I<small and efficient>.	29	policy> and AnyEvent is I<small and efficient>.
30		30
31	First and foremost, I<AnyEvent is not an event model> itself, it only	31	First and foremost, I<AnyEvent is not an event model> itself, it only
32	interfaces to whatever event model the main program happens to use in a	32	interfaces to whatever event model the main program happens to use in a
33	pragmatic way. For event models and certain classes of immortals alike,	33	pragmatic way. For event models and certain classes of immortals alike,
34	the statement "there can only be one" is a bitter reality, and AnyEvent	34	the statement "there can only be one" is a bitter reality: In general,
35	helps hiding the differences.	35	only one event loop can be active at the same time in a process. AnyEvent
		36	helps hiding the differences between those event loops.
36		37
37	The goal of AnyEvent is to offer module authors the ability to do event	38	The goal of AnyEvent is to offer module authors the ability to do event
38	programming (waiting for I/O or timer events) without subscribing to a	39	programming (waiting for I/O or timer events) without subscribing to a
39	religion, a way of living, and most importantly: without forcing your	40	religion, a way of living, and most importantly: without forcing your
40	module users into the same thing by forcing them to use the same event	41	module users into the same thing by forcing them to use the same event
41	model you use.	42	model you use.
42		43
43	For modules like POE or IO::Async (which is actually doing all I/O	44	For modules like POE or IO::Async (which is a total misnomer as it is
44	I<synchronously>...), using them in your module is like joining a	45	actually doing all I/O I<synchronously>...), using them in your module is
45	cult: After you joined, you are dependent on them and you cannot use	46	like joining a cult: After you joined, you are dependent on them and you
46	anything else, as it is simply incompatible to everything that isn't	47	cannot use anything else, as it is simply incompatible to everything that
47	itself.	48	isn't itself. What's worse, all the potential users of your module are
		49	I<also> forced to use the same event loop you use.
48		50
49	AnyEvent + POE works fine. AnyEvent + Glib works fine. AnyEvent + Tk	51	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
50	works fine etc. etc. but none of these work together with the rest: POE	52	fine. AnyEvent + Tk works fine etc. etc. but none of these work together
51	+ IO::Async? no go. Tk + Event? no go. If your module uses one of	53	with the rest: POE + IO::Async? no go. Tk + Event? no go. Again: if
52	those, every user of your module has to use it, too. If your module	54	your module uses one of those, every user of your module has to use it,
53	uses AnyEvent, it works transparently with all event models it supports	55	too. But if your module uses AnyEvent, it works transparently with all
54	(including stuff like POE and IO::Async).	56	event models it supports (including stuff like POE and IO::Async, as long
		57	as those use one of the supported event loops. It is trivial to add new
		58	event loops to AnyEvent, too, so it is future-proof).
55		59
56	In addition of being free of having to use I<the one and only true event	60	In addition to being free of having to use I<the one and only true event
57	model>, AnyEvent also is free of bloat and policy: with POE or similar	61	model>, AnyEvent also is free of bloat and policy: with POE or similar
58	modules, you get an enourmous amount of code and strict rules you have	62	modules, you get an enourmous amount of code and strict rules you have to
59	to follow. AnyEvent, on the other hand, is lean and to the point by only	63	follow. AnyEvent, on the other hand, is lean and up to the point, by only
60	offering the functionality that is useful, in as thin as a wrapper as	64	offering the functionality that is necessary, in as thin as a wrapper as
61	technically possible.	65	technically possible.
62		66
63	Of course, if you want lots of policy (this can arguably be somewhat	67	Of course, if you want lots of policy (this can arguably be somewhat
64	useful) and you want to force your users to use the one and only event	68	useful) and you want to force your users to use the one and only event
65	model, you should I<not> use this module.	69	model, you should I<not> use this module.
66
67		70
68	=head1 DESCRIPTION	71	=head1 DESCRIPTION
69		72
70	L<AnyEvent> provides an identical interface to multiple event loops. This	73	L<AnyEvent> provides an identical interface to multiple event loops. This
71	allows module authors to utilise an event loop without forcing module	74	allows module authors to utilise an event loop without forcing module
72	users to use the same event loop (as only a single event loop can coexist	75	users to use the same event loop (as only a single event loop can coexist
73	peacefully at any one time).	76	peacefully at any one time).
74		77
75	The interface itself is vaguely similar but not identical to the Event	78	The interface itself is vaguely similar, but not identical to the L<Event>
76	module.	79	module.
77		80
78	On the first call of any method, the module tries to detect the currently	81	During the first call of any watcher-creation method, the module tries
79	loaded event loop by probing wether any of the following modules is	82	to detect the currently loaded event loop by probing whether one of the
80	loaded: L<Coro::Event>, L<Event>, L<Glib>, L<Tk>. The first one found is	83	following modules is already loaded: L<Coro::EV>, L<Coro::Event>, L<EV>,
81	used. If none is found, the module tries to load these modules in the	84	L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>,
82	order given. The first one that could be successfully loaded will be	85	L<POE>. The first one found is used. If none are found, the module tries
83	used. If still none could be found, AnyEvent will fall back to a pure-perl	86	to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl
84	event loop, which is also not very efficient.	87	adaptor should always succeed) in the order given. The first one that can
		88	be successfully loaded will be used. If, after this, still none could be
		89	found, AnyEvent will fall back to a pure-perl event loop, which is not
		90	very efficient, but should work everywhere.
85		91
86	Because AnyEvent first checks for modules that are already loaded, loading	92	Because AnyEvent first checks for modules that are already loaded, loading
87	an Event model explicitly before first using AnyEvent will likely make	93	an event model explicitly before first using AnyEvent will likely make
88	that model the default. For example:	94	that model the default. For example:
89		95
90	use Tk;	96	use Tk;
91	use AnyEvent;	97	use AnyEvent;
92		98
93	# .. AnyEvent will likely default to Tk	99	# .. AnyEvent will likely default to Tk
		100
		101	The I<likely> means that, if any module loads another event model and
		102	starts using it, all bets are off. Maybe you should tell their authors to
		103	use AnyEvent so their modules work together with others seamlessly...
94		104
95	The pure-perl implementation of AnyEvent is called	105	The pure-perl implementation of AnyEvent is called
96	C<AnyEvent::Impl::Perl>. Like other event modules you can load it	106	C<AnyEvent::Impl::Perl>. Like other event modules you can load it
97	explicitly.	107	explicitly.
98		108
…		…
101	AnyEvent has the central concept of a I<watcher>, which is an object that	111	AnyEvent has the central concept of a I<watcher>, which is an object that
102	stores relevant data for each kind of event you are waiting for, such as	112	stores relevant data for each kind of event you are waiting for, such as
103	the callback to call, the filehandle to watch, etc.	113	the callback to call, the filehandle to watch, etc.
104		114
105	These watchers are normal Perl objects with normal Perl lifetime. After	115	These watchers are normal Perl objects with normal Perl lifetime. After
106	creating a watcher it will immediately "watch" for events and invoke	116	creating a watcher it will immediately "watch" for events and invoke the
		117	callback when the event occurs (of course, only when the event model
		118	is in control).
		119
107	the callback. To disable the watcher you have to destroy it (e.g. by	120	To disable the watcher you have to destroy it (e.g. by setting the
108	setting the variable that stores it to C<undef> or otherwise deleting all	121	variable you store it in to C<undef> or otherwise deleting all references
109	references to it).	122	to it).
110		123
111	All watchers are created by calling a method on the C<AnyEvent> class.	124	All watchers are created by calling a method on the C<AnyEvent> class.
112		125
		126	Many watchers either are used with "recursion" (repeating timers for
		127	example), or need to refer to their watcher object in other ways.
		128
		129	An any way to achieve that is this pattern:
		130
		131	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
		132	# you can use $w here, for example to undef it
		133	undef $w;
		134	});
		135
		136	Note that C<my $w; $w => combination. This is necessary because in Perl,
		137	my variables are only visible after the statement in which they are
		138	declared.
		139
113	=head2 IO WATCHERS	140	=head2 I/O WATCHERS
114		141
115	You can create I/O watcher by calling the C<< AnyEvent->io >> method with	142	You can create an I/O watcher by calling the C<< AnyEvent->io >> method
116	the following mandatory arguments:	143	with the following mandatory key-value pairs as arguments:
117		144
118	C<fh> the Perl I<filehandle> (not filedescriptor) to watch for	145	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch
119	events. C<poll> must be a string that is either C<r> or C<w>, that creates	146	for events. C<poll> must be a string that is either C<r> or C<w>,
120	a watcher waiting for "r"eadable or "w"ritable events. C<cb> the callback	147	which creates a watcher waiting for "r"eadable or "w"ritable events,
121	to invoke everytime the filehandle becomes ready.	148	respectively. C<cb> is the callback to invoke each time the file handle
		149	becomes ready.
122		150
123	Only one io watcher per C<fh> and C<poll> combination is allowed (i.e. on	151	Although the callback might get passed parameters, their value and
124	a socket you can have one r + one w, not any more (limitation comes from	152	presence is undefined and you cannot rely on them. Portable AnyEvent
125	Tk - if you are sure you are not using Tk this limitation is gone).	153	callbacks cannot use arguments passed to I/O watcher callbacks.
126		154
127	Filehandles will be kept alive, so as long as the watcher exists, the	155	The I/O watcher might use the underlying file descriptor or a copy of it.
128	filehandle exists, too.	156	You must not close a file handle as long as any watcher is active on the
		157	underlying file descriptor.
		158
		159	Some event loops issue spurious readyness notifications, so you should
		160	always use non-blocking calls when reading/writing from/to your file
		161	handles.
129		162
130	Example:	163	Example:
131		164
132	# wait for readability of STDIN, then read a line and disable the watcher	165	# wait for readability of STDIN, then read a line and disable the watcher
133	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {	166	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
…		…
139	=head2 TIME WATCHERS	172	=head2 TIME WATCHERS
140		173
141	You can create a time watcher by calling the C<< AnyEvent->timer >>	174	You can create a time watcher by calling the C<< AnyEvent->timer >>
142	method with the following mandatory arguments:	175	method with the following mandatory arguments:
143		176
144	C<after> after how many seconds (fractions are supported) should the timer	177	C<after> specifies after how many seconds (fractional values are
145	activate. C<cb> the callback to invoke.	178	supported) the callback should be invoked. C<cb> is the callback to invoke
		179	in that case.
		180
		181	Although the callback might get passed parameters, their value and
		182	presence is undefined and you cannot rely on them. Portable AnyEvent
		183	callbacks cannot use arguments passed to time watcher callbacks.
146		184
147	The timer callback will be invoked at most once: if you want a repeating	185	The timer callback will be invoked at most once: if you want a repeating
148	timer you have to create a new watcher (this is a limitation by both Tk	186	timer you have to create a new watcher (this is a limitation by both Tk
149	and Glib).	187	and Glib).
150		188
…		…
156	});	194	});
157		195
158	# to cancel the timer:	196	# to cancel the timer:
159	undef $w;	197	undef $w;
160		198
		199	Example 2:
		200
		201	# fire an event after 0.5 seconds, then roughly every second
		202	my $w;
		203
		204	my $cb = sub {
		205	# cancel the old timer while creating a new one
		206	$w = AnyEvent->timer (after => 1, cb => $cb);
		207	};
		208
		209	# start the "loop" by creating the first watcher
		210	$w = AnyEvent->timer (after => 0.5, cb => $cb);
		211
		212	=head3 TIMING ISSUES
		213
		214	There are two ways to handle timers: based on real time (relative, "fire
		215	in 10 seconds") and based on wallclock time (absolute, "fire at 12
		216	o'clock").
		217
		218	While most event loops expect timers to specified in a relative way, they
		219	use absolute time internally. This makes a difference when your clock
		220	"jumps", for example, when ntp decides to set your clock backwards from
		221	the wrong date of 2014-01-01 to 2008-01-01, a watcher that is supposed to
		222	fire "after" a second might actually take six years to finally fire.
		223
		224	AnyEvent cannot compensate for this. The only event loop that is conscious
		225	about these issues is L<EV>, which offers both relative (ev_timer, based
		226	on true relative time) and absolute (ev_periodic, based on wallclock time)
		227	timers.
		228
		229	AnyEvent always prefers relative timers, if available, matching the
		230	AnyEvent API.
		231
		232	=head2 SIGNAL WATCHERS
		233
		234	You can watch for signals using a signal watcher, C<signal> is the signal
		235	I<name> without any C<SIG> prefix, C<cb> is the Perl callback to
		236	be invoked whenever a signal occurs.
		237
		238	Although the callback might get passed parameters, their value and
		239	presence is undefined and you cannot rely on them. Portable AnyEvent
		240	callbacks cannot use arguments passed to signal watcher callbacks.
		241
		242	Multiple signal occurances can be clumped together into one callback
		243	invocation, and callback invocation will be synchronous. synchronous means
		244	that it might take a while until the signal gets handled by the process,
		245	but it is guarenteed not to interrupt any other callbacks.
		246
		247	The main advantage of using these watchers is that you can share a signal
		248	between multiple watchers.
		249
		250	This watcher might use C<%SIG>, so programs overwriting those signals
		251	directly will likely not work correctly.
		252
		253	Example: exit on SIGINT
		254
		255	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
		256
		257	=head2 CHILD PROCESS WATCHERS
		258
		259	You can also watch on a child process exit and catch its exit status.
		260
		261	The child process is specified by the C<pid> argument (if set to C<0>, it
		262	watches for any child process exit). The watcher will trigger as often
		263	as status change for the child are received. This works by installing a
		264	signal handler for C<SIGCHLD>. The callback will be called with the pid
		265	and exit status (as returned by waitpid), so unlike other watcher types,
		266	you I<can> rely on child watcher callback arguments.
		267
		268	There is a slight catch to child watchers, however: you usually start them
		269	I<after> the child process was created, and this means the process could
		270	have exited already (and no SIGCHLD will be sent anymore).
		271
		272	Not all event models handle this correctly (POE doesn't), but even for
		273	event models that I<do> handle this correctly, they usually need to be
		274	loaded before the process exits (i.e. before you fork in the first place).
		275
		276	This means you cannot create a child watcher as the very first thing in an
		277	AnyEvent program, you I<have> to create at least one watcher before you
		278	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).
		279
		280	Example: fork a process and wait for it
		281
		282	my $done = AnyEvent->condvar;
		283
		284	AnyEvent::detect; # force event module to be initialised
		285
		286	my $pid = fork or exit 5;
		287
		288	my $w = AnyEvent->child (
		289	pid => $pid,
		290	cb => sub {
		291	my ($pid, $status) = @_;
		292	warn "pid $pid exited with status $status";
		293	$done->send;
		294	},
		295	);
		296
		297	# do something else, then wait for process exit
		298	$done->wait;
		299
161	=head2 CONDITION WATCHERS	300	=head2 CONDITION VARIABLES
162		301
		302	If you are familiar with some event loops you will know that all of them
		303	require you to run some blocking "loop", "run" or similar function that
		304	will actively watch for new events and call your callbacks.
		305
		306	AnyEvent is different, it expects somebody else to run the event loop and
		307	will only block when necessary (usually when told by the user).
		308
		309	The instrument to do that is called a "condition variable", so called
		310	because they represent a condition that must become true.
		311
163	Condition watchers can be created by calling the C<< AnyEvent->condvar >>	312	Condition variables can be created by calling the C<< AnyEvent->condvar
164	method without any arguments.	313	>> method, usually without arguments. The only argument pair allowed is
		314	C<cb>, which specifies a callback to be called when the condition variable
		315	becomes true.
165		316
166	A condition watcher watches for a condition - precisely that the C<<	317	After creation, the conditon variable is "false" until it becomes "true"
167	->broadcast >> method has been called.	318	by calling the C<send> method.
168		319
		320	Condition variables are similar to callbacks, except that you can
		321	optionally wait for them. They can also be called merge points - points
		322	in time where multiple outstandign events have been processed. And yet
		323	another way to call them is transations - each condition variable can be
		324	used to represent a transaction, which finishes at some point and delivers
		325	a result.
		326
		327	Condition variables are very useful to signal that something has finished,
		328	for example, if you write a module that does asynchronous http requests,
		329	then a condition variable would be the ideal candidate to signal the
		330	availability of results. The user can either act when the callback is
		331	called or can synchronously C<< ->wait >> for the results.
		332
		333	You can also use them to simulate traditional event loops - for example,
		334	you can block your main program until an event occurs - for example, you
		335	could C<< ->wait >> in your main program until the user clicks the Quit
		336	button of your app, which would C<< ->send >> the "quit" event.
		337
169	Note that condition watchers recurse into the event loop - if you have	338	Note that condition variables recurse into the event loop - if you have
170	two watchers that call C<< ->wait >> in a round-robbin fashion, you	339	two pieces of code that call C<< ->wait >> in a round-robbin fashion, you
171	lose. Therefore, condition watchers are good to export to your caller, but	340	lose. Therefore, condition variables are good to export to your caller, but
172	you should avoid making a blocking wait, at least in callbacks, as this	341	you should avoid making a blocking wait yourself, at least in callbacks,
173	usually asks for trouble.	342	as this asks for trouble.
174		343
175	The watcher has only two methods:	344	Condition variables are represented by hash refs in perl, and the keys
		345	used by AnyEvent itself are all named C<_ae_XXX> to make subclassing
		346	easy (it is often useful to build your own transaction class on top of
		347	AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call
		348	it's C<new> method in your own C<new> method.
		349
		350	There are two "sides" to a condition variable - the "producer side" which
		351	eventually calls C<< -> send >>, and the "consumer side", which waits
		352	for the send to occur.
		353
		354	Example:
		355
		356	# wait till the result is ready
		357	my $result_ready = AnyEvent->condvar;
		358
		359	# do something such as adding a timer
		360	# or socket watcher the calls $result_ready->send
		361	# when the "result" is ready.
		362	# in this case, we simply use a timer:
		363	my $w = AnyEvent->timer (
		364	after => 1,
		365	cb => sub { $result_ready->send },
		366	);
		367
		368	# this "blocks" (while handling events) till the callback
		369	# calls send
		370	$result_ready->wait;
		371
		372	=head3 METHODS FOR PRODUCERS
		373
		374	These methods should only be used by the producing side, i.e. the
		375	code/module that eventually sends the signal. Note that it is also
		376	the producer side which creates the condvar in most cases, but it isn't
		377	uncommon for the consumer to create it as well.
176		378
177	=over 4	379	=over 4
178		380
		381	=item $cv->send (...)
		382
		383	Flag the condition as ready - a running C<< ->wait >> and all further
		384	calls to C<wait> will (eventually) return after this method has been
		385	called. If nobody is waiting the send will be remembered.
		386
		387	If a callback has been set on the condition variable, it is called
		388	immediately from within send.
		389
		390	Any arguments passed to the C<send> call will be returned by all
		391	future C<< ->wait >> calls.
		392
		393	=item $cv->croak ($error)
		394
		395	Similar to send, but causes all call's wait C<< ->wait >> to invoke
		396	C<Carp::croak> with the given error message/object/scalar.
		397
		398	This can be used to signal any errors to the condition variable
		399	user/consumer.
		400
		401	=item $cv->begin ([group callback])
		402
		403	=item $cv->end
		404
		405	These two methods can be used to combine many transactions/events into
		406	one. For example, a function that pings many hosts in parallel might want
		407	to use a condition variable for the whole process.
		408
		409	Every call to C<< ->begin >> will increment a counter, and every call to
		410	C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end
		411	>>, the (last) callback passed to C<begin> will be executed. That callback
		412	is I<supposed> to call C<< ->send >>, but that is not required. If no
		413	callback was set, C<send> will be called without any arguments.
		414
		415	Let's clarify this with the ping example:
		416
		417	my $cv = AnyEvent->condvar;
		418
		419	my %result;
		420	$cv->begin (sub { $cv->send (\%result) });
		421
		422	for my $host (@list_of_hosts) {
		423	$cv->begin;
		424	ping_host_then_call_callback $host, sub {
		425	$result{$host} = ...;
		426	$cv->end;
		427	};
		428	}
		429
		430	$cv->end;
		431
		432	This code fragment supposedly pings a number of hosts and calls
		433	C<send> after results for all then have have been gathered - in any
		434	order. To achieve this, the code issues a call to C<begin> when it starts
		435	each ping request and calls C<end> when it has received some result for
		436	it. Since C<begin> and C<end> only maintain a counter, the order in which
		437	results arrive is not relevant.
		438
		439	There is an additional bracketing call to C<begin> and C<end> outside the
		440	loop, which serves two important purposes: first, it sets the callback
		441	to be called once the counter reaches C<0>, and second, it ensures that
		442	C<send> is called even when C<no> hosts are being pinged (the loop
		443	doesn't execute once).
		444
		445	This is the general pattern when you "fan out" into multiple subrequests:
		446	use an outer C<begin>/C<end> pair to set the callback and ensure C<end>
		447	is called at least once, and then, for each subrequest you start, call
		448	C<begin> and for eahc subrequest you finish, call C<end>.
		449
		450	=back
		451
		452	=head3 METHODS FOR CONSUMERS
		453
		454	These methods should only be used by the consuming side, i.e. the
		455	code awaits the condition.
		456
		457	=over 4
		458
179	=item $cv->wait	459	=item $cv->wait
180		460
181	Wait (blocking if necessary) until the C<< ->broadcast >> method has been	461	Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak
182	called on c<$cv>, while servicing other watchers normally.	462	>> methods have been called on c<$cv>, while servicing other watchers
		463	normally.
183		464
184	You can only wait once on a condition - additional calls will return	465	You can only wait once on a condition - additional calls are valid but
185	immediately.	466	will return immediately.
		467
		468	If an error condition has been set by calling C<< ->croak >>, then this
		469	function will call C<croak>.
		470
		471	In list context, all parameters passed to C<send> will be returned,
		472	in scalar context only the first one will be returned.
186		473
187	Not all event models support a blocking wait - some die in that case	474	Not all event models support a blocking wait - some die in that case
188	(programs might want to do that so they stay interactive), so I<if you	475	(programs might want to do that to stay interactive), so I<if you are
189	are using this from a module, never require a blocking wait>, but let the	476	using this from a module, never require a blocking wait>, but let the
190	caller decide wether the call will block or not (for example, by coupling	477	caller decide whether the call will block or not (for example, by coupling
191	condition variables with some kind of request results and supporting	478	condition variables with some kind of request results and supporting
192	callbacks so the caller knows that getting the result will not block,	479	callbacks so the caller knows that getting the result will not block,
193	while still suppporting blocking waits if the caller so desires).	480	while still suppporting blocking waits if the caller so desires).
194		481
195	Another reason I<never> to C<< ->wait >> in a module is that you cannot	482	Another reason I<never> to C<< ->wait >> in a module is that you cannot
196	sensibly have two C<< ->wait >>'s in parallel, as that would require	483	sensibly have two C<< ->wait >>'s in parallel, as that would require
197	multiple interpreters or coroutines/threads, none of which C<AnyEvent>	484	multiple interpreters or coroutines/threads, none of which C<AnyEvent>
198	can supply (the coroutine-aware backends C<Coro::EV> and C<Coro::Event>	485	can supply (the coroutine-aware backends L<AnyEvent::Impl::CoroEV> and
199	explicitly support concurrent C<< ->wait >>'s from different coroutines,	486	L<AnyEvent::Impl::CoroEvent> explicitly support concurrent C<< ->wait >>'s
200	however).	487	from different coroutines, however).
201		488
202	=item $cv->broadcast	489	You can ensure that C<< -wait >> never blocks by setting a callback and
		490	only calling C<< ->wait >> from within that callback (or at a later
		491	time). This will work even when the event loop does not support blocking
		492	waits otherwise.
203		493
204	Flag the condition as ready - a running C<< ->wait >> and all further	494	=item $bool = $cv->ready
205	calls to C<wait> will return after this method has been called. If nobody
206	is waiting the broadcast will be remembered..
207		495
208	Example:	496	Returns true when the condition is "true", i.e. whether C<send> or
		497	C<croak> have been called.
209		498
210	# wait till the result is ready	499	=item $cb = $cv->cb ([new callback])
211	my $result_ready = AnyEvent->condvar;
212		500
213	# do something such as adding a timer	501	This is a mutator function that returns the callback set and optionally
214	# or socket watcher the calls $result_ready->broadcast	502	replaces it before doing so.
215	# when the "result" is ready.
216		503
217	$result_ready->wait;	504	The callback will be called when the condition becomes "true", i.e. when
		505	C<send> or C<croak> are called. Calling C<wait> inside the callback
		506	or at any later time is guaranteed not to block.
218		507
219	=back	508	=back
220		509
221	=head2 SIGNAL WATCHERS	510	=head1 GLOBAL VARIABLES AND FUNCTIONS
222
223	You can listen for signals using a signal watcher, C<signal> is the signal
224	I<name> without any C<SIG> prefix. Multiple signals events can be clumped
225	together into one callback invocation, and callback invocation might or
226	might not be asynchronous.
227
228	These watchers might use C<%SIG>, so programs overwriting those signals
229	directly will likely not work correctly.
230
231	Example: exit on SIGINT
232
233	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
234
235	=head2 CHILD PROCESS WATCHERS
236
237	You can also listen for the status of a child process specified by the
238	C<pid> argument (or any child if the pid argument is 0). The watcher will
239	trigger as often as status change for the child are received. This works
240	by installing a signal handler for C<SIGCHLD>. The callback will be called with
241	the pid and exit status (as returned by waitpid).
242
243	Example: wait for pid 1333
244
245	my $w = AnyEvent->child (pid => 1333, cb => sub { warn "exit status $?" });
246
247	=head1 GLOBALS
248		511
249	=over 4	512	=over 4
250		513
251	=item $AnyEvent::MODEL	514	=item $AnyEvent::MODEL
252		515
…		…
257	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).	520	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).
258		521
259	The known classes so far are:	522	The known classes so far are:
260		523
261	AnyEvent::Impl::CoroEV based on Coro::EV, best choice.	524	AnyEvent::Impl::CoroEV based on Coro::EV, best choice.
262	AnyEvent::Impl::EV based on EV (an interface to libev, also best choice).
263	AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.	525	AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
		526	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
264	AnyEvent::Impl::Event based on Event, also second best choice :)	527	AnyEvent::Impl::Event based on Event, second best choice.
		528	AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
265	AnyEvent::Impl::Glib based on Glib, second-best choice.	529	AnyEvent::Impl::Glib based on Glib, third-best choice.
266	AnyEvent::Impl::Tk based on Tk, very bad choice.	530	AnyEvent::Impl::Tk based on Tk, very bad choice.
267	AnyEvent::Impl::Perl pure-perl implementation, inefficient.	531	AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
		532	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
		533	AnyEvent::Impl::POE based on POE, not generic enough for full support.
		534
		535	There is no support for WxWidgets, as WxWidgets has no support for
		536	watching file handles. However, you can use WxWidgets through the
		537	POE Adaptor, as POE has a Wx backend that simply polls 20 times per
		538	second, which was considered to be too horrible to even consider for
		539	AnyEvent. Likewise, other POE backends can be used by AnyEvent by using
		540	it's adaptor.
		541
		542	AnyEvent knows about L<Prima> and L<Wx> and will try to use L<POE> when
		543	autodetecting them.
268		544
269	=item AnyEvent::detect	545	=item AnyEvent::detect
270		546
271	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model if	547	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
272	necessary. You should only call this function right before you would have	548	if necessary. You should only call this function right before you would
273	created an AnyEvent watcher anyway, that is, very late at runtime.	549	have created an AnyEvent watcher anyway, that is, as late as possible at
		550	runtime.
274		551
275	=back	552	=back
276		553
277	=head1 WHAT TO DO IN A MODULE	554	=head1 WHAT TO DO IN A MODULE
278		555
279	As a module author, you should "use AnyEvent" and call AnyEvent methods	556	As a module author, you should C<use AnyEvent> and call AnyEvent methods
280	freely, but you should not load a specific event module or rely on it.	557	freely, but you should not load a specific event module or rely on it.
281		558
282	Be careful when you create watchers in the module body - Anyevent will	559	Be careful when you create watchers in the module body - AnyEvent will
283	decide which event module to use as soon as the first method is called, so	560	decide which event module to use as soon as the first method is called, so
284	by calling AnyEvent in your module body you force the user of your module	561	by calling AnyEvent in your module body you force the user of your module
285	to load the event module first.	562	to load the event module first.
286		563
		564	Never call C<< ->wait >> on a condition variable unless you I<know> that
		565	the C<< ->send >> method has been called on it already. This is
		566	because it will stall the whole program, and the whole point of using
		567	events is to stay interactive.
		568
		569	It is fine, however, to call C<< ->wait >> when the user of your module
		570	requests it (i.e. if you create a http request object ad have a method
		571	called C<results> that returns the results, it should call C<< ->wait >>
		572	freely, as the user of your module knows what she is doing. always).
		573
287	=head1 WHAT TO DO IN THE MAIN PROGRAM	574	=head1 WHAT TO DO IN THE MAIN PROGRAM
288		575
289	There will always be a single main program - the only place that should	576	There will always be a single main program - the only place that should
290	dictate which event model to use.	577	dictate which event model to use.
291		578
292	If it doesn't care, it can just "use AnyEvent" and use it itself, or not	579	If it doesn't care, it can just "use AnyEvent" and use it itself, or not
293	do anything special and let AnyEvent decide which implementation to chose.	580	do anything special (it does not need to be event-based) and let AnyEvent
		581	decide which implementation to chose if some module relies on it.
294		582
295	If the main program relies on a specific event model (for example, in Gtk2	583	If the main program relies on a specific event model. For example, in
296	programs you have to rely on either Glib or Glib::Event), you should load	584	Gtk2 programs you have to rely on the Glib module. You should load the
297	it before loading AnyEvent or any module that uses it, generally, as early	585	event module before loading AnyEvent or any module that uses it: generally
298	as possible. The reason is that modules might create watchers when they	586	speaking, you should load it as early as possible. The reason is that
299	are loaded, and AnyEvent will decide on the event model to use as soon as	587	modules might create watchers when they are loaded, and AnyEvent will
300	it creates watchers, and it might chose the wrong one unless you load the	588	decide on the event model to use as soon as it creates watchers, and it
301	correct one yourself.	589	might chose the wrong one unless you load the correct one yourself.
302		590
303	You can chose to use a rather inefficient pure-perl implementation by	591	You can chose to use a rather inefficient pure-perl implementation by
304	loading the C<AnyEvent::Impl::Perl> module, but letting AnyEvent chose is	592	loading the C<AnyEvent::Impl::Perl> module, which gives you similar
305	generally better.	593	behaviour everywhere, but letting AnyEvent chose is generally better.
		594
		595	=head1 OTHER MODULES
		596
		597	The following is a non-exhaustive list of additional modules that use
		598	AnyEvent and can therefore be mixed easily with other AnyEvent modules
		599	in the same program. Some of the modules come with AnyEvent, some are
		600	available via CPAN.
		601
		602	=over 4
		603
		604	=item L<AnyEvent::Util>
		605
		606	Contains various utility functions that replace often-used but blocking
		607	functions such as C<inet_aton> by event-/callback-based versions.
		608
		609	=item L<AnyEvent::Handle>
		610
		611	Provide read and write buffers and manages watchers for reads and writes.
		612
		613	=item L<AnyEvent::Socket>
		614
		615	Provides a means to do non-blocking connects, accepts etc.
		616
		617	=item L<AnyEvent::HTTPD>
		618
		619	Provides a simple web application server framework.
		620
		621	=item L<AnyEvent::DNS>
		622
		623	Provides asynchronous DNS resolver capabilities, beyond what
		624	L<AnyEvent::Util> offers.
		625
		626	=item L<AnyEvent::FastPing>
		627
		628	The fastest ping in the west.
		629
		630	=item L<Net::IRC3>
		631
		632	AnyEvent based IRC client module family.
		633
		634	=item L<Net::XMPP2>
		635
		636	AnyEvent based XMPP (Jabber protocol) module family.
		637
		638	=item L<Net::FCP>
		639
		640	AnyEvent-based implementation of the Freenet Client Protocol, birthplace
		641	of AnyEvent.
		642
		643	=item L<Event::ExecFlow>
		644
		645	High level API for event-based execution flow control.
		646
		647	=item L<Coro>
		648
		649	Has special support for AnyEvent.
		650
		651	=item L<IO::Lambda>
		652
		653	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
		654
		655	=item L<IO::AIO>
		656
		657	Truly asynchronous I/O, should be in the toolbox of every event
		658	programmer. Can be trivially made to use AnyEvent.
		659
		660	=item L<BDB>
		661
		662	Truly asynchronous Berkeley DB access. Can be trivially made to use
		663	AnyEvent.
		664
		665	=back
306		666
307	=cut	667	=cut
308		668
309	package AnyEvent;	669	package AnyEvent;
310		670
311	no warnings;	671	no warnings;
312	use strict;	672	use strict;
313		673
314	use Carp;	674	use Carp;
315		675
316	our $VERSION = '3.0';	676	our $VERSION = '3.3';
317	our $MODEL;	677	our $MODEL;
318		678
319	our $AUTOLOAD;	679	our $AUTOLOAD;
320	our @ISA;	680	our @ISA;
321		681
…		…
323		683
324	our @REGISTRY;	684	our @REGISTRY;
325		685
326	my @models = (	686	my @models = (
327	[Coro::EV:: => AnyEvent::Impl::CoroEV::],	687	[Coro::EV:: => AnyEvent::Impl::CoroEV::],
		688	[Coro::Event:: => AnyEvent::Impl::CoroEvent::],
328	[EV:: => AnyEvent::Impl::EV::],	689	[EV:: => AnyEvent::Impl::EV::],
329	[Coro::Event:: => AnyEvent::Impl::CoroEvent::],
330	[Event:: => AnyEvent::Impl::Event::],	690	[Event:: => AnyEvent::Impl::Event::],
		691	[Tk:: => AnyEvent::Impl::Tk::],
		692	[Wx:: => AnyEvent::Impl::POE::],
		693	[Prima:: => AnyEvent::Impl::POE::],
		694	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
		695	# everything below here will not be autoprobed as the pureperl backend should work everywhere
331	[Glib:: => AnyEvent::Impl::Glib::],	696	[Glib:: => AnyEvent::Impl::Glib::],
332	[Tk:: => AnyEvent::Impl::Tk::],	697	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
333	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],	698	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program
		699	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
334	);	700	);
335		701
336	our %method = map +($_ => 1), qw(io timer condvar broadcast wait signal one_event DESTROY);	702	our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY);
337		703
338	sub detect() {	704	sub detect() {
339	unless ($MODEL) {	705	unless ($MODEL) {
340	no strict 'refs';	706	no strict 'refs';
341		707
		708	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
		709	my $model = "AnyEvent::Impl::$1";
		710	if (eval "require $model") {
		711	$MODEL = $model;
		712	warn "AnyEvent: loaded model '$model' (forced by \$PERL_ANYEVENT_MODEL), using it.\n" if $verbose > 1;
		713	} else {
		714	warn "AnyEvent: unable to load model '$model' (from \$PERL_ANYEVENT_MODEL):\n$@" if $verbose;
		715	}
		716	}
		717
342	# check for already loaded models	718	# check for already loaded models
		719	unless ($MODEL) {
343	for (@REGISTRY, @models) {	720	for (@REGISTRY, @models) {
344	my ($package, $model) = @$_;	721	my ($package, $model) = @$_;
345	if (${"$package\::VERSION"} > 0) {	722	if (${"$package\::VERSION"} > 0) {
346	if (eval "require $model") {	723	if (eval "require $model") {
347	$MODEL = $model;	724	$MODEL = $model;
348	warn "AnyEvent: found model '$model', using it.\n" if $verbose > 1;	725	warn "AnyEvent: autodetected model '$model', using it.\n" if $verbose > 1;
349	last;	726	last;
		727	}
350	}	728	}
351	}	729	}
352	}
353		730
354	unless ($MODEL) {	731	unless ($MODEL) {
355	# try to load a model	732	# try to load a model
356		733
357	for (@REGISTRY, @models) {	734	for (@REGISTRY, @models) {
358	my ($package, $model) = @$_;	735	my ($package, $model) = @$_;
359	if (eval "require $package"	736	if (eval "require $package"
360	and ${"$package\::VERSION"} > 0	737	and ${"$package\::VERSION"} > 0
361	and eval "require $model") {	738	and eval "require $model") {
362	$MODEL = $model;	739	$MODEL = $model;
363	warn "AnyEvent: autoprobed and loaded model '$model', using it.\n" if $verbose > 1;	740	warn "AnyEvent: autoprobed model '$model', using it.\n" if $verbose > 1;
364	last;	741	last;
		742	}
365	}	743	}
		744
		745	$MODEL
		746	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV (or Coro+EV), Event (or Coro+Event) or Glib.";
366	}	747	}
367
368	$MODEL
369	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV (or Coro+EV), Event (or Coro+Event), Glib or Tk.";
370	}	748	}
371		749
372	unshift @ISA, $MODEL;	750	unshift @ISA, $MODEL;
373	push @{"$MODEL\::ISA"}, "AnyEvent::Base";	751	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
374	}	752	}
…		…
485	undef $CHLD_W unless keys %PID_CB;	863	undef $CHLD_W unless keys %PID_CB;
486	}	864	}
487		865
488	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE	866	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
489		867
		868	This is an advanced topic that you do not normally need to use AnyEvent in
		869	a module. This section is only of use to event loop authors who want to
		870	provide AnyEvent compatibility.
		871
490	If you need to support another event library which isn't directly	872	If you need to support another event library which isn't directly
491	supported by AnyEvent, you can supply your own interface to it by	873	supported by AnyEvent, you can supply your own interface to it by
492	pushing, before the first watcher gets created, the package name of	874	pushing, before the first watcher gets created, the package name of
493	the event module and the package name of the interface to use onto	875	the event module and the package name of the interface to use onto
494	C<@AnyEvent::REGISTRY>. You can do that before and even without loading	876	C<@AnyEvent::REGISTRY>. You can do that before and even without loading
495	AnyEvent.	877	AnyEvent, so it is reasonably cheap.
496		878
497	Example:	879	Example:
498		880
499	push @AnyEvent::REGISTRY, [urxvt => urxvt::anyevent::];	881	push @AnyEvent::REGISTRY, [urxvt => urxvt::anyevent::];
500		882
501	This tells AnyEvent to (literally) use the C<urxvt::anyevent::>	883	This tells AnyEvent to (literally) use the C<urxvt::anyevent::>
502	package/class when it finds the C<urxvt> package/module is loaded. When	884	package/class when it finds the C<urxvt> package/module is already loaded.
		885
503	AnyEvent is loaded and asked to find a suitable event model, it will	886	When AnyEvent is loaded and asked to find a suitable event model, it
504	first check for the presence of urxvt.	887	will first check for the presence of urxvt by trying to C<use> the
		888	C<urxvt::anyevent> module.
505		889
506	The class should provide implementations for all watcher types (see	890	The class should provide implementations for all watcher types. See
507	L<AnyEvent::Impl::Event> (source code), L<AnyEvent::Impl::Glib>	891	L<AnyEvent::Impl::EV> (source code), L<AnyEvent::Impl::Glib> (Source code)
508	(Source code) and so on for actual examples, use C<perldoc -m	892	and so on for actual examples. Use C<perldoc -m AnyEvent::Impl::Glib> to
509	AnyEvent::Impl::Glib> to see the sources).	893	see the sources.
510		894
		895	If you don't provide C<signal> and C<child> watchers than AnyEvent will
		896	provide suitable (hopefully) replacements.
		897
511	The above isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt)	898	The above example isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt)
512	uses the above line as-is. An interface isn't included in AnyEvent	899	terminal emulator uses the above line as-is. An interface isn't included
513	because it doesn't make sense outside the embedded interpreter inside	900	in AnyEvent because it doesn't make sense outside the embedded interpreter
514	I<rxvt-unicode>, and it is updated and maintained as part of the	901	inside I<rxvt-unicode>, and it is updated and maintained as part of the
515	I<rxvt-unicode> distribution.	902	I<rxvt-unicode> distribution.
516		903
517	I<rxvt-unicode> also cheats a bit by not providing blocking access to	904	I<rxvt-unicode> also cheats a bit by not providing blocking access to
518	condition variables: code blocking while waiting for a condition will	905	condition variables: code blocking while waiting for a condition will
519	C<die>. This still works with most modules/usages, and blocking calls must	906	C<die>. This still works with most modules/usages, and blocking calls must
520	not be in an interactive application, so it makes sense.	907	not be done in an interactive application, so it makes sense.
521		908
522	=head1 ENVIRONMENT VARIABLES	909	=head1 ENVIRONMENT VARIABLES
523		910
524	The following environment variables are used by this module:	911	The following environment variables are used by this module:
525		912
526	C<PERL_ANYEVENT_VERBOSE> when set to C<2> or higher, reports which event	913	=over 4
527	model gets used.
528		914
		915	=item C<PERL_ANYEVENT_VERBOSE>
		916
		917	By default, AnyEvent will be completely silent except in fatal
		918	conditions. You can set this environment variable to make AnyEvent more
		919	talkative.
		920
		921	When set to C<1> or higher, causes AnyEvent to warn about unexpected
		922	conditions, such as not being able to load the event model specified by
		923	C<PERL_ANYEVENT_MODEL>.
		924
		925	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
		926	model it chooses.
		927
		928	=item C<PERL_ANYEVENT_MODEL>
		929
		930	This can be used to specify the event model to be used by AnyEvent, before
		931	autodetection and -probing kicks in. It must be a string consisting
		932	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
		933	and the resulting module name is loaded and if the load was successful,
		934	used as event model. If it fails to load AnyEvent will proceed with
		935	autodetection and -probing.
		936
		937	This functionality might change in future versions.
		938
		939	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
		940	could start your program like this:
		941
		942	PERL_ANYEVENT_MODEL=Perl perl ...
		943
		944	=back
		945
529	=head1 EXAMPLE	946	=head1 EXAMPLE PROGRAM
530		947
531	The following program uses an io watcher to read data from stdin, a timer	948	The following program uses an I/O watcher to read data from STDIN, a timer
532	to display a message once per second, and a condvar to exit the program	949	to display a message once per second, and a condition variable to quit the
533	when the user enters quit:	950	program when the user enters quit:
534		951
535	use AnyEvent;	952	use AnyEvent;
536		953
537	my $cv = AnyEvent->condvar;	954	my $cv = AnyEvent->condvar;
538		955
539	my $io_watcher = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {	956	my $io_watcher = AnyEvent->io (
		957	fh => \*STDIN,
		958	poll => 'r',
		959	cb => sub {
540	warn "io event <$_[0]>\n"; # will always output <r>	960	warn "io event <$_[0]>\n"; # will always output <r>
541	chomp (my $input = <STDIN>); # read a line	961	chomp (my $input = <STDIN>); # read a line
542	warn "read: $input\n"; # output what has been read	962	warn "read: $input\n"; # output what has been read
543	$cv->broadcast if $input =~ /^q/i; # quit program if /^q/i	963	$cv->broadcast if $input =~ /^q/i; # quit program if /^q/i
		964	},
544	});	965	);
545		966
546	my $time_watcher; # can only be used once	967	my $time_watcher; # can only be used once
547		968
548	sub new_timer {	969	sub new_timer {
549	$timer = AnyEvent->timer (after => 1, cb => sub {	970	$timer = AnyEvent->timer (after => 1, cb => sub {
…		…
631	$txn->{finished}->wait;	1052	$txn->{finished}->wait;
632	return $txn->{result};	1053	return $txn->{result};
633		1054
634	The actual code goes further and collects all errors (C<die>s, exceptions)	1055	The actual code goes further and collects all errors (C<die>s, exceptions)
635	that occured during request processing. The C<result> method detects	1056	that occured during request processing. The C<result> method detects
636	wether an exception as thrown (it is stored inside the $txn object)	1057	whether an exception as thrown (it is stored inside the $txn object)
637	and just throws the exception, which means connection errors and other	1058	and just throws the exception, which means connection errors and other
638	problems get reported tot he code that tries to use the result, not in a	1059	problems get reported tot he code that tries to use the result, not in a
639	random callback.	1060	random callback.
640		1061
641	All of this enables the following usage styles:	1062	All of this enables the following usage styles:
642		1063
643	1. Blocking:	1064	1. Blocking:
644		1065
645	my $data = $fcp->client_get ($url);	1066	my $data = $fcp->client_get ($url);
646		1067
647	2. Blocking, but parallelizing:	1068	2. Blocking, but running in parallel:
648		1069
649	my @datas = map $_->result,	1070	my @datas = map $_->result,
650	map $fcp->txn_client_get ($_),	1071	map $fcp->txn_client_get ($_),
651	@urls;	1072	@urls;
652		1073
653	Both blocking examples work without the module user having to know	1074	Both blocking examples work without the module user having to know
654	anything about events.	1075	anything about events.
655		1076
656	3a. Event-based in a main program, using any support Event module:	1077	3a. Event-based in a main program, using any supported event module:
657		1078
658	use Event;	1079	use EV;
659		1080
660	$fcp->txn_client_get ($url)->cb (sub {	1081	$fcp->txn_client_get ($url)->cb (sub {
661	my $txn = shift;	1082	my $txn = shift;
662	my $data = $txn->result;	1083	my $data = $txn->result;
663	...	1084	...
664	});	1085	});
665		1086
666	Event::loop;	1087	EV::loop;
667		1088
668	3b. The module user could use AnyEvent, too:	1089	3b. The module user could use AnyEvent, too:
669		1090
670	use AnyEvent;	1091	use AnyEvent;
671		1092
…		…
676	$quit->broadcast;	1097	$quit->broadcast;
677	});	1098	});
678		1099
679	$quit->wait;	1100	$quit->wait;
680		1101
		1102
		1103	=head1 BENCHMARKS
		1104
		1105	To give you an idea of the performance and overheads that AnyEvent adds
		1106	over the event loops themselves and to give you an impression of the speed
		1107	of various event loops I prepared some benchmarks.
		1108
		1109	=head2 BENCHMARKING ANYEVENT OVERHEAD
		1110
		1111	Here is a benchmark of various supported event models used natively and
		1112	through anyevent. The benchmark creates a lot of timers (with a zero
		1113	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,
		1114	which it is), lets them fire exactly once and destroys them again.
		1115
		1116	Source code for this benchmark is found as F<eg/bench> in the AnyEvent
		1117	distribution.
		1118
		1119	=head3 Explanation of the columns
		1120
		1121	I<watcher> is the number of event watchers created/destroyed. Since
		1122	different event models feature vastly different performances, each event
		1123	loop was given a number of watchers so that overall runtime is acceptable
		1124	and similar between tested event loop (and keep them from crashing): Glib
		1125	would probably take thousands of years if asked to process the same number
		1126	of watchers as EV in this benchmark.
		1127
		1128	I<bytes> is the number of bytes (as measured by the resident set size,
		1129	RSS) consumed by each watcher. This method of measuring captures both C
		1130	and Perl-based overheads.
		1131
		1132	I<create> is the time, in microseconds (millionths of seconds), that it
		1133	takes to create a single watcher. The callback is a closure shared between
		1134	all watchers, to avoid adding memory overhead. That means closure creation
		1135	and memory usage is not included in the figures.
		1136
		1137	I<invoke> is the time, in microseconds, used to invoke a simple
		1138	callback. The callback simply counts down a Perl variable and after it was
		1139	invoked "watcher" times, it would C<< ->broadcast >> a condvar once to
		1140	signal the end of this phase.
		1141
		1142	I<destroy> is the time, in microseconds, that it takes to destroy a single
		1143	watcher.
		1144
		1145	=head3 Results
		1146
		1147	name watchers bytes create invoke destroy comment
		1148	EV/EV 400000 244 0.56 0.46 0.31 EV native interface
		1149	EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers
		1150	CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal
		1151	Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation
		1152	Event/Event 16000 516 31.88 31.30 0.85 Event native interface
		1153	Event/Any 16000 590 35.75 31.42 1.08 Event + AnyEvent watchers
		1154	Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour
		1155	Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers
		1156	POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event
		1157	POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select
		1158
		1159	=head3 Discussion
		1160
		1161	The benchmark does I<not> measure scalability of the event loop very
		1162	well. For example, a select-based event loop (such as the pure perl one)
		1163	can never compete with an event loop that uses epoll when the number of
		1164	file descriptors grows high. In this benchmark, all events become ready at
		1165	the same time, so select/poll-based implementations get an unnatural speed
		1166	boost.
		1167
		1168	Also, note that the number of watchers usually has a nonlinear effect on
		1169	overall speed, that is, creating twice as many watchers doesn't take twice
		1170	the time - usually it takes longer. This puts event loops tested with a
		1171	higher number of watchers at a disadvantage.
		1172
		1173	To put the range of results into perspective, consider that on the
		1174	benchmark machine, handling an event takes roughly 1600 CPU cycles with
		1175	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU
		1176	cycles with POE.
		1177
		1178	C<EV> is the sole leader regarding speed and memory use, which are both
		1179	maximal/minimal, respectively. Even when going through AnyEvent, it uses
		1180	far less memory than any other event loop and is still faster than Event
		1181	natively.
		1182
		1183	The pure perl implementation is hit in a few sweet spots (both the
		1184	constant timeout and the use of a single fd hit optimisations in the perl
		1185	interpreter and the backend itself). Nevertheless this shows that it
		1186	adds very little overhead in itself. Like any select-based backend its
		1187	performance becomes really bad with lots of file descriptors (and few of
		1188	them active), of course, but this was not subject of this benchmark.
		1189
		1190	The C<Event> module has a relatively high setup and callback invocation
		1191	cost, but overall scores in on the third place.
		1192
		1193	C<Glib>'s memory usage is quite a bit higher, but it features a
		1194	faster callback invocation and overall ends up in the same class as
		1195	C<Event>. However, Glib scales extremely badly, doubling the number of
		1196	watchers increases the processing time by more than a factor of four,
		1197	making it completely unusable when using larger numbers of watchers
		1198	(note that only a single file descriptor was used in the benchmark, so
		1199	inefficiencies of C<poll> do not account for this).
		1200
		1201	The C<Tk> adaptor works relatively well. The fact that it crashes with
		1202	more than 2000 watchers is a big setback, however, as correctness takes
		1203	precedence over speed. Nevertheless, its performance is surprising, as the
		1204	file descriptor is dup()ed for each watcher. This shows that the dup()
		1205	employed by some adaptors is not a big performance issue (it does incur a
		1206	hidden memory cost inside the kernel which is not reflected in the figures
		1207	above).
		1208
		1209	C<POE>, regardless of underlying event loop (whether using its pure perl
		1210	select-based backend or the Event module, the POE-EV backend couldn't
		1211	be tested because it wasn't working) shows abysmal performance and
		1212	memory usage with AnyEvent: Watchers use almost 30 times as much memory
		1213	as EV watchers, and 10 times as much memory as Event (the high memory
		1214	requirements are caused by requiring a session for each watcher). Watcher
		1215	invocation speed is almost 900 times slower than with AnyEvent's pure perl
		1216	implementation.
		1217
		1218	The design of the POE adaptor class in AnyEvent can not really account
		1219	for the performance issues, though, as session creation overhead is
		1220	small compared to execution of the state machine, which is coded pretty
		1221	optimally within L<AnyEvent::Impl::POE> (and while everybody agrees that
		1222	using multiple sessions is not a good approach, especially regarding
		1223	memory usage, even the author of POE could not come up with a faster
		1224	design).
		1225
		1226	=head3 Summary
		1227
		1228	=over 4
		1229
		1230	=item * Using EV through AnyEvent is faster than any other event loop
		1231	(even when used without AnyEvent), but most event loops have acceptable
		1232	performance with or without AnyEvent.
		1233
		1234	=item * The overhead AnyEvent adds is usually much smaller than the overhead of
		1235	the actual event loop, only with extremely fast event loops such as EV
		1236	adds AnyEvent significant overhead.
		1237
		1238	=item * You should avoid POE like the plague if you want performance or
		1239	reasonable memory usage.
		1240
		1241	=back
		1242
		1243	=head2 BENCHMARKING THE LARGE SERVER CASE
		1244
		1245	This benchmark atcually benchmarks the event loop itself. It works by
		1246	creating a number of "servers": each server consists of a socketpair, a
		1247	timeout watcher that gets reset on activity (but never fires), and an I/O
		1248	watcher waiting for input on one side of the socket. Each time the socket
		1249	watcher reads a byte it will write that byte to a random other "server".
		1250
		1251	The effect is that there will be a lot of I/O watchers, only part of which
		1252	are active at any one point (so there is a constant number of active
		1253	fds for each loop iterstaion, but which fds these are is random). The
		1254	timeout is reset each time something is read because that reflects how
		1255	most timeouts work (and puts extra pressure on the event loops).
		1256
		1257	In this benchmark, we use 10000 socketpairs (20000 sockets), of which 100
		1258	(1%) are active. This mirrors the activity of large servers with many
		1259	connections, most of which are idle at any one point in time.
		1260
		1261	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent
		1262	distribution.
		1263
		1264	=head3 Explanation of the columns
		1265
		1266	I<sockets> is the number of sockets, and twice the number of "servers" (as
		1267	each server has a read and write socket end).
		1268
		1269	I<create> is the time it takes to create a socketpair (which is
		1270	nontrivial) and two watchers: an I/O watcher and a timeout watcher.
		1271
		1272	I<request>, the most important value, is the time it takes to handle a
		1273	single "request", that is, reading the token from the pipe and forwarding
		1274	it to another server. This includes deleting the old timeout and creating
		1275	a new one that moves the timeout into the future.
		1276
		1277	=head3 Results
		1278
		1279	name sockets create request
		1280	EV 20000 69.01 11.16
		1281	Perl 20000 73.32 35.87
		1282	Event 20000 212.62 257.32
		1283	Glib 20000 651.16 1896.30
		1284	POE 20000 349.67 12317.24 uses POE::Loop::Event
		1285
		1286	=head3 Discussion
		1287
		1288	This benchmark I<does> measure scalability and overall performance of the
		1289	particular event loop.
		1290
		1291	EV is again fastest. Since it is using epoll on my system, the setup time
		1292	is relatively high, though.
		1293
		1294	Perl surprisingly comes second. It is much faster than the C-based event
		1295	loops Event and Glib.
		1296
		1297	Event suffers from high setup time as well (look at its code and you will
		1298	understand why). Callback invocation also has a high overhead compared to
		1299	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event
		1300	uses select or poll in basically all documented configurations.
		1301
		1302	Glib is hit hard by its quadratic behaviour w.r.t. many watchers. It
		1303	clearly fails to perform with many filehandles or in busy servers.
		1304
		1305	POE is still completely out of the picture, taking over 1000 times as long
		1306	as EV, and over 100 times as long as the Perl implementation, even though
		1307	it uses a C-based event loop in this case.
		1308
		1309	=head3 Summary
		1310
		1311	=over 4
		1312
		1313	=item * The pure perl implementation performs extremely well.
		1314
		1315	=item * Avoid Glib or POE in large projects where performance matters.
		1316
		1317	=back
		1318
		1319	=head2 BENCHMARKING SMALL SERVERS
		1320
		1321	While event loops should scale (and select-based ones do not...) even to
		1322	large servers, most programs we (or I :) actually write have only a few
		1323	I/O watchers.
		1324
		1325	In this benchmark, I use the same benchmark program as in the large server
		1326	case, but it uses only eight "servers", of which three are active at any
		1327	one time. This should reflect performance for a small server relatively
		1328	well.
		1329
		1330	The columns are identical to the previous table.
		1331
		1332	=head3 Results
		1333
		1334	name sockets create request
		1335	EV 16 20.00 6.54
		1336	Perl 16 25.75 12.62
		1337	Event 16 81.27 35.86
		1338	Glib 16 32.63 15.48
		1339	POE 16 261.87 276.28 uses POE::Loop::Event
		1340
		1341	=head3 Discussion
		1342
		1343	The benchmark tries to test the performance of a typical small
		1344	server. While knowing how various event loops perform is interesting, keep
		1345	in mind that their overhead in this case is usually not as important, due
		1346	to the small absolute number of watchers (that is, you need efficiency and
		1347	speed most when you have lots of watchers, not when you only have a few of
		1348	them).
		1349
		1350	EV is again fastest.
		1351
		1352	Perl again comes second. It is noticably faster than the C-based event
		1353	loops Event and Glib, although the difference is too small to really
		1354	matter.
		1355
		1356	POE also performs much better in this case, but is is still far behind the
		1357	others.
		1358
		1359	=head3 Summary
		1360
		1361	=over 4
		1362
		1363	=item * C-based event loops perform very well with small number of
		1364	watchers, as the management overhead dominates.
		1365
		1366	=back
		1367
		1368
		1369	=head1 FORK
		1370
		1371	Most event libraries are not fork-safe. The ones who are usually are
		1372	because they rely on inefficient but fork-safe C<select> or C<poll>
		1373	calls. Only L<EV> is fully fork-aware.
		1374
		1375	If you have to fork, you must either do so I<before> creating your first
		1376	watcher OR you must not use AnyEvent at all in the child.
		1377
		1378
		1379	=head1 SECURITY CONSIDERATIONS
		1380
		1381	AnyEvent can be forced to load any event model via
		1382	$ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used to
		1383	execute arbitrary code or directly gain access, it can easily be used to
		1384	make the program hang or malfunction in subtle ways, as AnyEvent watchers
		1385	will not be active when the program uses a different event model than
		1386	specified in the variable.
		1387
		1388	You can make AnyEvent completely ignore this variable by deleting it
		1389	before the first watcher gets created, e.g. with a C<BEGIN> block:
		1390
		1391	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }
		1392
		1393	use AnyEvent;
		1394
		1395
681	=head1 SEE ALSO	1396	=head1 SEE ALSO
682		1397
683	Event modules: L<Coro::Event>, L<Coro>, L<Event>, L<Glib::Event>, L<Glib>.	1398	Event modules: L<Coro::EV>, L<EV>, L<EV::Glib>, L<Glib::EV>,
		1399	L<Coro::Event>, L<Event>, L<Glib::Event>, L<Glib>, L<Coro>, L<Tk>,
		1400	L<Event::Lib>, L<Qt>, L<POE>.
684		1401
		1402	Implementations: L<AnyEvent::Impl::CoroEV>, L<AnyEvent::Impl::EV>,
685	Implementations: L<AnyEvent::Impl::Coro>, L<AnyEvent::Impl::Event>, L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>.	1403	L<AnyEvent::Impl::CoroEvent>, L<AnyEvent::Impl::Event>, L<AnyEvent::Impl::Glib>,
		1404	L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, L<AnyEvent::Impl::EventLib>,
		1405	L<AnyEvent::Impl::Qt>, L<AnyEvent::Impl::POE>.
686		1406
687	Nontrivial usage example: L<Net::FCP>.	1407	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>.
688		1408
689	=head1	1409
		1410	=head1 AUTHOR
		1411
		1412	Marc Lehmann <schmorp@schmorp.de>
		1413	http://home.schmorp.de/
690		1414
691	=cut	1415	=cut
692		1416
693	1	1417	1
694		1418

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.47 by root, Mon Apr 14 16:09:33 2008 UTC vs. Revision 1.106 by root, Thu May 1 13:45:22 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.47 by root, Mon Apr 14 16:09:33 2008 UTC vs.
Revision 1.106 by root, Thu May 1 13:45:22 2008 UTC