ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.164 by root, Tue Jul 8 19:50:25 2008 UTC vs.
Revision 1.296 by root, Tue Nov 17 01:19:49 2009 UTC

1	=head1 NAME	1	=head1 NAME
2		2
3	AnyEvent - provide framework for multiple event loops	3	AnyEvent - the DBI of event loop programming
4		4
5	EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops	5	EV, Event, Glib, Tk, Perl, Event::Lib, Irssi, rxvt-unicode, IO::Async, Qt
		6	and POE are various supported event loops/environments.
6		7
7	=head1 SYNOPSIS	8	=head1 SYNOPSIS
8		9
9	use AnyEvent;	10	use AnyEvent;
10		11
		12	# file descriptor readable
11	my $w = AnyEvent->io (fh => $fh, poll => "r|w", cb => sub {	13	my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... });
		14
		15	# one-shot or repeating timers
		16	my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });
		17	my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...
		18
		19	print AnyEvent->now; # prints current event loop time
		20	print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
		21
		22	# POSIX signal
		23	my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... });
		24
		25	# child process exit
		26	my $w = AnyEvent->child (pid => $pid, cb => sub {
		27	my ($pid, $status) = @_;
12	...	28	...
13	});	29	});
14		30
15	my $w = AnyEvent->timer (after => $seconds, cb => sub {	31	# called when event loop idle (if applicable)
16	...	32	my $w = AnyEvent->idle (cb => sub { ... });
17	});
18		33
19	my $w = AnyEvent->condvar; # stores whether a condition was flagged	34	my $w = AnyEvent->condvar; # stores whether a condition was flagged
20	$w->send; # wake up current and all future recv's	35	$w->send; # wake up current and all future recv's
21	$w->recv; # enters "main loop" till $condvar gets ->send	36	$w->recv; # enters "main loop" till $condvar gets ->send
		37	# use a condvar in callback mode:
		38	$w->cb (sub { $_[0]->recv });
22		39
23	=head1 INTRODUCTION/TUTORIAL	40	=head1 INTRODUCTION/TUTORIAL
24		41
25	This manpage is mainly a reference manual. If you are interested	42	This manpage is mainly a reference manual. If you are interested
26	in a tutorial or some gentle introduction, have a look at the	43	in a tutorial or some gentle introduction, have a look at the
27	L<AnyEvent::Intro> manpage.	44	L<AnyEvent::Intro> manpage.
28		45
		46	=head1 SUPPORT
		47
		48	There is a mailinglist for discussing all things AnyEvent, and an IRC
		49	channel, too.
		50
		51	See the AnyEvent project page at the B<Schmorpforge Ta-Sa Software
		52	Repository>, at L<http://anyevent.schmorp.de>, for more info.
		53
29	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)	54	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
30		55
31	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen	56	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
32	nowadays. So what is different about AnyEvent?	57	nowadays. So what is different about AnyEvent?
33		58
34	Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of	59	Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of
35	policy> and AnyEvent is I<small and efficient>.	60	policy> and AnyEvent is I<small and efficient>.
36		61
37	First and foremost, I<AnyEvent is not an event model> itself, it only	62	First and foremost, I<AnyEvent is not an event model> itself, it only
38	interfaces to whatever event model the main program happens to use in a	63	interfaces to whatever event model the main program happens to use, in a
39	pragmatic way. For event models and certain classes of immortals alike,	64	pragmatic way. For event models and certain classes of immortals alike,
40	the statement "there can only be one" is a bitter reality: In general,	65	the statement "there can only be one" is a bitter reality: In general,
41	only one event loop can be active at the same time in a process. AnyEvent	66	only one event loop can be active at the same time in a process. AnyEvent
42	helps hiding the differences between those event loops.	67	cannot change this, but it can hide the differences between those event
		68	loops.
43		69
44	The goal of AnyEvent is to offer module authors the ability to do event	70	The goal of AnyEvent is to offer module authors the ability to do event
45	programming (waiting for I/O or timer events) without subscribing to a	71	programming (waiting for I/O or timer events) without subscribing to a
46	religion, a way of living, and most importantly: without forcing your	72	religion, a way of living, and most importantly: without forcing your
47	module users into the same thing by forcing them to use the same event	73	module users into the same thing by forcing them to use the same event
48	model you use.	74	model you use.
49		75
50	For modules like POE or IO::Async (which is a total misnomer as it is	76	For modules like POE or IO::Async (which is a total misnomer as it is
51	actually doing all I/O I<synchronously>...), using them in your module is	77	actually doing all I/O I<synchronously>...), using them in your module is
52	like joining a cult: After you joined, you are dependent on them and you	78	like joining a cult: After you joined, you are dependent on them and you
53	cannot use anything else, as it is simply incompatible to everything that	79	cannot use anything else, as they are simply incompatible to everything
54	isn't itself. What's worse, all the potential users of your module are	80	that isn't them. What's worse, all the potential users of your
55	I<also> forced to use the same event loop you use.	81	module are I<also> forced to use the same event loop you use.
56		82
57	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works	83	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
58	fine. AnyEvent + Tk works fine etc. etc. but none of these work together	84	fine. AnyEvent + Tk works fine etc. etc. but none of these work together
59	with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if	85	with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if
60	your module uses one of those, every user of your module has to use it,	86	your module uses one of those, every user of your module has to use it,
61	too. But if your module uses AnyEvent, it works transparently with all	87	too. But if your module uses AnyEvent, it works transparently with all
62	event models it supports (including stuff like POE and IO::Async, as long	88	event models it supports (including stuff like IO::Async, as long as those
63	as those use one of the supported event loops. It is trivial to add new	89	use one of the supported event loops. It is trivial to add new event loops
64	event loops to AnyEvent, too, so it is future-proof).	90	to AnyEvent, too, so it is future-proof).
65		91
66	In addition to being free of having to use I<the one and only true event	92	In addition to being free of having to use I<the one and only true event
67	model>, AnyEvent also is free of bloat and policy: with POE or similar	93	model>, AnyEvent also is free of bloat and policy: with POE or similar
68	modules, you get an enormous amount of code and strict rules you have to	94	modules, you get an enormous amount of code and strict rules you have to
69	follow. AnyEvent, on the other hand, is lean and up to the point, by only	95	follow. AnyEvent, on the other hand, is lean and up to the point, by only
…		…
127	These watchers are normal Perl objects with normal Perl lifetime. After	153	These watchers are normal Perl objects with normal Perl lifetime. After
128	creating a watcher it will immediately "watch" for events and invoke the	154	creating a watcher it will immediately "watch" for events and invoke the
129	callback when the event occurs (of course, only when the event model	155	callback when the event occurs (of course, only when the event model
130	is in control).	156	is in control).
131		157
		158	Note that B<callbacks must not permanently change global variables>
		159	potentially in use by the event loop (such as C<$_> or C<$[>) and that B<<
		160	callbacks must not C<die> >>. The former is good programming practise in
		161	Perl and the latter stems from the fact that exception handling differs
		162	widely between event loops.
		163
132	To disable the watcher you have to destroy it (e.g. by setting the	164	To disable the watcher you have to destroy it (e.g. by setting the
133	variable you store it in to C<undef> or otherwise deleting all references	165	variable you store it in to C<undef> or otherwise deleting all references
134	to it).	166	to it).
135		167
136	All watchers are created by calling a method on the C<AnyEvent> class.	168	All watchers are created by calling a method on the C<AnyEvent> class.
…		…
149	my variables are only visible after the statement in which they are	181	my variables are only visible after the statement in which they are
150	declared.	182	declared.
151		183
152	=head2 I/O WATCHERS	184	=head2 I/O WATCHERS
153		185
		186	$w = AnyEvent->io (
		187	fh => <filehandle_or_fileno>,
		188	poll => <"r" or "w">,
		189	cb => <callback>,
		190	);
		191
154	You can create an I/O watcher by calling the C<< AnyEvent->io >> method	192	You can create an I/O watcher by calling the C<< AnyEvent->io >> method
155	with the following mandatory key-value pairs as arguments:	193	with the following mandatory key-value pairs as arguments:
156		194
157	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch	195	C<fh> is the Perl I<file handle> (or a naked file descriptor) to watch
		196	for events (AnyEvent might or might not keep a reference to this file
		197	handle). Note that only file handles pointing to things for which
		198	non-blocking operation makes sense are allowed. This includes sockets,
		199	most character devices, pipes, fifos and so on, but not for example files
		200	or block devices.
		201
158	for events. C<poll> must be a string that is either C<r> or C<w>,	202	C<poll> must be a string that is either C<r> or C<w>, which creates a
159	which creates a watcher waiting for "r"eadable or "w"ritable events,	203	watcher waiting for "r"eadable or "w"ritable events, respectively.
		204
160	respectively. C<cb> is the callback to invoke each time the file handle	205	C<cb> is the callback to invoke each time the file handle becomes ready.
161	becomes ready.
162		206
163	Although the callback might get passed parameters, their value and	207	Although the callback might get passed parameters, their value and
164	presence is undefined and you cannot rely on them. Portable AnyEvent	208	presence is undefined and you cannot rely on them. Portable AnyEvent
165	callbacks cannot use arguments passed to I/O watcher callbacks.	209	callbacks cannot use arguments passed to I/O watcher callbacks.
166		210
…		…
181	undef $w;	225	undef $w;
182	});	226	});
183		227
184	=head2 TIME WATCHERS	228	=head2 TIME WATCHERS
185		229
		230	$w = AnyEvent->timer (after => <seconds>, cb => <callback>);
		231
		232	$w = AnyEvent->timer (
		233	after => <fractional_seconds>,
		234	interval => <fractional_seconds>,
		235	cb => <callback>,
		236	);
		237
186	You can create a time watcher by calling the C<< AnyEvent->timer >>	238	You can create a time watcher by calling the C<< AnyEvent->timer >>
187	method with the following mandatory arguments:	239	method with the following mandatory arguments:
188		240
189	C<after> specifies after how many seconds (fractional values are	241	C<after> specifies after how many seconds (fractional values are
190	supported) the callback should be invoked. C<cb> is the callback to invoke	242	supported) the callback should be invoked. C<cb> is the callback to invoke
…		…
193	Although the callback might get passed parameters, their value and	245	Although the callback might get passed parameters, their value and
194	presence is undefined and you cannot rely on them. Portable AnyEvent	246	presence is undefined and you cannot rely on them. Portable AnyEvent
195	callbacks cannot use arguments passed to time watcher callbacks.	247	callbacks cannot use arguments passed to time watcher callbacks.
196		248
197	The callback will normally be invoked once only. If you specify another	249	The callback will normally be invoked once only. If you specify another
198	parameter, C<interval>, as a positive number, then the callback will be	250	parameter, C<interval>, as a strictly positive number (> 0), then the
199	invoked regularly at that interval (in fractional seconds) after the first	251	callback will be invoked regularly at that interval (in fractional
200	invocation.	252	seconds) after the first invocation. If C<interval> is specified with a
		253	false value, then it is treated as if it were missing.
201		254
202	The callback will be rescheduled before invoking the callback, but no	255	The callback will be rescheduled before invoking the callback, but no
203	attempt is done to avoid timer drift in most backends, so the interval is	256	attempt is done to avoid timer drift in most backends, so the interval is
204	only approximate.	257	only approximate.
205		258
…		…
297	In either case, if you care (and in most cases, you don't), then you	350	In either case, if you care (and in most cases, you don't), then you
298	can get whatever behaviour you want with any event loop, by taking the	351	can get whatever behaviour you want with any event loop, by taking the
299	difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into	352	difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into
300	account.	353	account.
301		354
		355	=item AnyEvent->now_update
		356
		357	Some event loops (such as L<EV> or L<AnyEvent::Impl::Perl>) cache
		358	the current time for each loop iteration (see the discussion of L<<
		359	AnyEvent->now >>, above).
		360
		361	When a callback runs for a long time (or when the process sleeps), then
		362	this "current" time will differ substantially from the real time, which
		363	might affect timers and time-outs.
		364
		365	When this is the case, you can call this method, which will update the
		366	event loop's idea of "current time".
		367
		368	A typical example would be a script in a web server (e.g. C<mod_perl>) -
		369	when mod_perl executes the script, then the event loop will have the wrong
		370	idea about the "current time" (being potentially far in the past, when the
		371	script ran the last time). In that case you should arrange a call to C<<
		372	AnyEvent->now_update >> each time the web server process wakes up again
		373	(e.g. at the start of your script, or in a handler).
		374
		375	Note that updating the time I<might> cause some events to be handled.
		376
302	=back	377	=back
303		378
304	=head2 SIGNAL WATCHERS	379	=head2 SIGNAL WATCHERS
305		380
		381	$w = AnyEvent->signal (signal => <uppercase_signal_name>, cb => <callback>);
		382
306	You can watch for signals using a signal watcher, C<signal> is the signal	383	You can watch for signals using a signal watcher, C<signal> is the signal
307	I<name> without any C<SIG> prefix, C<cb> is the Perl callback to	384	I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl
308	be invoked whenever a signal occurs.	385	callback to be invoked whenever a signal occurs.
309		386
310	Although the callback might get passed parameters, their value and	387	Although the callback might get passed parameters, their value and
311	presence is undefined and you cannot rely on them. Portable AnyEvent	388	presence is undefined and you cannot rely on them. Portable AnyEvent
312	callbacks cannot use arguments passed to signal watcher callbacks.	389	callbacks cannot use arguments passed to signal watcher callbacks.
313		390
…		…
315	invocation, and callback invocation will be synchronous. Synchronous means	392	invocation, and callback invocation will be synchronous. Synchronous means
316	that it might take a while until the signal gets handled by the process,	393	that it might take a while until the signal gets handled by the process,
317	but it is guaranteed not to interrupt any other callbacks.	394	but it is guaranteed not to interrupt any other callbacks.
318		395
319	The main advantage of using these watchers is that you can share a signal	396	The main advantage of using these watchers is that you can share a signal
320	between multiple watchers.	397	between multiple watchers, and AnyEvent will ensure that signals will not
		398	interrupt your program at bad times.
321		399
322	This watcher might use C<%SIG>, so programs overwriting those signals	400	This watcher might use C<%SIG> (depending on the event loop used),
323	directly will likely not work correctly.	401	so programs overwriting those signals directly will likely not work
		402	correctly.
324		403
325	Example: exit on SIGINT	404	Example: exit on SIGINT
326		405
327	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });	406	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
328		407
		408	=head3 Signal Races, Delays and Workarounds
		409
		410	Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching
		411	callbacks to signals in a generic way, which is a pity, as you cannot
		412	do race-free signal handling in perl, requiring C libraries for
		413	this. AnyEvent will try to do it's best, which means in some cases,
		414	signals will be delayed. The maximum time a signal might be delayed is
		415	specified in C<$AnyEvent::MAX_SIGNAL_LATENCY> (default: 10 seconds). This
		416	variable can be changed only before the first signal watcher is created,
		417	and should be left alone otherwise. This variable determines how often
		418	AnyEvent polls for signals (in case a wake-up was missed). Higher values
		419	will cause fewer spurious wake-ups, which is better for power and CPU
		420	saving.
		421
		422	All these problems can be avoided by installing the optional
		423	L<Async::Interrupt> module, which works with most event loops. It will not
		424	work with inherently broken event loops such as L<Event> or L<Event::Lib>
		425	(and not with L<POE> currently, as POE does it's own workaround with
		426	one-second latency). For those, you just have to suffer the delays.
		427
329	=head2 CHILD PROCESS WATCHERS	428	=head2 CHILD PROCESS WATCHERS
330		429
		430	$w = AnyEvent->child (pid => <process id>, cb => <callback>);
		431
331	You can also watch on a child process exit and catch its exit status.	432	You can also watch on a child process exit and catch its exit status.
332		433
333	The child process is specified by the C<pid> argument (if set to C<0>, it	434	The child process is specified by the C<pid> argument (one some backends,
334	watches for any child process exit). The watcher will trigger as often	435	using C<0> watches for any child process exit, on others this will
335	as status change for the child are received. This works by installing a	436	croak). The watcher will be triggered only when the child process has
336	signal handler for C<SIGCHLD>. The callback will be called with the pid	437	finished and an exit status is available, not on any trace events
337	and exit status (as returned by waitpid), so unlike other watcher types,	438	(stopped/continued).
338	you I<can> rely on child watcher callback arguments.	439
		440	The callback will be called with the pid and exit status (as returned by
		441	waitpid), so unlike other watcher types, you I<can> rely on child watcher
		442	callback arguments.
		443
		444	This watcher type works by installing a signal handler for C<SIGCHLD>,
		445	and since it cannot be shared, nothing else should use SIGCHLD or reap
		446	random child processes (waiting for specific child processes, e.g. inside
		447	C<system>, is just fine).
339		448
340	There is a slight catch to child watchers, however: you usually start them	449	There is a slight catch to child watchers, however: you usually start them
341	I<after> the child process was created, and this means the process could	450	I<after> the child process was created, and this means the process could
342	have exited already (and no SIGCHLD will be sent anymore).	451	have exited already (and no SIGCHLD will be sent anymore).
343		452
344	Not all event models handle this correctly (POE doesn't), but even for	453	Not all event models handle this correctly (neither POE nor IO::Async do,
		454	see their AnyEvent::Impl manpages for details), but even for event models
345	event models that I<do> handle this correctly, they usually need to be	455	that I<do> handle this correctly, they usually need to be loaded before
346	loaded before the process exits (i.e. before you fork in the first place).	456	the process exits (i.e. before you fork in the first place). AnyEvent's
		457	pure perl event loop handles all cases correctly regardless of when you
		458	start the watcher.
347		459
348	This means you cannot create a child watcher as the very first thing in an	460	This means you cannot create a child watcher as the very first
349	AnyEvent program, you I<have> to create at least one watcher before you	461	thing in an AnyEvent program, you I<have> to create at least one
350	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).	462	watcher before you C<fork> the child (alternatively, you can call
		463	C<AnyEvent::detect>).
		464
		465	As most event loops do not support waiting for child events, they will be
		466	emulated by AnyEvent in most cases, in which the latency and race problems
		467	mentioned in the description of signal watchers apply.
351		468
352	Example: fork a process and wait for it	469	Example: fork a process and wait for it
353		470
354	my $done = AnyEvent->condvar;	471	my $done = AnyEvent->condvar;
355		472
…		…
365	);	482	);
366		483
367	# do something else, then wait for process exit	484	# do something else, then wait for process exit
368	$done->recv;	485	$done->recv;
369		486
		487	=head2 IDLE WATCHERS
		488
		489	$w = AnyEvent->idle (cb => <callback>);
		490
		491	Sometimes there is a need to do something, but it is not so important
		492	to do it instantly, but only when there is nothing better to do. This
		493	"nothing better to do" is usually defined to be "no other events need
		494	attention by the event loop".
		495
		496	Idle watchers ideally get invoked when the event loop has nothing
		497	better to do, just before it would block the process to wait for new
		498	events. Instead of blocking, the idle watcher is invoked.
		499
		500	Most event loops unfortunately do not really support idle watchers (only
		501	EV, Event and Glib do it in a usable fashion) - for the rest, AnyEvent
		502	will simply call the callback "from time to time".
		503
		504	Example: read lines from STDIN, but only process them when the
		505	program is otherwise idle:
		506
		507	my @lines; # read data
		508	my $idle_w;
		509	my $io_w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
		510	push @lines, scalar <STDIN>;
		511
		512	# start an idle watcher, if not already done
		513	$idle_w ||= AnyEvent->idle (cb => sub {
		514	# handle only one line, when there are lines left
		515	if (my $line = shift @lines) {
		516	print "handled when idle: $line";
		517	} else {
		518	# otherwise disable the idle watcher again
		519	undef $idle_w;
		520	}
		521	});
		522	});
		523
370	=head2 CONDITION VARIABLES	524	=head2 CONDITION VARIABLES
		525
		526	$cv = AnyEvent->condvar;
		527
		528	$cv->send (<list>);
		529	my @res = $cv->recv;
371		530
372	If you are familiar with some event loops you will know that all of them	531	If you are familiar with some event loops you will know that all of them
373	require you to run some blocking "loop", "run" or similar function that	532	require you to run some blocking "loop", "run" or similar function that
374	will actively watch for new events and call your callbacks.	533	will actively watch for new events and call your callbacks.
375		534
376	AnyEvent is different, it expects somebody else to run the event loop and	535	AnyEvent is slightly different: it expects somebody else to run the event
377	will only block when necessary (usually when told by the user).	536	loop and will only block when necessary (usually when told by the user).
378		537
379	The instrument to do that is called a "condition variable", so called	538	The instrument to do that is called a "condition variable", so called
380	because they represent a condition that must become true.	539	because they represent a condition that must become true.
		540
		541	Now is probably a good time to look at the examples further below.
381		542
382	Condition variables can be created by calling the C<< AnyEvent->condvar	543	Condition variables can be created by calling the C<< AnyEvent->condvar
383	>> method, usually without arguments. The only argument pair allowed is	544	>> method, usually without arguments. The only argument pair allowed is
384	C<cb>, which specifies a callback to be called when the condition variable	545	C<cb>, which specifies a callback to be called when the condition variable
385	becomes true.	546	becomes true, with the condition variable as the first argument (but not
		547	the results).
386		548
387	After creation, the condition variable is "false" until it becomes "true"	549	After creation, the condition variable is "false" until it becomes "true"
388	by calling the C<send> method (or calling the condition variable as if it	550	by calling the C<send> method (or calling the condition variable as if it
389	were a callback, read about the caveats in the description for the C<<	551	were a callback, read about the caveats in the description for the C<<
390	->send >> method).	552	->send >> method).
…		…
392	Condition variables are similar to callbacks, except that you can	554	Condition variables are similar to callbacks, except that you can
393	optionally wait for them. They can also be called merge points - points	555	optionally wait for them. They can also be called merge points - points
394	in time where multiple outstanding events have been processed. And yet	556	in time where multiple outstanding events have been processed. And yet
395	another way to call them is transactions - each condition variable can be	557	another way to call them is transactions - each condition variable can be
396	used to represent a transaction, which finishes at some point and delivers	558	used to represent a transaction, which finishes at some point and delivers
397	a result.	559	a result. And yet some people know them as "futures" - a promise to
		560	compute/deliver something that you can wait for.
398		561
399	Condition variables are very useful to signal that something has finished,	562	Condition variables are very useful to signal that something has finished,
400	for example, if you write a module that does asynchronous http requests,	563	for example, if you write a module that does asynchronous http requests,
401	then a condition variable would be the ideal candidate to signal the	564	then a condition variable would be the ideal candidate to signal the
402	availability of results. The user can either act when the callback is	565	availability of results. The user can either act when the callback is
…		…
436	after => 1,	599	after => 1,
437	cb => sub { $result_ready->send },	600	cb => sub { $result_ready->send },
438	);	601	);
439		602
440	# this "blocks" (while handling events) till the callback	603	# this "blocks" (while handling events) till the callback
441	# calls send	604	# calls ->send
442	$result_ready->recv;	605	$result_ready->recv;
443		606
444	Example: wait for a timer, but take advantage of the fact that	607	Example: wait for a timer, but take advantage of the fact that condition
445	condition variables are also code references.	608	variables are also callable directly.
446		609
447	my $done = AnyEvent->condvar;	610	my $done = AnyEvent->condvar;
448	my $delay = AnyEvent->timer (after => 5, cb => $done);	611	my $delay = AnyEvent->timer (after => 5, cb => $done);
449	$done->recv;	612	$done->recv;
		613
		614	Example: Imagine an API that returns a condvar and doesn't support
		615	callbacks. This is how you make a synchronous call, for example from
		616	the main program:
		617
		618	use AnyEvent::CouchDB;
		619
		620	...
		621
		622	my @info = $couchdb->info->recv;
		623
		624	And this is how you would just set a callback to be called whenever the
		625	results are available:
		626
		627	$couchdb->info->cb (sub {
		628	my @info = $_[0]->recv;
		629	});
450		630
451	=head3 METHODS FOR PRODUCERS	631	=head3 METHODS FOR PRODUCERS
452		632
453	These methods should only be used by the producing side, i.e. the	633	These methods should only be used by the producing side, i.e. the
454	code/module that eventually sends the signal. Note that it is also	634	code/module that eventually sends the signal. Note that it is also
…		…
467	immediately from within send.	647	immediately from within send.
468		648
469	Any arguments passed to the C<send> call will be returned by all	649	Any arguments passed to the C<send> call will be returned by all
470	future C<< ->recv >> calls.	650	future C<< ->recv >> calls.
471		651
472	Condition variables are overloaded so one can call them directly	652	Condition variables are overloaded so one can call them directly (as if
473	(as a code reference). Calling them directly is the same as calling	653	they were a code reference). Calling them directly is the same as calling
474	C<send>. Note, however, that many C-based event loops do not handle	654	C<send>.
475	overloading, so as tempting as it may be, passing a condition variable
476	instead of a callback does not work. Both the pure perl and EV loops
477	support overloading, however, as well as all functions that use perl to
478	invoke a callback (as in L<AnyEvent::Socket> and L<AnyEvent::DNS> for
479	example).
480		655
481	=item $cv->croak ($error)	656	=item $cv->croak ($error)
482		657
483	Similar to send, but causes all call's to C<< ->recv >> to invoke	658	Similar to send, but causes all call's to C<< ->recv >> to invoke
484	C<Carp::croak> with the given error message/object/scalar.	659	C<Carp::croak> with the given error message/object/scalar.
485		660
486	This can be used to signal any errors to the condition variable	661	This can be used to signal any errors to the condition variable
487	user/consumer.	662	user/consumer. Doing it this way instead of calling C<croak> directly
		663	delays the error detetcion, but has the overwhelmign advantage that it
		664	diagnoses the error at the place where the result is expected, and not
		665	deep in some event clalback without connection to the actual code causing
		666	the problem.
488		667
489	=item $cv->begin ([group callback])	668	=item $cv->begin ([group callback])
490		669
491	=item $cv->end	670	=item $cv->end
492
493	These two methods are EXPERIMENTAL and MIGHT CHANGE.
494		671
495	These two methods can be used to combine many transactions/events into	672	These two methods can be used to combine many transactions/events into
496	one. For example, a function that pings many hosts in parallel might want	673	one. For example, a function that pings many hosts in parallel might want
497	to use a condition variable for the whole process.	674	to use a condition variable for the whole process.
498		675
499	Every call to C<< ->begin >> will increment a counter, and every call to	676	Every call to C<< ->begin >> will increment a counter, and every call to
500	C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end	677	C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end
501	>>, the (last) callback passed to C<begin> will be executed. That callback	678	>>, the (last) callback passed to C<begin> will be executed, passing the
502	is I<supposed> to call C<< ->send >>, but that is not required. If no	679	condvar as first argument. That callback is I<supposed> to call C<< ->send
503	callback was set, C<send> will be called without any arguments.	680	>>, but that is not required. If no group callback was set, C<send> will
		681	be called without any arguments.
504		682
505	Let's clarify this with the ping example:	683	You can think of C<< $cv->send >> giving you an OR condition (one call
		684	sends), while C<< $cv->begin >> and C<< $cv->end >> giving you an AND
		685	condition (all C<begin> calls must be C<end>'ed before the condvar sends).
		686
		687	Let's start with a simple example: you have two I/O watchers (for example,
		688	STDOUT and STDERR for a program), and you want to wait for both streams to
		689	close before activating a condvar:
506		690
507	my $cv = AnyEvent->condvar;	691	my $cv = AnyEvent->condvar;
508		692
		693	$cv->begin; # first watcher
		694	my $w1 = AnyEvent->io (fh => $fh1, cb => sub {
		695	defined sysread $fh1, my $buf, 4096
		696	or $cv->end;
		697	});
		698
		699	$cv->begin; # second watcher
		700	my $w2 = AnyEvent->io (fh => $fh2, cb => sub {
		701	defined sysread $fh2, my $buf, 4096
		702	or $cv->end;
		703	});
		704
		705	$cv->recv;
		706
		707	This works because for every event source (EOF on file handle), there is
		708	one call to C<begin>, so the condvar waits for all calls to C<end> before
		709	sending.
		710
		711	The ping example mentioned above is slightly more complicated, as the
		712	there are results to be passwd back, and the number of tasks that are
		713	begung can potentially be zero:
		714
		715	my $cv = AnyEvent->condvar;
		716
509	my %result;	717	my %result;
510	$cv->begin (sub { $cv->send (\%result) });	718	$cv->begin (sub { shift->send (\%result) });
511		719
512	for my $host (@list_of_hosts) {	720	for my $host (@list_of_hosts) {
513	$cv->begin;	721	$cv->begin;
514	ping_host_then_call_callback $host, sub {	722	ping_host_then_call_callback $host, sub {
515	$result{$host} = ...;	723	$result{$host} = ...;
…		…
530	loop, which serves two important purposes: first, it sets the callback	738	loop, which serves two important purposes: first, it sets the callback
531	to be called once the counter reaches C<0>, and second, it ensures that	739	to be called once the counter reaches C<0>, and second, it ensures that
532	C<send> is called even when C<no> hosts are being pinged (the loop	740	C<send> is called even when C<no> hosts are being pinged (the loop
533	doesn't execute once).	741	doesn't execute once).
534		742
535	This is the general pattern when you "fan out" into multiple subrequests:	743	This is the general pattern when you "fan out" into multiple (but
536	use an outer C<begin>/C<end> pair to set the callback and ensure C<end>	744	potentially none) subrequests: use an outer C<begin>/C<end> pair to set
537	is called at least once, and then, for each subrequest you start, call	745	the callback and ensure C<end> is called at least once, and then, for each
538	C<begin> and for each subrequest you finish, call C<end>.	746	subrequest you start, call C<begin> and for each subrequest you finish,
		747	call C<end>.
539		748
540	=back	749	=back
541		750
542	=head3 METHODS FOR CONSUMERS	751	=head3 METHODS FOR CONSUMERS
543		752
…		…
559	function will call C<croak>.	768	function will call C<croak>.
560		769
561	In list context, all parameters passed to C<send> will be returned,	770	In list context, all parameters passed to C<send> will be returned,
562	in scalar context only the first one will be returned.	771	in scalar context only the first one will be returned.
563		772
		773	Note that doing a blocking wait in a callback is not supported by any
		774	event loop, that is, recursive invocation of a blocking C<< ->recv
		775	>> is not allowed, and the C<recv> call will C<croak> if such a
		776	condition is detected. This condition can be slightly loosened by using
		777	L<Coro::AnyEvent>, which allows you to do a blocking C<< ->recv >> from
		778	any thread that doesn't run the event loop itself.
		779
564	Not all event models support a blocking wait - some die in that case	780	Not all event models support a blocking wait - some die in that case
565	(programs might want to do that to stay interactive), so I<if you are	781	(programs might want to do that to stay interactive), so I<if you are
566	using this from a module, never require a blocking wait>, but let the	782	using this from a module, never require a blocking wait>. Instead, let the
567	caller decide whether the call will block or not (for example, by coupling	783	caller decide whether the call will block or not (for example, by coupling
568	condition variables with some kind of request results and supporting	784	condition variables with some kind of request results and supporting
569	callbacks so the caller knows that getting the result will not block,	785	callbacks so the caller knows that getting the result will not block,
570	while still supporting blocking waits if the caller so desires).	786	while still supporting blocking waits if the caller so desires).
571		787
572	Another reason I<never> to C<< ->recv >> in a module is that you cannot
573	sensibly have two C<< ->recv >>'s in parallel, as that would require
574	multiple interpreters or coroutines/threads, none of which C<AnyEvent>
575	can supply.
576
577	The L<Coro> module, however, I<can> and I<does> supply coroutines and, in
578	fact, L<Coro::AnyEvent> replaces AnyEvent's condvars by coroutine-safe
579	versions and also integrates coroutines into AnyEvent, making blocking
580	C<< ->recv >> calls perfectly safe as long as they are done from another
581	coroutine (one that doesn't run the event loop).
582
583	You can ensure that C<< -recv >> never blocks by setting a callback and	788	You can ensure that C<< -recv >> never blocks by setting a callback and
584	only calling C<< ->recv >> from within that callback (or at a later	789	only calling C<< ->recv >> from within that callback (or at a later
585	time). This will work even when the event loop does not support blocking	790	time). This will work even when the event loop does not support blocking
586	waits otherwise.	791	waits otherwise.
587		792
588	=item $bool = $cv->ready	793	=item $bool = $cv->ready
589		794
590	Returns true when the condition is "true", i.e. whether C<send> or	795	Returns true when the condition is "true", i.e. whether C<send> or
591	C<croak> have been called.	796	C<croak> have been called.
592		797
593	=item $cb = $cv->cb ([new callback])	798	=item $cb = $cv->cb ($cb->($cv))
594		799
595	This is a mutator function that returns the callback set and optionally	800	This is a mutator function that returns the callback set and optionally
596	replaces it before doing so.	801	replaces it before doing so.
597		802
598	The callback will be called when the condition becomes "true", i.e. when	803	The callback will be called when the condition becomes (or already was)
599	C<send> or C<croak> are called, with the only argument being the condition	804	"true", i.e. when C<send> or C<croak> are called (or were called), with
600	variable itself. Calling C<recv> inside the callback or at any later time	805	the only argument being the condition variable itself. Calling C<recv>
601	is guaranteed not to block.	806	inside the callback or at any later time is guaranteed not to block.
602		807
603	=back	808	=back
604		809
		810	=head1 SUPPORTED EVENT LOOPS/BACKENDS
		811
		812	The available backend classes are (every class has its own manpage):
		813
		814	=over 4
		815
		816	=item Backends that are autoprobed when no other event loop can be found.
		817
		818	EV is the preferred backend when no other event loop seems to be in
		819	use. If EV is not installed, then AnyEvent will fall back to its own
		820	pure-perl implementation, which is available everywhere as it comes with
		821	AnyEvent itself.
		822
		823	AnyEvent::Impl::EV based on EV (interface to libev, best choice).
		824	AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
		825
		826	=item Backends that are transparently being picked up when they are used.
		827
		828	These will be used when they are currently loaded when the first watcher
		829	is created, in which case it is assumed that the application is using
		830	them. This means that AnyEvent will automatically pick the right backend
		831	when the main program loads an event module before anything starts to
		832	create watchers. Nothing special needs to be done by the main program.
		833
		834	AnyEvent::Impl::Event based on Event, very stable, few glitches.
		835	AnyEvent::Impl::Glib based on Glib, slow but very stable.
		836	AnyEvent::Impl::Tk based on Tk, very broken.
		837	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
		838	AnyEvent::Impl::POE based on POE, very slow, some limitations.
		839	AnyEvent::Impl::Irssi used when running within irssi.
		840
		841	=item Backends with special needs.
		842
		843	Qt requires the Qt::Application to be instantiated first, but will
		844	otherwise be picked up automatically. As long as the main program
		845	instantiates the application before any AnyEvent watchers are created,
		846	everything should just work.
		847
		848	AnyEvent::Impl::Qt based on Qt.
		849
		850	Support for IO::Async can only be partial, as it is too broken and
		851	architecturally limited to even support the AnyEvent API. It also
		852	is the only event loop that needs the loop to be set explicitly, so
		853	it can only be used by a main program knowing about AnyEvent. See
		854	L<AnyEvent::Impl::Async> for the gory details.
		855
		856	AnyEvent::Impl::IOAsync based on IO::Async, cannot be autoprobed.
		857
		858	=item Event loops that are indirectly supported via other backends.
		859
		860	Some event loops can be supported via other modules:
		861
		862	There is no direct support for WxWidgets (L<Wx>) or L<Prima>.
		863
		864	B<WxWidgets> has no support for watching file handles. However, you can
		865	use WxWidgets through the POE adaptor, as POE has a Wx backend that simply
		866	polls 20 times per second, which was considered to be too horrible to even
		867	consider for AnyEvent.
		868
		869	B<Prima> is not supported as nobody seems to be using it, but it has a POE
		870	backend, so it can be supported through POE.
		871
		872	AnyEvent knows about both L<Prima> and L<Wx>, however, and will try to
		873	load L<POE> when detecting them, in the hope that POE will pick them up,
		874	in which case everything will be automatic.
		875
		876	=back
		877
605	=head1 GLOBAL VARIABLES AND FUNCTIONS	878	=head1 GLOBAL VARIABLES AND FUNCTIONS
606		879
		880	These are not normally required to use AnyEvent, but can be useful to
		881	write AnyEvent extension modules.
		882
607	=over 4	883	=over 4
608		884
609	=item $AnyEvent::MODEL	885	=item $AnyEvent::MODEL
610		886
611	Contains C<undef> until the first watcher is being created. Then it	887	Contains C<undef> until the first watcher is being created, before the
		888	backend has been autodetected.
		889
612	contains the event model that is being used, which is the name of the	890	Afterwards it contains the event model that is being used, which is the
613	Perl class implementing the model. This class is usually one of the	891	name of the Perl class implementing the model. This class is usually one
614	C<AnyEvent::Impl:xxx> modules, but can be any other class in the case	892	of the C<AnyEvent::Impl:xxx> modules, but can be any other class in the
615	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).	893	case AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode> it
616		894	will be C<urxvt::anyevent>).
617	The known classes so far are:
618
619	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
620	AnyEvent::Impl::Event based on Event, second best choice.
621	AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
622	AnyEvent::Impl::Glib based on Glib, third-best choice.
623	AnyEvent::Impl::Tk based on Tk, very bad choice.
624	AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
625	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
626	AnyEvent::Impl::POE based on POE, not generic enough for full support.
627
628	There is no support for WxWidgets, as WxWidgets has no support for
629	watching file handles. However, you can use WxWidgets through the
630	POE Adaptor, as POE has a Wx backend that simply polls 20 times per
631	second, which was considered to be too horrible to even consider for
632	AnyEvent. Likewise, other POE backends can be used by AnyEvent by using
633	it's adaptor.
634
635	AnyEvent knows about L<Prima> and L<Wx> and will try to use L<POE> when
636	autodetecting them.
637		895
638	=item AnyEvent::detect	896	=item AnyEvent::detect
639		897
640	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model	898	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
641	if necessary. You should only call this function right before you would	899	if necessary. You should only call this function right before you would
642	have created an AnyEvent watcher anyway, that is, as late as possible at	900	have created an AnyEvent watcher anyway, that is, as late as possible at
643	runtime.	901	runtime, and not e.g. while initialising of your module.
		902
		903	If you need to do some initialisation before AnyEvent watchers are
		904	created, use C<post_detect>.
644		905
645	=item $guard = AnyEvent::post_detect { BLOCK }	906	=item $guard = AnyEvent::post_detect { BLOCK }
646		907
647	Arranges for the code block to be executed as soon as the event model is	908	Arranges for the code block to be executed as soon as the event model is
648	autodetected (or immediately if this has already happened).	909	autodetected (or immediately if this has already happened).
649		910
		911	The block will be executed I<after> the actual backend has been detected
		912	(C<$AnyEvent::MODEL> is set), but I<before> any watchers have been
		913	created, so it is possible to e.g. patch C<@AnyEvent::ISA> or do
		914	other initialisations - see the sources of L<AnyEvent::Strict> or
		915	L<AnyEvent::AIO> to see how this is used.
		916
		917	The most common usage is to create some global watchers, without forcing
		918	event module detection too early, for example, L<AnyEvent::AIO> creates
		919	and installs the global L<IO::AIO> watcher in a C<post_detect> block to
		920	avoid autodetecting the event module at load time.
		921
650	If called in scalar or list context, then it creates and returns an object	922	If called in scalar or list context, then it creates and returns an object
651	that automatically removes the callback again when it is destroyed. See	923	that automatically removes the callback again when it is destroyed (or
		924	C<undef> when the hook was immediately executed). See L<AnyEvent::AIO> for
652	L<Coro::BDB> for a case where this is useful.	925	a case where this is useful.
		926
		927	Example: Create a watcher for the IO::AIO module and store it in
		928	C<$WATCHER>. Only do so after the event loop is initialised, though.
		929
		930	our WATCHER;
		931
		932	my $guard = AnyEvent::post_detect {
		933	$WATCHER = AnyEvent->io (fh => IO::AIO::poll_fileno, poll => 'r', cb => \&IO::AIO::poll_cb);
		934	};
		935
		936	# the ||= is important in case post_detect immediately runs the block,
		937	# as to not clobber the newly-created watcher. assigning both watcher and
		938	# post_detect guard to the same variable has the advantage of users being
		939	# able to just C<undef $WATCHER> if the watcher causes them grief.
		940
		941	$WATCHER ||= $guard;
653		942
654	=item @AnyEvent::post_detect	943	=item @AnyEvent::post_detect
655		944
656	If there are any code references in this array (you can C<push> to it	945	If there are any code references in this array (you can C<push> to it
657	before or after loading AnyEvent), then they will called directly after	946	before or after loading AnyEvent), then they will called directly after
658	the event loop has been chosen.	947	the event loop has been chosen.
659		948
660	You should check C<$AnyEvent::MODEL> before adding to this array, though:	949	You should check C<$AnyEvent::MODEL> before adding to this array, though:
661	if it contains a true value then the event loop has already been detected,	950	if it is defined then the event loop has already been detected, and the
662	and the array will be ignored.	951	array will be ignored.
663		952
664	Best use C<AnyEvent::post_detect { BLOCK }> instead.	953	Best use C<AnyEvent::post_detect { BLOCK }> when your application allows
		954	it,as it takes care of these details.
		955
		956	This variable is mainly useful for modules that can do something useful
		957	when AnyEvent is used and thus want to know when it is initialised, but do
		958	not need to even load it by default. This array provides the means to hook
		959	into AnyEvent passively, without loading it.
665		960
666	=back	961	=back
667		962
668	=head1 WHAT TO DO IN A MODULE	963	=head1 WHAT TO DO IN A MODULE
669		964
…		…
724		1019
725		1020
726	=head1 OTHER MODULES	1021	=head1 OTHER MODULES
727		1022
728	The following is a non-exhaustive list of additional modules that use	1023	The following is a non-exhaustive list of additional modules that use
729	AnyEvent and can therefore be mixed easily with other AnyEvent modules	1024	AnyEvent as a client and can therefore be mixed easily with other AnyEvent
730	in the same program. Some of the modules come with AnyEvent, some are	1025	modules and other event loops in the same program. Some of the modules
731	available via CPAN.	1026	come with AnyEvent, most are available via CPAN.
732		1027
733	=over 4	1028	=over 4
734		1029
735	=item L<AnyEvent::Util>	1030	=item L<AnyEvent::Util>
736		1031
…		…
745		1040
746	=item L<AnyEvent::Handle>	1041	=item L<AnyEvent::Handle>
747		1042
748	Provide read and write buffers, manages watchers for reads and writes,	1043	Provide read and write buffers, manages watchers for reads and writes,
749	supports raw and formatted I/O, I/O queued and fully transparent and	1044	supports raw and formatted I/O, I/O queued and fully transparent and
750	non-blocking SSL/TLS.	1045	non-blocking SSL/TLS (via L<AnyEvent::TLS>.
751		1046
752	=item L<AnyEvent::DNS>	1047	=item L<AnyEvent::DNS>
753		1048
754	Provides rich asynchronous DNS resolver capabilities.	1049	Provides rich asynchronous DNS resolver capabilities.
755		1050
…		…
783		1078
784	=item L<AnyEvent::GPSD>	1079	=item L<AnyEvent::GPSD>
785		1080
786	A non-blocking interface to gpsd, a daemon delivering GPS information.	1081	A non-blocking interface to gpsd, a daemon delivering GPS information.
787		1082
		1083	=item L<AnyEvent::IRC>
		1084
		1085	AnyEvent based IRC client module family (replacing the older Net::IRC3).
		1086
		1087	=item L<AnyEvent::XMPP>
		1088
		1089	AnyEvent based XMPP (Jabber protocol) module family (replacing the older
		1090	Net::XMPP2>.
		1091
788	=item L<AnyEvent::IGS>	1092	=item L<AnyEvent::IGS>
789		1093
790	A non-blocking interface to the Internet Go Server protocol (used by	1094	A non-blocking interface to the Internet Go Server protocol (used by
791	L<App::IGS>).	1095	L<App::IGS>).
792		1096
793	=item L<Net::IRC3>
794
795	AnyEvent based IRC client module family.
796
797	=item L<Net::XMPP2>
798
799	AnyEvent based XMPP (Jabber protocol) module family.
800
801	=item L<Net::FCP>	1097	=item L<Net::FCP>
802		1098
803	AnyEvent-based implementation of the Freenet Client Protocol, birthplace	1099	AnyEvent-based implementation of the Freenet Client Protocol, birthplace
804	of AnyEvent.	1100	of AnyEvent.
805		1101
…		…
809		1105
810	=item L<Coro>	1106	=item L<Coro>
811		1107
812	Has special support for AnyEvent via L<Coro::AnyEvent>.	1108	Has special support for AnyEvent via L<Coro::AnyEvent>.
813		1109
814	=item L<IO::Lambda>
815
816	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
817
818	=back	1110	=back
819		1111
820	=cut	1112	=cut
821		1113
822	package AnyEvent;	1114	package AnyEvent;
823		1115
824	no warnings;	1116	# basically a tuned-down version of common::sense
825	use strict;	1117	sub common_sense {
		1118	# from common:.sense 1.0
		1119	${^WARNING_BITS} = "\xfc\x3f\xf3\x00\x0f\xf3\xcf\xc0\xf3\xfc\x33\x03";
		1120	# use strict vars subs
		1121	$^H |= 0x00000600;
		1122	}
826		1123
		1124	BEGIN { AnyEvent::common_sense }
		1125
827	use Carp;	1126	use Carp ();
828		1127
829	our $VERSION = 4.2;	1128	our $VERSION = '5.202';
830	our $MODEL;	1129	our $MODEL;
831		1130
832	our $AUTOLOAD;	1131	our $AUTOLOAD;
833	our @ISA;	1132	our @ISA;
834		1133
835	our @REGISTRY;	1134	our @REGISTRY;
836		1135
837	our $WIN32;	1136	our $WIN32;
838		1137
		1138	our $VERBOSE;
		1139
839	BEGIN {	1140	BEGIN {
840	my $win32 = ! ! ($^O =~ /mswin32/i);	1141	eval "sub WIN32(){ " . (($^O =~ /mswin32/i)*1) ." }";
841	eval "sub WIN32(){ $win32 }";	1142	eval "sub TAINT(){ " . (${^TAINT}*1) . " }";
842	}
843		1143
		1144	delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV}
		1145	if ${^TAINT};
		1146
844	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;	1147	$VERBOSE = $ENV{PERL_ANYEVENT_VERBOSE}*1;
		1148
		1149	}
		1150
		1151	our $MAX_SIGNAL_LATENCY = 10;
845		1152
846	our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred	1153	our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred
847		1154
848	{	1155	{
849	my $idx;	1156	my $idx;
…		…
851	for reverse split /\s*,\s*/,	1158	for reverse split /\s*,\s*/,
852	$ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";	1159	$ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";
853	}	1160	}
854		1161
855	my @models = (	1162	my @models = (
856	[EV:: => AnyEvent::Impl::EV::],	1163	[EV:: => AnyEvent::Impl::EV:: , 1],
857	[Event:: => AnyEvent::Impl::Event::],
858	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],	1164	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl:: , 1],
859	# everything below here will not be autoprobed	1165	# everything below here will not (normally) be autoprobed
860	# as the pureperl backend should work everywhere	1166	# as the pureperl backend should work everywhere
861	# and is usually faster	1167	# and is usually faster
		1168	[Event:: => AnyEvent::Impl::Event::, 1],
		1169	[Glib:: => AnyEvent::Impl::Glib:: , 1], # becomes extremely slow with many watchers
		1170	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
		1171	[Irssi:: => AnyEvent::Impl::Irssi::], # Irssi has a bogus "Event" package
862	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles	1172	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
863	[Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers
864	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
865	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program	1173	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program
866	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza	1174	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
867	[Wx:: => AnyEvent::Impl::POE::],	1175	[Wx:: => AnyEvent::Impl::POE::],
868	[Prima:: => AnyEvent::Impl::POE::],	1176	[Prima:: => AnyEvent::Impl::POE::],
		1177	# IO::Async is just too broken - we would need workarounds for its
		1178	# byzantine signal and broken child handling, among others.
		1179	# IO::Async is rather hard to detect, as it doesn't have any
		1180	# obvious default class.
		1181	[IO::Async:: => AnyEvent::Impl::IOAsync::], # requires special main program
		1182	[IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # requires special main program
		1183	[IO::Async::Notifier:: => AnyEvent::Impl::IOAsync::], # requires special main program
		1184	[AnyEvent::Impl::IOAsync:: => AnyEvent::Impl::IOAsync::], # requires special main program
869	);	1185	);
870		1186
871	our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY);	1187	our %method = map +($_ => 1),
		1188	qw(io timer time now now_update signal child idle condvar one_event DESTROY);
872		1189
873	our @post_detect;	1190	our @post_detect;
874		1191
875	sub post_detect(&) {	1192	sub post_detect(&) {
876	my ($cb) = @_;	1193	my ($cb) = @_;
877		1194
878	if ($MODEL) {	1195	if ($MODEL) {
879	$cb->();	1196	$cb->();
880		1197
881	1	1198	undef
882	} else {	1199	} else {
883	push @post_detect, $cb;	1200	push @post_detect, $cb;
884		1201
885	defined wantarray	1202	defined wantarray
886	? bless \$cb, "AnyEvent::Util::PostDetect"	1203	? bless \$cb, "AnyEvent::Util::postdetect"
887	: ()	1204	: ()
888	}	1205	}
889	}	1206	}
890		1207
891	sub AnyEvent::Util::PostDetect::DESTROY {	1208	sub AnyEvent::Util::postdetect::DESTROY {
892	@post_detect = grep $_ != ${$_[0]}, @post_detect;	1209	@post_detect = grep $_ != ${$_[0]}, @post_detect;
893	}	1210	}
894		1211
895	sub detect() {	1212	sub detect() {
896	unless ($MODEL) {	1213	unless ($MODEL) {
897	no strict 'refs';
898	local $SIG{__DIE__};	1214	local $SIG{__DIE__};
899		1215
900	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {	1216	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
901	my $model = "AnyEvent::Impl::$1";	1217	my $model = "AnyEvent::Impl::$1";
902	if (eval "require $model") {	1218	if (eval "require $model") {
903	$MODEL = $model;	1219	$MODEL = $model;
904	warn "AnyEvent: loaded model '$model' (forced by \$PERL_ANYEVENT_MODEL), using it.\n" if $verbose > 1;	1220	warn "AnyEvent: loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.\n" if $VERBOSE >= 2;
905	} else {	1221	} else {
906	warn "AnyEvent: unable to load model '$model' (from \$PERL_ANYEVENT_MODEL):\n$@" if $verbose;	1222	warn "AnyEvent: unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@" if $VERBOSE;
907	}	1223	}
908	}	1224	}
909		1225
910	# check for already loaded models	1226	# check for already loaded models
911	unless ($MODEL) {	1227	unless ($MODEL) {
912	for (@REGISTRY, @models) {	1228	for (@REGISTRY, @models) {
913	my ($package, $model) = @$_;	1229	my ($package, $model) = @$_;
914	if (${"$package\::VERSION"} > 0) {	1230	if (${"$package\::VERSION"} > 0) {
915	if (eval "require $model") {	1231	if (eval "require $model") {
916	$MODEL = $model;	1232	$MODEL = $model;
917	warn "AnyEvent: autodetected model '$model', using it.\n" if $verbose > 1;	1233	warn "AnyEvent: autodetected model '$model', using it.\n" if $VERBOSE >= 2;
918	last;	1234	last;
919	}	1235	}
920	}	1236	}
921	}	1237	}
922		1238
923	unless ($MODEL) {	1239	unless ($MODEL) {
924	# try to load a model	1240	# try to autoload a model
925
926	for (@REGISTRY, @models) {	1241	for (@REGISTRY, @models) {
927	my ($package, $model) = @$_;	1242	my ($package, $model, $autoload) = @$_;
		1243	if (
		1244	$autoload
928	if (eval "require $package"	1245	and eval "require $package"
929	and ${"$package\::VERSION"} > 0	1246	and ${"$package\::VERSION"} > 0
930	and eval "require $model") {	1247	and eval "require $model"
		1248	) {
931	$MODEL = $model;	1249	$MODEL = $model;
932	warn "AnyEvent: autoprobed model '$model', using it.\n" if $verbose > 1;	1250	warn "AnyEvent: autoloaded model '$model', using it.\n" if $VERBOSE >= 2;
933	last;	1251	last;
934	}	1252	}
935	}	1253	}
936		1254
937	$MODEL	1255	$MODEL
938	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";	1256	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.\n";
939	}	1257	}
940	}	1258	}
941		1259
		1260	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
		1261
942	unshift @ISA, $MODEL;	1262	unshift @ISA, $MODEL;
943	push @{"$MODEL\::ISA"}, "AnyEvent::Base";	1263
		1264	require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
944		1265
945	(shift @post_detect)->() while @post_detect;	1266	(shift @post_detect)->() while @post_detect;
946	}	1267	}
947		1268
948	$MODEL	1269	$MODEL
…		…
950		1271
951	sub AUTOLOAD {	1272	sub AUTOLOAD {
952	(my $func = $AUTOLOAD) =~ s/.*://;	1273	(my $func = $AUTOLOAD) =~ s/.*://;
953		1274
954	$method{$func}	1275	$method{$func}
955	or croak "$func: not a valid method for AnyEvent objects";	1276	or Carp::croak "$func: not a valid method for AnyEvent objects";
956		1277
957	detect unless $MODEL;	1278	detect unless $MODEL;
958		1279
959	my $class = shift;	1280	my $class = shift;
960	$class->$func (@_);	1281	$class->$func (@_);
961	}	1282	}
962		1283
		1284	# utility function to dup a filehandle. this is used by many backends
		1285	# to support binding more than one watcher per filehandle (they usually
		1286	# allow only one watcher per fd, so we dup it to get a different one).
		1287	sub _dupfh($$;$$) {
		1288	my ($poll, $fh, $r, $w) = @_;
		1289
		1290	# cygwin requires the fh mode to be matching, unix doesn't
		1291	my ($rw, $mode) = $poll eq "r" ? ($r, "<&") : ($w, ">&");
		1292
		1293	open my $fh2, $mode, $fh
		1294	or die "AnyEvent->io: cannot dup() filehandle in mode '$poll': $!,";
		1295
		1296	# we assume CLOEXEC is already set by perl in all important cases
		1297
		1298	($fh2, $rw)
		1299	}
		1300
		1301	=head1 SIMPLIFIED AE API
		1302
		1303	Starting with version 5.0, AnyEvent officially supports a second, much
		1304	simpler, API that is designed to reduce the calling, typing and memory
		1305	overhead.
		1306
		1307	See the L<AE> manpage for details.
		1308
		1309	=cut
		1310
		1311	package AE;
		1312
		1313	our $VERSION = $AnyEvent::VERSION;
		1314
		1315	sub io($$$) {
		1316	AnyEvent->io (fh => $_[0], poll => $_[1] ? "w" : "r", cb => $_[2])
		1317	}
		1318
		1319	sub timer($$$) {
		1320	AnyEvent->timer (after => $_[0], interval => $_[1], cb => $_[2])
		1321	}
		1322
		1323	sub signal($$) {
		1324	AnyEvent->signal (signal => $_[0], cb => $_[1])
		1325	}
		1326
		1327	sub child($$) {
		1328	AnyEvent->child (pid => $_[0], cb => $_[1])
		1329	}
		1330
		1331	sub idle($) {
		1332	AnyEvent->idle (cb => $_[0])
		1333	}
		1334
		1335	sub cv(;&) {
		1336	AnyEvent->condvar (@_ ? (cb => $_[0]) : ())
		1337	}
		1338
		1339	sub now() {
		1340	AnyEvent->now
		1341	}
		1342
		1343	sub now_update() {
		1344	AnyEvent->now_update
		1345	}
		1346
		1347	sub time() {
		1348	AnyEvent->time
		1349	}
		1350
963	package AnyEvent::Base;	1351	package AnyEvent::Base;
964		1352
965	# default implementation for now and time	1353	# default implementations for many methods
966		1354
967	use Time::HiRes ();	1355	sub _time() {
		1356	# probe for availability of Time::HiRes
		1357	if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {
		1358	warn "AnyEvent: using Time::HiRes for sub-second timing accuracy.\n" if $VERBOSE >= 8;
		1359	*_time = \&Time::HiRes::time;
		1360	# if (eval "use POSIX (); (POSIX::times())...
		1361	} else {
		1362	warn "AnyEvent: using built-in time(), WARNING, no sub-second resolution!\n" if $VERBOSE;
		1363	*_time = sub { time }; # epic fail
		1364	}
968		1365
969	sub time { Time::HiRes::time }	1366	&_time
970	sub now { Time::HiRes::time }	1367	}
		1368
		1369	sub time { _time }
		1370	sub now { _time }
		1371	sub now_update { }
971		1372
972	# default implementation for ->condvar	1373	# default implementation for ->condvar
973		1374
974	sub condvar {	1375	sub condvar {
975	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::	1376	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar"
976	}	1377	}
977		1378
978	# default implementation for ->signal	1379	# default implementation for ->signal
979		1380
980	our %SIG_CB;	1381	our $HAVE_ASYNC_INTERRUPT;
		1382
		1383	sub _have_async_interrupt() {
		1384	$HAVE_ASYNC_INTERRUPT = 1*(!$ENV{PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT}
		1385	&& eval "use Async::Interrupt 1.02 (); 1")
		1386	unless defined $HAVE_ASYNC_INTERRUPT;
		1387
		1388	$HAVE_ASYNC_INTERRUPT
		1389	}
		1390
		1391	our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO);
		1392	our (%SIG_ASY, %SIG_ASY_W);
		1393	our ($SIG_COUNT, $SIG_TW);
		1394
		1395	sub _signal_exec {
		1396	$HAVE_ASYNC_INTERRUPT
		1397	? $SIGPIPE_R->drain
		1398	: sysread $SIGPIPE_R, (my $dummy), 9;
		1399
		1400	while (%SIG_EV) {
		1401	for (keys %SIG_EV) {
		1402	delete $SIG_EV{$_};
		1403	$_->() for values %{ $SIG_CB{$_} || {} };
		1404	}
		1405	}
		1406	}
		1407
		1408	# install a dummy wakeup watcher to reduce signal catching latency
		1409	sub _sig_add() {
		1410	unless ($SIG_COUNT++) {
		1411	# try to align timer on a full-second boundary, if possible
		1412	my $NOW = AE::now;
		1413
		1414	$SIG_TW = AE::timer
		1415	$MAX_SIGNAL_LATENCY - ($NOW - int $NOW),
		1416	$MAX_SIGNAL_LATENCY,
		1417	sub { } # just for the PERL_ASYNC_CHECK
		1418	;
		1419	}
		1420	}
		1421
		1422	sub _sig_del {
		1423	undef $SIG_TW
		1424	unless --$SIG_COUNT;
		1425	}
		1426
		1427	our $_sig_name_init; $_sig_name_init = sub {
		1428	eval q{ # poor man's autoloading
		1429	undef $_sig_name_init;
		1430
		1431	if (_have_async_interrupt) {
		1432	*sig2num = \&Async::Interrupt::sig2num;
		1433	*sig2name = \&Async::Interrupt::sig2name;
		1434	} else {
		1435	require Config;
		1436
		1437	my %signame2num;
		1438	@signame2num{ split ' ', $Config::Config{sig_name} }
		1439	= split ' ', $Config::Config{sig_num};
		1440
		1441	my @signum2name;
		1442	@signum2name[values %signame2num] = keys %signame2num;
		1443
		1444	*sig2num = sub($) {
		1445	$_[0] > 0 ? shift : $signame2num{+shift}
		1446	};
		1447	*sig2name = sub ($) {
		1448	$_[0] > 0 ? $signum2name[+shift] : shift
		1449	};
		1450	}
		1451	};
		1452	die if $@;
		1453	};
		1454
		1455	sub sig2num ($) { &$_sig_name_init; &sig2num }
		1456	sub sig2name($) { &$_sig_name_init; &sig2name }
981		1457
982	sub signal {	1458	sub signal {
		1459	eval q{ # poor man's autoloading {}
		1460	# probe for availability of Async::Interrupt
		1461	if (_have_async_interrupt) {
		1462	warn "AnyEvent: using Async::Interrupt for race-free signal handling.\n" if $VERBOSE >= 8;
		1463
		1464	$SIGPIPE_R = new Async::Interrupt::EventPipe;
		1465	$SIG_IO = AE::io $SIGPIPE_R->fileno, 0, \&_signal_exec;
		1466
		1467	} else {
		1468	warn "AnyEvent: using emulated perl signal handling with latency timer.\n" if $VERBOSE >= 8;
		1469
		1470	require Fcntl;
		1471
		1472	if (AnyEvent::WIN32) {
		1473	require AnyEvent::Util;
		1474
		1475	($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
		1476	AnyEvent::Util::fh_nonblocking ($SIGPIPE_R, 1) if $SIGPIPE_R;
		1477	AnyEvent::Util::fh_nonblocking ($SIGPIPE_W, 1) if $SIGPIPE_W; # just in case
		1478	} else {
		1479	pipe $SIGPIPE_R, $SIGPIPE_W;
		1480	fcntl $SIGPIPE_R, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_R;
		1481	fcntl $SIGPIPE_W, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_W; # just in case
		1482
		1483	# not strictly required, as $^F is normally 2, but let's make sure...
		1484	fcntl $SIGPIPE_R, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC;
		1485	fcntl $SIGPIPE_W, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC;
		1486	}
		1487
		1488	$SIGPIPE_R
		1489	or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n";
		1490
		1491	$SIG_IO = AE::io $SIGPIPE_R, 0, \&_signal_exec;
		1492	}
		1493
		1494	*signal = sub {
983	my (undef, %arg) = @_;	1495	my (undef, %arg) = @_;
984		1496
985	my $signal = uc $arg{signal}	1497	my $signal = uc $arg{signal}
986	or Carp::croak "required option 'signal' is missing";	1498	or Carp::croak "required option 'signal' is missing";
987		1499
		1500	if ($HAVE_ASYNC_INTERRUPT) {
		1501	# async::interrupt
		1502
		1503	$signal = sig2num $signal;
988	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};	1504	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};
		1505
		1506	$SIG_ASY{$signal} ||= new Async::Interrupt
		1507	cb => sub { undef $SIG_EV{$signal} },
		1508	signal => $signal,
		1509	pipe => [$SIGPIPE_R->filenos],
		1510	pipe_autodrain => 0,
		1511	;
		1512
		1513	} else {
		1514	# pure perl
		1515
		1516	# AE::Util has been loaded in signal
		1517	$signal = sig2name $signal;
		1518	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};
		1519
989	$SIG{$signal} ||= sub {	1520	$SIG{$signal} ||= sub {
990	$_->() for values %{ $SIG_CB{$signal} || {} };	1521	local $!;
		1522	syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV;
		1523	undef $SIG_EV{$signal};
		1524	};
		1525
		1526	# can't do signal processing without introducing races in pure perl,
		1527	# so limit the signal latency.
		1528	_sig_add;
		1529	}
		1530
		1531	bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
		1532	};
		1533
		1534	*AnyEvent::Base::signal::DESTROY = sub {
		1535	my ($signal, $cb) = @{$_[0]};
		1536
		1537	_sig_del;
		1538
		1539	delete $SIG_CB{$signal}{$cb};
		1540
		1541	$HAVE_ASYNC_INTERRUPT
		1542	? delete $SIG_ASY{$signal}
		1543	: # delete doesn't work with older perls - they then
		1544	# print weird messages, or just unconditionally exit
		1545	# instead of getting the default action.
		1546	undef $SIG{$signal}
		1547	unless keys %{ $SIG_CB{$signal} };
		1548	};
991	};	1549	};
992		1550	die if $@;
993	bless [$signal, $arg{cb}], "AnyEvent::Base::Signal"	1551	&signal
994	}
995
996	sub AnyEvent::Base::Signal::DESTROY {
997	my ($signal, $cb) = @{$_[0]};
998
999	delete $SIG_CB{$signal}{$cb};
1000
1001	delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
1002	}	1552	}
1003		1553
1004	# default implementation for ->child	1554	# default implementation for ->child
1005		1555
1006	our %PID_CB;	1556	our %PID_CB;
1007	our $CHLD_W;	1557	our $CHLD_W;
1008	our $CHLD_DELAY_W;	1558	our $CHLD_DELAY_W;
1009	our $PID_IDLE;
1010	our $WNOHANG;	1559	our $WNOHANG;
1011		1560
1012	sub _child_wait {	1561	sub _emit_childstatus($$) {
1013	while (0 < (my $pid = waitpid -1, $WNOHANG)) {	1562	my (undef, $rpid, $rstatus) = @_;
		1563
		1564	$_->($rpid, $rstatus)
1014	$_->($pid, $?) for (values %{ $PID_CB{$pid} || {} }),	1565	for values %{ $PID_CB{$rpid} || {} },
1015	(values %{ $PID_CB{0} || {} });	1566	values %{ $PID_CB{0} || {} };
1016	}
1017
1018	undef $PID_IDLE;
1019	}	1567	}
1020		1568
1021	sub _sigchld {	1569	sub _sigchld {
1022	# make sure we deliver these changes "synchronous" with the event loop.	1570	my $pid;
1023	$CHLD_DELAY_W ||= AnyEvent->timer (after => 0, cb => sub {	1571
1024	undef $CHLD_DELAY_W;	1572	AnyEvent->_emit_childstatus ($pid, $?)
1025	&_child_wait;	1573	while ($pid = waitpid -1, $WNOHANG) > 0;
1026	});
1027	}	1574	}
1028		1575
1029	sub child {	1576	sub child {
1030	my (undef, %arg) = @_;	1577	my (undef, %arg) = @_;
1031		1578
1032	defined (my $pid = $arg{pid} + 0)	1579	defined (my $pid = $arg{pid} + 0)
1033	or Carp::croak "required option 'pid' is missing";	1580	or Carp::croak "required option 'pid' is missing";
1034		1581
1035	$PID_CB{$pid}{$arg{cb}} = $arg{cb};	1582	$PID_CB{$pid}{$arg{cb}} = $arg{cb};
1036		1583
1037	unless ($WNOHANG) {	1584	# WNOHANG is almost cetrainly 1 everywhere
		1585	$WNOHANG ||= $^O =~ /^(?:openbsd|netbsd|linux|freebsd|cygwin|MSWin32)$/
		1586	? 1
1038	$WNOHANG = eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;	1587	: eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;
1039	}
1040		1588
1041	unless ($CHLD_W) {	1589	unless ($CHLD_W) {
1042	$CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);	1590	$CHLD_W = AE::signal CHLD => \&_sigchld;
1043	# child could be a zombie already, so make at least one round	1591	# child could be a zombie already, so make at least one round
1044	&_sigchld;	1592	&_sigchld;
1045	}	1593	}
1046		1594
1047	bless [$pid, $arg{cb}], "AnyEvent::Base::Child"	1595	bless [$pid, $arg{cb}], "AnyEvent::Base::child"
1048	}	1596	}
1049		1597
1050	sub AnyEvent::Base::Child::DESTROY {	1598	sub AnyEvent::Base::child::DESTROY {
1051	my ($pid, $cb) = @{$_[0]};	1599	my ($pid, $cb) = @{$_[0]};
1052		1600
1053	delete $PID_CB{$pid}{$cb};	1601	delete $PID_CB{$pid}{$cb};
1054	delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };	1602	delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
1055		1603
1056	undef $CHLD_W unless keys %PID_CB;	1604	undef $CHLD_W unless keys %PID_CB;
1057	}	1605	}
1058		1606
		1607	# idle emulation is done by simply using a timer, regardless
		1608	# of whether the process is idle or not, and not letting
		1609	# the callback use more than 50% of the time.
		1610	sub idle {
		1611	my (undef, %arg) = @_;
		1612
		1613	my ($cb, $w, $rcb) = $arg{cb};
		1614
		1615	$rcb = sub {
		1616	if ($cb) {
		1617	$w = _time;
		1618	&$cb;
		1619	$w = _time - $w;
		1620
		1621	# never use more then 50% of the time for the idle watcher,
		1622	# within some limits
		1623	$w = 0.0001 if $w < 0.0001;
		1624	$w = 5 if $w > 5;
		1625
		1626	$w = AE::timer $w, 0, $rcb;
		1627	} else {
		1628	# clean up...
		1629	undef $w;
		1630	undef $rcb;
		1631	}
		1632	};
		1633
		1634	$w = AE::timer 0.05, 0, $rcb;
		1635
		1636	bless \\$cb, "AnyEvent::Base::idle"
		1637	}
		1638
		1639	sub AnyEvent::Base::idle::DESTROY {
		1640	undef $${$_[0]};
		1641	}
		1642
1059	package AnyEvent::CondVar;	1643	package AnyEvent::CondVar;
1060		1644
1061	our @ISA = AnyEvent::CondVar::Base::;	1645	our @ISA = AnyEvent::CondVar::Base::;
1062		1646
1063	package AnyEvent::CondVar::Base;	1647	package AnyEvent::CondVar::Base;
1064		1648
1065	use overload	1649	#use overload
1066	'&{}' => sub { my $self = shift; sub { $self->send (@_) } },	1650	# '&{}' => sub { my $self = shift; sub { $self->send (@_) } },
1067	fallback => 1;	1651	# fallback => 1;
		1652
		1653	# save 300+ kilobytes by dirtily hardcoding overloading
		1654	${"AnyEvent::CondVar::Base::OVERLOAD"}{dummy}++; # Register with magic by touching.
		1655	*{'AnyEvent::CondVar::Base::()'} = sub { }; # "Make it findable via fetchmethod."
		1656	*{'AnyEvent::CondVar::Base::(&{}'} = sub { my $self = shift; sub { $self->send (@_) } }; # &{}
		1657	${'AnyEvent::CondVar::Base::()'} = 1; # fallback
		1658
		1659	our $WAITING;
1068		1660
1069	sub _send {	1661	sub _send {
1070	# nop	1662	# nop
1071	}	1663	}
1072		1664
…		…
1085	sub ready {	1677	sub ready {
1086	$_[0]{_ae_sent}	1678	$_[0]{_ae_sent}
1087	}	1679	}
1088		1680
1089	sub _wait {	1681	sub _wait {
		1682	$WAITING
		1683	and !$_[0]{_ae_sent}
		1684	and Carp::croak "AnyEvent::CondVar: recursive blocking wait detected";
		1685
		1686	local $WAITING = 1;
1090	AnyEvent->one_event while !$_[0]{_ae_sent};	1687	AnyEvent->one_event while !$_[0]{_ae_sent};
1091	}	1688	}
1092		1689
1093	sub recv {	1690	sub recv {
1094	$_[0]->_wait;	1691	$_[0]->_wait;
…		…
1096	Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak};	1693	Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak};
1097	wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0]	1694	wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0]
1098	}	1695	}
1099		1696
1100	sub cb {	1697	sub cb {
1101	$_[0]{_ae_cb} = $_[1] if @_ > 1;	1698	my $cv = shift;
		1699
		1700	@_
		1701	and $cv->{_ae_cb} = shift
		1702	and $cv->{_ae_sent}
		1703	and (delete $cv->{_ae_cb})->($cv);
		1704
1102	$_[0]{_ae_cb}	1705	$cv->{_ae_cb}
1103	}	1706	}
1104		1707
1105	sub begin {	1708	sub begin {
1106	++$_[0]{_ae_counter};	1709	++$_[0]{_ae_counter};
1107	$_[0]{_ae_end_cb} = $_[1] if @_ > 1;	1710	$_[0]{_ae_end_cb} = $_[1] if @_ > 1;
…		…
1113	}	1716	}
1114		1717
1115	# undocumented/compatibility with pre-3.4	1718	# undocumented/compatibility with pre-3.4
1116	*broadcast = \&send;	1719	*broadcast = \&send;
1117	*wait = \&_wait;	1720	*wait = \&_wait;
		1721
		1722	=head1 ERROR AND EXCEPTION HANDLING
		1723
		1724	In general, AnyEvent does not do any error handling - it relies on the
		1725	caller to do that if required. The L<AnyEvent::Strict> module (see also
		1726	the C<PERL_ANYEVENT_STRICT> environment variable, below) provides strict
		1727	checking of all AnyEvent methods, however, which is highly useful during
		1728	development.
		1729
		1730	As for exception handling (i.e. runtime errors and exceptions thrown while
		1731	executing a callback), this is not only highly event-loop specific, but
		1732	also not in any way wrapped by this module, as this is the job of the main
		1733	program.
		1734
		1735	The pure perl event loop simply re-throws the exception (usually
		1736	within C<< condvar->recv >>), the L<Event> and L<EV> modules call C<<
		1737	$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and
		1738	so on.
		1739
		1740	=head1 ENVIRONMENT VARIABLES
		1741
		1742	The following environment variables are used by this module or its
		1743	submodules.
		1744
		1745	Note that AnyEvent will remove I<all> environment variables starting with
		1746	C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
		1747	enabled.
		1748
		1749	=over 4
		1750
		1751	=item C<PERL_ANYEVENT_VERBOSE>
		1752
		1753	By default, AnyEvent will be completely silent except in fatal
		1754	conditions. You can set this environment variable to make AnyEvent more
		1755	talkative.
		1756
		1757	When set to C<1> or higher, causes AnyEvent to warn about unexpected
		1758	conditions, such as not being able to load the event model specified by
		1759	C<PERL_ANYEVENT_MODEL>.
		1760
		1761	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
		1762	model it chooses.
		1763
		1764	When set to C<8> or higher, then AnyEvent will report extra information on
		1765	which optional modules it loads and how it implements certain features.
		1766
		1767	=item C<PERL_ANYEVENT_STRICT>
		1768
		1769	AnyEvent does not do much argument checking by default, as thorough
		1770	argument checking is very costly. Setting this variable to a true value
		1771	will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
		1772	check the arguments passed to most method calls. If it finds any problems,
		1773	it will croak.
		1774
		1775	In other words, enables "strict" mode.
		1776
		1777	Unlike C<use strict> (or it's modern cousin, C<< use L<common::sense>
		1778	>>, it is definitely recommended to keep it off in production. Keeping
		1779	C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs
		1780	can be very useful, however.
		1781
		1782	=item C<PERL_ANYEVENT_MODEL>
		1783
		1784	This can be used to specify the event model to be used by AnyEvent, before
		1785	auto detection and -probing kicks in. It must be a string consisting
		1786	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
		1787	and the resulting module name is loaded and if the load was successful,
		1788	used as event model. If it fails to load AnyEvent will proceed with
		1789	auto detection and -probing.
		1790
		1791	This functionality might change in future versions.
		1792
		1793	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
		1794	could start your program like this:
		1795
		1796	PERL_ANYEVENT_MODEL=Perl perl ...
		1797
		1798	=item C<PERL_ANYEVENT_PROTOCOLS>
		1799
		1800	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
		1801	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
		1802	of auto probing).
		1803
		1804	Must be set to a comma-separated list of protocols or address families,
		1805	current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
		1806	used, and preference will be given to protocols mentioned earlier in the
		1807	list.
		1808
		1809	This variable can effectively be used for denial-of-service attacks
		1810	against local programs (e.g. when setuid), although the impact is likely
		1811	small, as the program has to handle conenction and other failures anyways.
		1812
		1813	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
		1814	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
		1815	- only support IPv4, never try to resolve or contact IPv6
		1816	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
		1817	IPv6, but prefer IPv6 over IPv4.
		1818
		1819	=item C<PERL_ANYEVENT_EDNS0>
		1820
		1821	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
		1822	for DNS. This extension is generally useful to reduce DNS traffic, but
		1823	some (broken) firewalls drop such DNS packets, which is why it is off by
		1824	default.
		1825
		1826	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
		1827	EDNS0 in its DNS requests.
		1828
		1829	=item C<PERL_ANYEVENT_MAX_FORKS>
		1830
		1831	The maximum number of child processes that C<AnyEvent::Util::fork_call>
		1832	will create in parallel.
		1833
		1834	=item C<PERL_ANYEVENT_MAX_OUTSTANDING_DNS>
		1835
		1836	The default value for the C<max_outstanding> parameter for the default DNS
		1837	resolver - this is the maximum number of parallel DNS requests that are
		1838	sent to the DNS server.
		1839
		1840	=item C<PERL_ANYEVENT_RESOLV_CONF>
		1841
		1842	The file to use instead of F</etc/resolv.conf> (or OS-specific
		1843	configuration) in the default resolver. When set to the empty string, no
		1844	default config will be used.
		1845
		1846	=item C<PERL_ANYEVENT_CA_FILE>, C<PERL_ANYEVENT_CA_PATH>.
		1847
		1848	When neither C<ca_file> nor C<ca_path> was specified during
		1849	L<AnyEvent::TLS> context creation, and either of these environment
		1850	variables exist, they will be used to specify CA certificate locations
		1851	instead of a system-dependent default.
		1852
		1853	=item C<PERL_ANYEVENT_AVOID_GUARD> and C<PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT>
		1854
		1855	When these are set to C<1>, then the respective modules are not
		1856	loaded. Mostly good for testing AnyEvent itself.
		1857
		1858	=back
1118		1859
1119	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE	1860	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
1120		1861
1121	This is an advanced topic that you do not normally need to use AnyEvent in	1862	This is an advanced topic that you do not normally need to use AnyEvent in
1122	a module. This section is only of use to event loop authors who want to	1863	a module. This section is only of use to event loop authors who want to
…		…
1156		1897
1157	I<rxvt-unicode> also cheats a bit by not providing blocking access to	1898	I<rxvt-unicode> also cheats a bit by not providing blocking access to
1158	condition variables: code blocking while waiting for a condition will	1899	condition variables: code blocking while waiting for a condition will
1159	C<die>. This still works with most modules/usages, and blocking calls must	1900	C<die>. This still works with most modules/usages, and blocking calls must
1160	not be done in an interactive application, so it makes sense.	1901	not be done in an interactive application, so it makes sense.
1161
1162	=head1 ENVIRONMENT VARIABLES
1163
1164	The following environment variables are used by this module:
1165
1166	=over 4
1167
1168	=item C<PERL_ANYEVENT_VERBOSE>
1169
1170	By default, AnyEvent will be completely silent except in fatal
1171	conditions. You can set this environment variable to make AnyEvent more
1172	talkative.
1173
1174	When set to C<1> or higher, causes AnyEvent to warn about unexpected
1175	conditions, such as not being able to load the event model specified by
1176	C<PERL_ANYEVENT_MODEL>.
1177
1178	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1179	model it chooses.
1180
1181	=item C<PERL_ANYEVENT_MODEL>
1182
1183	This can be used to specify the event model to be used by AnyEvent, before
1184	auto detection and -probing kicks in. It must be a string consisting
1185	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
1186	and the resulting module name is loaded and if the load was successful,
1187	used as event model. If it fails to load AnyEvent will proceed with
1188	auto detection and -probing.
1189
1190	This functionality might change in future versions.
1191
1192	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1193	could start your program like this:
1194
1195	PERL_ANYEVENT_MODEL=Perl perl ...
1196
1197	=item C<PERL_ANYEVENT_PROTOCOLS>
1198
1199	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1200	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
1201	of auto probing).
1202
1203	Must be set to a comma-separated list of protocols or address families,
1204	current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
1205	used, and preference will be given to protocols mentioned earlier in the
1206	list.
1207
1208	This variable can effectively be used for denial-of-service attacks
1209	against local programs (e.g. when setuid), although the impact is likely
1210	small, as the program has to handle connection errors already-
1211
1212	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1213	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1214	- only support IPv4, never try to resolve or contact IPv6
1215	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1216	IPv6, but prefer IPv6 over IPv4.
1217
1218	=item C<PERL_ANYEVENT_EDNS0>
1219
1220	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
1221	for DNS. This extension is generally useful to reduce DNS traffic, but
1222	some (broken) firewalls drop such DNS packets, which is why it is off by
1223	default.
1224
1225	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1226	EDNS0 in its DNS requests.
1227
1228	=item C<PERL_ANYEVENT_MAX_FORKS>
1229
1230	The maximum number of child processes that C<AnyEvent::Util::fork_call>
1231	will create in parallel.
1232
1233	=back
1234		1902
1235	=head1 EXAMPLE PROGRAM	1903	=head1 EXAMPLE PROGRAM
1236		1904
1237	The following program uses an I/O watcher to read data from STDIN, a timer	1905	The following program uses an I/O watcher to read data from STDIN, a timer
1238	to display a message once per second, and a condition variable to quit the	1906	to display a message once per second, and a condition variable to quit the
…		…
1251	warn "read: $input\n"; # output what has been read	1919	warn "read: $input\n"; # output what has been read
1252	$cv->send if $input =~ /^q/i; # quit program if /^q/i	1920	$cv->send if $input =~ /^q/i; # quit program if /^q/i
1253	},	1921	},
1254	);	1922	);
1255		1923
1256	my $time_watcher; # can only be used once
1257
1258	sub new_timer {
1259	$timer = AnyEvent->timer (after => 1, cb => sub {	1924	my $time_watcher = AnyEvent->timer (after => 1, interval => 1, cb => sub {
1260	warn "timeout\n"; # print 'timeout' about every second	1925	warn "timeout\n"; # print 'timeout' at most every second
1261	&new_timer; # and restart the time
1262	});	1926	});
1263	}
1264
1265	new_timer; # create first timer
1266		1927
1267	$cv->recv; # wait until user enters /^q/i	1928	$cv->recv; # wait until user enters /^q/i
1268		1929
1269	=head1 REAL-WORLD EXAMPLE	1930	=head1 REAL-WORLD EXAMPLE
1270		1931
…		…
1401	through AnyEvent. The benchmark creates a lot of timers (with a zero	2062	through AnyEvent. The benchmark creates a lot of timers (with a zero
1402	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,	2063	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,
1403	which it is), lets them fire exactly once and destroys them again.	2064	which it is), lets them fire exactly once and destroys them again.
1404		2065
1405	Source code for this benchmark is found as F<eg/bench> in the AnyEvent	2066	Source code for this benchmark is found as F<eg/bench> in the AnyEvent
1406	distribution.	2067	distribution. It uses the L<AE> interface, which makes a real difference
		2068	for the EV and Perl backends only.
1407		2069
1408	=head3 Explanation of the columns	2070	=head3 Explanation of the columns
1409		2071
1410	I<watcher> is the number of event watchers created/destroyed. Since	2072	I<watcher> is the number of event watchers created/destroyed. Since
1411	different event models feature vastly different performances, each event	2073	different event models feature vastly different performances, each event
…		…
1432	watcher.	2094	watcher.
1433		2095
1434	=head3 Results	2096	=head3 Results
1435		2097
1436	name watchers bytes create invoke destroy comment	2098	name watchers bytes create invoke destroy comment
1437	EV/EV 400000 244 0.56 0.46 0.31 EV native interface	2099	EV/EV 100000 223 0.47 0.43 0.27 EV native interface
1438	EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers	2100	EV/Any 100000 223 0.48 0.42 0.26 EV + AnyEvent watchers
1439	CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal	2101	Coro::EV/Any 100000 223 0.47 0.42 0.26 coroutines + Coro::Signal
1440	Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation	2102	Perl/Any 100000 431 2.70 0.74 0.92 pure perl implementation
1441	Event/Event 16000 516 31.88 31.30 0.85 Event native interface	2103	Event/Event 16000 516 31.16 31.84 0.82 Event native interface
1442	Event/Any 16000 590 35.75 31.42 1.08 Event + AnyEvent watchers	2104	Event/Any 16000 1203 42.61 34.79 1.80 Event + AnyEvent watchers
		2105	IOAsync/Any 16000 1911 41.92 27.45 16.81 via IO::Async::Loop::IO_Poll
		2106	IOAsync/Any 16000 1726 40.69 26.37 15.25 via IO::Async::Loop::Epoll
1443	Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour	2107	Glib/Any 16000 1118 89.00 12.57 51.17 quadratic behaviour
1444	Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers	2108	Tk/Any 2000 1346 20.96 10.75 8.00 SEGV with >> 2000 watchers
1445	POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event	2109	POE/Any 2000 6951 108.97 795.32 14.24 via POE::Loop::Event
1446	POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select	2110	POE/Any 2000 6648 94.79 774.40 575.51 via POE::Loop::Select
1447		2111
1448	=head3 Discussion	2112	=head3 Discussion
1449		2113
1450	The benchmark does I<not> measure scalability of the event loop very	2114	The benchmark does I<not> measure scalability of the event loop very
1451	well. For example, a select-based event loop (such as the pure perl one)	2115	well. For example, a select-based event loop (such as the pure perl one)
…		…
1463	benchmark machine, handling an event takes roughly 1600 CPU cycles with	2127	benchmark machine, handling an event takes roughly 1600 CPU cycles with
1464	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU	2128	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU
1465	cycles with POE.	2129	cycles with POE.
1466		2130
1467	C<EV> is the sole leader regarding speed and memory use, which are both	2131	C<EV> is the sole leader regarding speed and memory use, which are both
1468	maximal/minimal, respectively. Even when going through AnyEvent, it uses	2132	maximal/minimal, respectively. When using the L<AE> API there is zero
		2133	overhead (when going through the AnyEvent API create is about 5-6 times
		2134	slower, with other times being equal, so still uses far less memory than
1469	far less memory than any other event loop and is still faster than Event	2135	any other event loop and is still faster than Event natively).
1470	natively.
1471		2136
1472	The pure perl implementation is hit in a few sweet spots (both the	2137	The pure perl implementation is hit in a few sweet spots (both the
1473	constant timeout and the use of a single fd hit optimisations in the perl	2138	constant timeout and the use of a single fd hit optimisations in the perl
1474	interpreter and the backend itself). Nevertheless this shows that it	2139	interpreter and the backend itself). Nevertheless this shows that it
1475	adds very little overhead in itself. Like any select-based backend its	2140	adds very little overhead in itself. Like any select-based backend its
1476	performance becomes really bad with lots of file descriptors (and few of	2141	performance becomes really bad with lots of file descriptors (and few of
1477	them active), of course, but this was not subject of this benchmark.	2142	them active), of course, but this was not subject of this benchmark.
1478		2143
1479	The C<Event> module has a relatively high setup and callback invocation	2144	The C<Event> module has a relatively high setup and callback invocation
1480	cost, but overall scores in on the third place.	2145	cost, but overall scores in on the third place.
		2146
		2147	C<IO::Async> performs admirably well, about on par with C<Event>, even
		2148	when using its pure perl backend.
1481		2149
1482	C<Glib>'s memory usage is quite a bit higher, but it features a	2150	C<Glib>'s memory usage is quite a bit higher, but it features a
1483	faster callback invocation and overall ends up in the same class as	2151	faster callback invocation and overall ends up in the same class as
1484	C<Event>. However, Glib scales extremely badly, doubling the number of	2152	C<Event>. However, Glib scales extremely badly, doubling the number of
1485	watchers increases the processing time by more than a factor of four,	2153	watchers increases the processing time by more than a factor of four,
…		…
1546	In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100	2214	In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100
1547	(1%) are active. This mirrors the activity of large servers with many	2215	(1%) are active. This mirrors the activity of large servers with many
1548	connections, most of which are idle at any one point in time.	2216	connections, most of which are idle at any one point in time.
1549		2217
1550	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent	2218	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent
1551	distribution.	2219	distribution. It uses the L<AE> interface, which makes a real difference
		2220	for the EV and Perl backends only.
1552		2221
1553	=head3 Explanation of the columns	2222	=head3 Explanation of the columns
1554		2223
1555	I<sockets> is the number of sockets, and twice the number of "servers" (as	2224	I<sockets> is the number of sockets, and twice the number of "servers" (as
1556	each server has a read and write socket end).	2225	each server has a read and write socket end).
…		…
1563	it to another server. This includes deleting the old timeout and creating	2232	it to another server. This includes deleting the old timeout and creating
1564	a new one that moves the timeout into the future.	2233	a new one that moves the timeout into the future.
1565		2234
1566	=head3 Results	2235	=head3 Results
1567		2236
1568	name sockets create request	2237	name sockets create request
1569	EV 20000 69.01 11.16	2238	EV 20000 62.66 7.99
1570	Perl 20000 73.32 35.87	2239	Perl 20000 68.32 32.64
1571	Event 20000 212.62 257.32	2240	IOAsync 20000 174.06 101.15 epoll
1572	Glib 20000 651.16 1896.30	2241	IOAsync 20000 174.67 610.84 poll
		2242	Event 20000 202.69 242.91
		2243	Glib 20000 557.01 1689.52
1573	POE 20000 349.67 12317.24 uses POE::Loop::Event	2244	POE 20000 341.54 12086.32 uses POE::Loop::Event
1574		2245
1575	=head3 Discussion	2246	=head3 Discussion
1576		2247
1577	This benchmark I<does> measure scalability and overall performance of the	2248	This benchmark I<does> measure scalability and overall performance of the
1578	particular event loop.	2249	particular event loop.
…		…
1580	EV is again fastest. Since it is using epoll on my system, the setup time	2251	EV is again fastest. Since it is using epoll on my system, the setup time
1581	is relatively high, though.	2252	is relatively high, though.
1582		2253
1583	Perl surprisingly comes second. It is much faster than the C-based event	2254	Perl surprisingly comes second. It is much faster than the C-based event
1584	loops Event and Glib.	2255	loops Event and Glib.
		2256
		2257	IO::Async performs very well when using its epoll backend, and still quite
		2258	good compared to Glib when using its pure perl backend.
1585		2259
1586	Event suffers from high setup time as well (look at its code and you will	2260	Event suffers from high setup time as well (look at its code and you will
1587	understand why). Callback invocation also has a high overhead compared to	2261	understand why). Callback invocation also has a high overhead compared to
1588	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event	2262	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event
1589	uses select or poll in basically all documented configurations.	2263	uses select or poll in basically all documented configurations.
…		…
1652	=item * C-based event loops perform very well with small number of	2326	=item * C-based event loops perform very well with small number of
1653	watchers, as the management overhead dominates.	2327	watchers, as the management overhead dominates.
1654		2328
1655	=back	2329	=back
1656		2330
		2331	=head2 THE IO::Lambda BENCHMARK
		2332
		2333	Recently I was told about the benchmark in the IO::Lambda manpage, which
		2334	could be misinterpreted to make AnyEvent look bad. In fact, the benchmark
		2335	simply compares IO::Lambda with POE, and IO::Lambda looks better (which
		2336	shouldn't come as a surprise to anybody). As such, the benchmark is
		2337	fine, and mostly shows that the AnyEvent backend from IO::Lambda isn't
		2338	very optimal. But how would AnyEvent compare when used without the extra
		2339	baggage? To explore this, I wrote the equivalent benchmark for AnyEvent.
		2340
		2341	The benchmark itself creates an echo-server, and then, for 500 times,
		2342	connects to the echo server, sends a line, waits for the reply, and then
		2343	creates the next connection. This is a rather bad benchmark, as it doesn't
		2344	test the efficiency of the framework or much non-blocking I/O, but it is a
		2345	benchmark nevertheless.
		2346
		2347	name runtime
		2348	Lambda/select 0.330 sec
		2349	+ optimized 0.122 sec
		2350	Lambda/AnyEvent 0.327 sec
		2351	+ optimized 0.138 sec
		2352	Raw sockets/select 0.077 sec
		2353	POE/select, components 0.662 sec
		2354	POE/select, raw sockets 0.226 sec
		2355	POE/select, optimized 0.404 sec
		2356
		2357	AnyEvent/select/nb 0.085 sec
		2358	AnyEvent/EV/nb 0.068 sec
		2359	+state machine 0.134 sec
		2360
		2361	The benchmark is also a bit unfair (my fault): the IO::Lambda/POE
		2362	benchmarks actually make blocking connects and use 100% blocking I/O,
		2363	defeating the purpose of an event-based solution. All of the newly
		2364	written AnyEvent benchmarks use 100% non-blocking connects (using
		2365	AnyEvent::Socket::tcp_connect and the asynchronous pure perl DNS
		2366	resolver), so AnyEvent is at a disadvantage here, as non-blocking connects
		2367	generally require a lot more bookkeeping and event handling than blocking
		2368	connects (which involve a single syscall only).
		2369
		2370	The last AnyEvent benchmark additionally uses L<AnyEvent::Handle>, which
		2371	offers similar expressive power as POE and IO::Lambda, using conventional
		2372	Perl syntax. This means that both the echo server and the client are 100%
		2373	non-blocking, further placing it at a disadvantage.
		2374
		2375	As you can see, the AnyEvent + EV combination even beats the
		2376	hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl
		2377	backend easily beats IO::Lambda and POE.
		2378
		2379	And even the 100% non-blocking version written using the high-level (and
		2380	slow :) L<AnyEvent::Handle> abstraction beats both POE and IO::Lambda
		2381	higher level ("unoptimised") abstractions by a large margin, even though
		2382	it does all of DNS, tcp-connect and socket I/O in a non-blocking way.
		2383
		2384	The two AnyEvent benchmarks programs can be found as F<eg/ae0.pl> and
		2385	F<eg/ae2.pl> in the AnyEvent distribution, the remaining benchmarks are
		2386	part of the IO::Lambda distribution and were used without any changes.
		2387
		2388
		2389	=head1 SIGNALS
		2390
		2391	AnyEvent currently installs handlers for these signals:
		2392
		2393	=over 4
		2394
		2395	=item SIGCHLD
		2396
		2397	A handler for C<SIGCHLD> is installed by AnyEvent's child watcher
		2398	emulation for event loops that do not support them natively. Also, some
		2399	event loops install a similar handler.
		2400
		2401	Additionally, when AnyEvent is loaded and SIGCHLD is set to IGNORE, then
		2402	AnyEvent will reset it to default, to avoid losing child exit statuses.
		2403
		2404	=item SIGPIPE
		2405
		2406	A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef>
		2407	when AnyEvent gets loaded.
		2408
		2409	The rationale for this is that AnyEvent users usually do not really depend
		2410	on SIGPIPE delivery (which is purely an optimisation for shell use, or
		2411	badly-written programs), but C<SIGPIPE> can cause spurious and rare
		2412	program exits as a lot of people do not expect C<SIGPIPE> when writing to
		2413	some random socket.
		2414
		2415	The rationale for installing a no-op handler as opposed to ignoring it is
		2416	that this way, the handler will be restored to defaults on exec.
		2417
		2418	Feel free to install your own handler, or reset it to defaults.
		2419
		2420	=back
		2421
		2422	=cut
		2423
		2424	undef $SIG{CHLD}
		2425	if $SIG{CHLD} eq 'IGNORE';
		2426
		2427	$SIG{PIPE} = sub { }
		2428	unless defined $SIG{PIPE};
		2429
		2430	=head1 RECOMMENDED/OPTIONAL MODULES
		2431
		2432	One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and
		2433	it's built-in modules) are required to use it.
		2434
		2435	That does not mean that AnyEvent won't take advantage of some additional
		2436	modules if they are installed.
		2437
		2438	This section epxlains which additional modules will be used, and how they
		2439	affect AnyEvent's operetion.
		2440
		2441	=over 4
		2442
		2443	=item L<Async::Interrupt>
		2444
		2445	This slightly arcane module is used to implement fast signal handling: To
		2446	my knowledge, there is no way to do completely race-free and quick
		2447	signal handling in pure perl. To ensure that signals still get
		2448	delivered, AnyEvent will start an interval timer to wake up perl (and
		2449	catch the signals) with some delay (default is 10 seconds, look for
		2450	C<$AnyEvent::MAX_SIGNAL_LATENCY>).
		2451
		2452	If this module is available, then it will be used to implement signal
		2453	catching, which means that signals will not be delayed, and the event loop
		2454	will not be interrupted regularly, which is more efficient (And good for
		2455	battery life on laptops).
		2456
		2457	This affects not just the pure-perl event loop, but also other event loops
		2458	that have no signal handling on their own (e.g. Glib, Tk, Qt).
		2459
		2460	Some event loops (POE, Event, Event::Lib) offer signal watchers natively,
		2461	and either employ their own workarounds (POE) or use AnyEvent's workaround
		2462	(using C<$AnyEvent::MAX_SIGNAL_LATENCY>). Installing L<Async::Interrupt>
		2463	does nothing for those backends.
		2464
		2465	=item L<EV>
		2466
		2467	This module isn't really "optional", as it is simply one of the backend
		2468	event loops that AnyEvent can use. However, it is simply the best event
		2469	loop available in terms of features, speed and stability: It supports
		2470	the AnyEvent API optimally, implements all the watcher types in XS, does
		2471	automatic timer adjustments even when no monotonic clock is available,
		2472	can take avdantage of advanced kernel interfaces such as C<epoll> and
		2473	C<kqueue>, and is the fastest backend I<by far>. You can even embed
		2474	L<Glib>/L<Gtk2> in it (or vice versa, see L<EV::Glib> and L<Glib::EV>).
		2475
		2476	=item L<Guard>
		2477
		2478	The guard module, when used, will be used to implement
		2479	C<AnyEvent::Util::guard>. This speeds up guards considerably (and uses a
		2480	lot less memory), but otherwise doesn't affect guard operation much. It is
		2481	purely used for performance.
		2482
		2483	=item L<JSON> and L<JSON::XS>
		2484
		2485	One of these modules is required when you want to read or write JSON data
		2486	via L<AnyEvent::Handle>. It is also written in pure-perl, but can take
		2487	advantage of the ultra-high-speed L<JSON::XS> module when it is installed.
		2488
		2489	In fact, L<AnyEvent::Handle> will use L<JSON::XS> by default if it is
		2490	installed.
		2491
		2492	=item L<Net::SSLeay>
		2493
		2494	Implementing TLS/SSL in Perl is certainly interesting, but not very
		2495	worthwhile: If this module is installed, then L<AnyEvent::Handle> (with
		2496	the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL.
		2497
		2498	=item L<Time::HiRes>
		2499
		2500	This module is part of perl since release 5.008. It will be used when the
		2501	chosen event library does not come with a timing source on it's own. The
		2502	pure-perl event loop (L<AnyEvent::Impl::Perl>) will additionally use it to
		2503	try to use a monotonic clock for timing stability.
		2504
		2505	=back
		2506
1657		2507
1658	=head1 FORK	2508	=head1 FORK
1659		2509
1660	Most event libraries are not fork-safe. The ones who are usually are	2510	Most event libraries are not fork-safe. The ones who are usually are
1661	because they rely on inefficient but fork-safe C<select> or C<poll>	2511	because they rely on inefficient but fork-safe C<select> or C<poll>
1662	calls. Only L<EV> is fully fork-aware.	2512	calls. Only L<EV> is fully fork-aware.
1663		2513
1664	If you have to fork, you must either do so I<before> creating your first	2514	If you have to fork, you must either do so I<before> creating your first
1665	watcher OR you must not use AnyEvent at all in the child.	2515	watcher OR you must not use AnyEvent at all in the child OR you must do
		2516	something completely out of the scope of AnyEvent.
1666		2517
1667		2518
1668	=head1 SECURITY CONSIDERATIONS	2519	=head1 SECURITY CONSIDERATIONS
1669		2520
1670	AnyEvent can be forced to load any event model via	2521	AnyEvent can be forced to load any event model via
…		…
1681		2532
1682	use AnyEvent;	2533	use AnyEvent;
1683		2534
1684	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can	2535	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1685	be used to probe what backend is used and gain other information (which is	2536	be used to probe what backend is used and gain other information (which is
1686	probably even less useful to an attacker than PERL_ANYEVENT_MODEL).	2537	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
		2538	$ENV{PERL_ANYEVENT_STRICT}.
		2539
		2540	Note that AnyEvent will remove I<all> environment variables starting with
		2541	C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
		2542	enabled.
1687		2543
1688		2544
1689	=head1 BUGS	2545	=head1 BUGS
1690		2546
1691	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard	2547	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
1692	to work around. If you suffer from memleaks, first upgrade to Perl 5.10	2548	to work around. If you suffer from memleaks, first upgrade to Perl 5.10
1693	and check wether the leaks still show up. (Perl 5.10.0 has other annoying	2549	and check wether the leaks still show up. (Perl 5.10.0 has other annoying
1694	mamleaks, such as leaking on C<map> and C<grep> but it is usually not as	2550	memleaks, such as leaking on C<map> and C<grep> but it is usually not as
1695	pronounced).	2551	pronounced).
1696		2552
1697		2553
1698	=head1 SEE ALSO	2554	=head1 SEE ALSO
1699		2555
…		…
1703	L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.	2559	L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.
1704		2560
1705	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,	2561	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
1706	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,	2562	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
1707	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,	2563	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
1708	L<AnyEvent::Impl::POE>.	2564	L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>, L<Anyevent::Impl::Irssi>.
1709		2565
1710	Non-blocking file handles, sockets, TCP clients and	2566	Non-blocking file handles, sockets, TCP clients and
1711	servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>.	2567	servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>.
1712		2568
1713	Asynchronous DNS: L<AnyEvent::DNS>.	2569	Asynchronous DNS: L<AnyEvent::DNS>.
1714		2570
1715	Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>,	2571	Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>,
		2572	L<Coro::Event>,
1716		2573
1717	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.	2574	Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::XMPP>,
		2575	L<AnyEvent::HTTP>.
1718		2576
1719		2577
1720	=head1 AUTHOR	2578	=head1 AUTHOR
1721		2579
1722	Marc Lehmann <schmorp@schmorp.de>	2580	Marc Lehmann <schmorp@schmorp.de>

Diff Legend

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