ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.165 by root, Tue Jul 8 23:07:26 2008 UTC vs.
Revision 1.353 by root, Thu Aug 11 20:56:07 2011 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	# if you prefer function calls, look at the AE manpage for
		13	# an alternative API.
		14
		15	# file handle or descriptor readable
11	my $w = AnyEvent->io (fh => $fh, poll => "r|w", cb => sub {	16	my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... });
		17
		18	# one-shot or repeating timers
		19	my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });
		20	my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...);
		21
		22	print AnyEvent->now; # prints current event loop time
		23	print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
		24
		25	# POSIX signal
		26	my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... });
		27
		28	# child process exit
		29	my $w = AnyEvent->child (pid => $pid, cb => sub {
		30	my ($pid, $status) = @_;
12	...	31	...
13	});	32	});
14		33
15	my $w = AnyEvent->timer (after => $seconds, cb => sub {	34	# called when event loop idle (if applicable)
16	...	35	my $w = AnyEvent->idle (cb => sub { ... });
17	});
18		36
19	my $w = AnyEvent->condvar; # stores whether a condition was flagged	37	my $w = AnyEvent->condvar; # stores whether a condition was flagged
20	$w->send; # wake up current and all future recv's	38	$w->send; # wake up current and all future recv's
21	$w->recv; # enters "main loop" till $condvar gets ->send	39	$w->recv; # enters "main loop" till $condvar gets ->send
		40	# use a condvar in callback mode:
		41	$w->cb (sub { $_[0]->recv });
22		42
23	=head1 INTRODUCTION/TUTORIAL	43	=head1 INTRODUCTION/TUTORIAL
24		44
25	This manpage is mainly a reference manual. If you are interested	45	This manpage is mainly a reference manual. If you are interested
26	in a tutorial or some gentle introduction, have a look at the	46	in a tutorial or some gentle introduction, have a look at the
27	L<AnyEvent::Intro> manpage.	47	L<AnyEvent::Intro> manpage.
28		48
		49	=head1 SUPPORT
		50
		51	An FAQ document is available as L<AnyEvent::FAQ>.
		52
		53	There also is a mailinglist for discussing all things AnyEvent, and an IRC
		54	channel, too.
		55
		56	See the AnyEvent project page at the B<Schmorpforge Ta-Sa Software
		57	Repository>, at L<http://anyevent.schmorp.de>, for more info.
		58
29	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)	59	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
30		60
31	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen	61	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
32	nowadays. So what is different about AnyEvent?	62	nowadays. So what is different about AnyEvent?
33		63
34	Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of	64	Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of
35	policy> and AnyEvent is I<small and efficient>.	65	policy> and AnyEvent is I<small and efficient>.
36		66
37	First and foremost, I<AnyEvent is not an event model> itself, it only	67	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	68	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,	69	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,	70	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	71	only one event loop can be active at the same time in a process. AnyEvent
42	helps hiding the differences between those event loops.	72	cannot change this, but it can hide the differences between those event
		73	loops.
43		74
44	The goal of AnyEvent is to offer module authors the ability to do event	75	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	76	programming (waiting for I/O or timer events) without subscribing to a
46	religion, a way of living, and most importantly: without forcing your	77	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	78	module users into the same thing by forcing them to use the same event
48	model you use.	79	model you use.
49		80
50	For modules like POE or IO::Async (which is a total misnomer as it is	81	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	82	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	83	like joining a cult: After you join, you are dependent on them and you
53	cannot use anything else, as it is simply incompatible to everything that	84	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	85	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.	86	module are I<also> forced to use the same event loop you use.
56		87
57	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works	88	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
58	fine. AnyEvent + Tk works fine etc. etc. but none of these work together	89	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	90	with the rest: POE + EV? No go. Tk + Event? No go. Again: if your module
60	your module uses one of those, every user of your module has to use it,	91	uses one of those, every user of your module has to use it, too. But if
61	too. But if your module uses AnyEvent, it works transparently with all	92	your module uses AnyEvent, it works transparently with all event models it
62	event models it supports (including stuff like POE and IO::Async, as long	93	supports (including stuff like IO::Async, as long as those use one of the
63	as those use one of the supported event loops. It is trivial to add new	94	supported event loops. It is easy to add new event loops to AnyEvent, too,
64	event loops to AnyEvent, too, so it is future-proof).	95	so it is future-proof).
65		96
66	In addition to being free of having to use I<the one and only true event	97	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	98	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	99	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	100	follow. AnyEvent, on the other hand, is lean and to the point, by only
70	offering the functionality that is necessary, in as thin as a wrapper as	101	offering the functionality that is necessary, in as thin as a wrapper as
71	technically possible.	102	technically possible.
72		103
73	Of course, AnyEvent comes with a big (and fully optional!) toolbox	104	Of course, AnyEvent comes with a big (and fully optional!) toolbox
74	of useful functionality, such as an asynchronous DNS resolver, 100%	105	of useful functionality, such as an asynchronous DNS resolver, 100%
…		…
80	useful) and you want to force your users to use the one and only event	111	useful) and you want to force your users to use the one and only event
81	model, you should I<not> use this module.	112	model, you should I<not> use this module.
82		113
83	=head1 DESCRIPTION	114	=head1 DESCRIPTION
84		115
85	L<AnyEvent> provides an identical interface to multiple event loops. This	116	L<AnyEvent> provides a uniform interface to various event loops. This
86	allows module authors to utilise an event loop without forcing module	117	allows module authors to use event loop functionality without forcing
87	users to use the same event loop (as only a single event loop can coexist	118	module users to use a specific event loop implementation (since more
88	peacefully at any one time).	119	than one event loop cannot coexist peacefully).
89		120
90	The interface itself is vaguely similar, but not identical to the L<Event>	121	The interface itself is vaguely similar, but not identical to the L<Event>
91	module.	122	module.
92		123
93	During the first call of any watcher-creation method, the module tries	124	During the first call of any watcher-creation method, the module tries
94	to detect the currently loaded event loop by probing whether one of the	125	to detect the currently loaded event loop by probing whether one of the
95	following modules is already loaded: L<EV>,	126	following modules is already loaded: L<EV>, L<AnyEvent::Loop>,
96	L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>,	127	L<Event>, L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>. The first one
97	L<POE>. The first one found is used. If none are found, the module tries	128	found is used. If none are detected, the module tries to load the first
98	to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl	129	four modules in the order given; but note that if L<EV> is not
99	adaptor should always succeed) in the order given. The first one that can	130	available, the pure-perl L<AnyEvent::Loop> should always work, so
100	be successfully loaded will be used. If, after this, still none could be	131	the other two are not normally tried.
101	found, AnyEvent will fall back to a pure-perl event loop, which is not
102	very efficient, but should work everywhere.
103		132
104	Because AnyEvent first checks for modules that are already loaded, loading	133	Because AnyEvent first checks for modules that are already loaded, loading
105	an event model explicitly before first using AnyEvent will likely make	134	an event model explicitly before first using AnyEvent will likely make
106	that model the default. For example:	135	that model the default. For example:
107		136
…		…
109	use AnyEvent;	138	use AnyEvent;
110		139
111	# .. AnyEvent will likely default to Tk	140	# .. AnyEvent will likely default to Tk
112		141
113	The I<likely> means that, if any module loads another event model and	142	The I<likely> means that, if any module loads another event model and
114	starts using it, all bets are off. Maybe you should tell their authors to	143	starts using it, all bets are off - this case should be very rare though,
115	use AnyEvent so their modules work together with others seamlessly...	144	as very few modules hardcode event loops without announcing this very
		145	loudly.
116		146
117	The pure-perl implementation of AnyEvent is called	147	The pure-perl implementation of AnyEvent is called C<AnyEvent::Loop>. Like
118	C<AnyEvent::Impl::Perl>. Like other event modules you can load it	148	other event modules you can load it explicitly and enjoy the high
119	explicitly and enjoy the high availability of that event loop :)	149	availability of that event loop :)
120		150
121	=head1 WATCHERS	151	=head1 WATCHERS
122		152
123	AnyEvent has the central concept of a I<watcher>, which is an object that	153	AnyEvent has the central concept of a I<watcher>, which is an object that
124	stores relevant data for each kind of event you are waiting for, such as	154	stores relevant data for each kind of event you are waiting for, such as
…		…
127	These watchers are normal Perl objects with normal Perl lifetime. After	157	These watchers are normal Perl objects with normal Perl lifetime. After
128	creating a watcher it will immediately "watch" for events and invoke the	158	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	159	callback when the event occurs (of course, only when the event model
130	is in control).	160	is in control).
131		161
		162	Note that B<callbacks must not permanently change global variables>
		163	potentially in use by the event loop (such as C<$_> or C<$[>) and that B<<
		164	callbacks must not C<die> >>. The former is good programming practice in
		165	Perl and the latter stems from the fact that exception handling differs
		166	widely between event loops.
		167
132	To disable the watcher you have to destroy it (e.g. by setting the	168	To disable a 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	169	variable you store it in to C<undef> or otherwise deleting all references
134	to it).	170	to it).
135		171
136	All watchers are created by calling a method on the C<AnyEvent> class.	172	All watchers are created by calling a method on the C<AnyEvent> class.
137		173
138	Many watchers either are used with "recursion" (repeating timers for	174	Many watchers either are used with "recursion" (repeating timers for
139	example), or need to refer to their watcher object in other ways.	175	example), or need to refer to their watcher object in other ways.
140		176
141	An any way to achieve that is this pattern:	177	One way to achieve that is this pattern:
142		178
143	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {	179	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
144	# you can use $w here, for example to undef it	180	# you can use $w here, for example to undef it
145	undef $w;	181	undef $w;
146	});	182	});
…		…
149	my variables are only visible after the statement in which they are	185	my variables are only visible after the statement in which they are
150	declared.	186	declared.
151		187
152	=head2 I/O WATCHERS	188	=head2 I/O WATCHERS
153		189
		190	$w = AnyEvent->io (
		191	fh => <filehandle_or_fileno>,
		192	poll => <"r" or "w">,
		193	cb => <callback>,
		194	);
		195
154	You can create an I/O watcher by calling the C<< AnyEvent->io >> method	196	You can create an I/O watcher by calling the C<< AnyEvent->io >> method
155	with the following mandatory key-value pairs as arguments:	197	with the following mandatory key-value pairs as arguments:
156		198
157	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch	199	C<fh> is the Perl I<file handle> (or a naked file descriptor) to watch
		200	for events (AnyEvent might or might not keep a reference to this file
		201	handle). Note that only file handles pointing to things for which
		202	non-blocking operation makes sense are allowed. This includes sockets,
		203	most character devices, pipes, fifos and so on, but not for example files
		204	or block devices.
		205
158	for events. C<poll> must be a string that is either C<r> or C<w>,	206	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,	207	watcher waiting for "r"eadable or "w"ritable events, respectively.
		208
160	respectively. C<cb> is the callback to invoke each time the file handle	209	C<cb> is the callback to invoke each time the file handle becomes ready.
161	becomes ready.
162		210
163	Although the callback might get passed parameters, their value and	211	Although the callback might get passed parameters, their value and
164	presence is undefined and you cannot rely on them. Portable AnyEvent	212	presence is undefined and you cannot rely on them. Portable AnyEvent
165	callbacks cannot use arguments passed to I/O watcher callbacks.	213	callbacks cannot use arguments passed to I/O watcher callbacks.
166		214
167	The I/O watcher might use the underlying file descriptor or a copy of it.	215	The I/O watcher might use the underlying file descriptor or a copy of it.
168	You must not close a file handle as long as any watcher is active on the	216	You must not close a file handle as long as any watcher is active on the
169	underlying file descriptor.	217	underlying file descriptor.
170		218
171	Some event loops issue spurious readyness notifications, so you should	219	Some event loops issue spurious readiness notifications, so you should
172	always use non-blocking calls when reading/writing from/to your file	220	always use non-blocking calls when reading/writing from/to your file
173	handles.	221	handles.
174		222
175	Example: wait for readability of STDIN, then read a line and disable the	223	Example: wait for readability of STDIN, then read a line and disable the
176	watcher.	224	watcher.
…		…
181	undef $w;	229	undef $w;
182	});	230	});
183		231
184	=head2 TIME WATCHERS	232	=head2 TIME WATCHERS
185		233
		234	$w = AnyEvent->timer (after => <seconds>, cb => <callback>);
		235
		236	$w = AnyEvent->timer (
		237	after => <fractional_seconds>,
		238	interval => <fractional_seconds>,
		239	cb => <callback>,
		240	);
		241
186	You can create a time watcher by calling the C<< AnyEvent->timer >>	242	You can create a time watcher by calling the C<< AnyEvent->timer >>
187	method with the following mandatory arguments:	243	method with the following mandatory arguments:
188		244
189	C<after> specifies after how many seconds (fractional values are	245	C<after> specifies after how many seconds (fractional values are
190	supported) the callback should be invoked. C<cb> is the callback to invoke	246	supported) the callback should be invoked. C<cb> is the callback to invoke
…		…
192		248
193	Although the callback might get passed parameters, their value and	249	Although the callback might get passed parameters, their value and
194	presence is undefined and you cannot rely on them. Portable AnyEvent	250	presence is undefined and you cannot rely on them. Portable AnyEvent
195	callbacks cannot use arguments passed to time watcher callbacks.	251	callbacks cannot use arguments passed to time watcher callbacks.
196		252
197	The callback will normally be invoked once only. If you specify another	253	The callback will normally be invoked only once. If you specify another
198	parameter, C<interval>, as a strictly positive number (> 0), then the	254	parameter, C<interval>, as a strictly positive number (> 0), then the
199	callback will be invoked regularly at that interval (in fractional	255	callback will be invoked regularly at that interval (in fractional
200	seconds) after the first invocation. If C<interval> is specified with a	256	seconds) after the first invocation. If C<interval> is specified with a
201	false value, then it is treated as if it were missing.	257	false value, then it is treated as if it were not specified at all.
202		258
203	The callback will be rescheduled before invoking the callback, but no	259	The callback will be rescheduled before invoking the callback, but no
204	attempt is done to avoid timer drift in most backends, so the interval is	260	attempt is made to avoid timer drift in most backends, so the interval is
205	only approximate.	261	only approximate.
206		262
207	Example: fire an event after 7.7 seconds.	263	Example: fire an event after 7.7 seconds.
208		264
209	my $w = AnyEvent->timer (after => 7.7, cb => sub {	265	my $w = AnyEvent->timer (after => 7.7, cb => sub {
…		…
227		283
228	While most event loops expect timers to specified in a relative way, they	284	While most event loops expect timers to specified in a relative way, they
229	use absolute time internally. This makes a difference when your clock	285	use absolute time internally. This makes a difference when your clock
230	"jumps", for example, when ntp decides to set your clock backwards from	286	"jumps", for example, when ntp decides to set your clock backwards from
231	the wrong date of 2014-01-01 to 2008-01-01, a watcher that is supposed to	287	the wrong date of 2014-01-01 to 2008-01-01, a watcher that is supposed to
232	fire "after" a second might actually take six years to finally fire.	288	fire "after a second" might actually take six years to finally fire.
233		289
234	AnyEvent cannot compensate for this. The only event loop that is conscious	290	AnyEvent cannot compensate for this. The only event loop that is conscious
235	about these issues is L<EV>, which offers both relative (ev_timer, based	291	of these issues is L<EV>, which offers both relative (ev_timer, based
236	on true relative time) and absolute (ev_periodic, based on wallclock time)	292	on true relative time) and absolute (ev_periodic, based on wallclock time)
237	timers.	293	timers.
238		294
239	AnyEvent always prefers relative timers, if available, matching the	295	AnyEvent always prefers relative timers, if available, matching the
240	AnyEvent API.	296	AnyEvent API.
…		…
262	I<In almost all cases (in all cases if you don't care), this is the	318	I<In almost all cases (in all cases if you don't care), this is the
263	function to call when you want to know the current time.>	319	function to call when you want to know the current time.>
264		320
265	This function is also often faster then C<< AnyEvent->time >>, and	321	This function is also often faster then C<< AnyEvent->time >>, and
266	thus the preferred method if you want some timestamp (for example,	322	thus the preferred method if you want some timestamp (for example,
267	L<AnyEvent::Handle> uses this to update it's activity timeouts).	323	L<AnyEvent::Handle> uses this to update its activity timeouts).
268		324
269	The rest of this section is only of relevance if you try to be very exact	325	The rest of this section is only of relevance if you try to be very exact
270	with your timing, you can skip it without bad conscience.	326	with your timing; you can skip it without a bad conscience.
271		327
272	For a practical example of when these times differ, consider L<Event::Lib>	328	For a practical example of when these times differ, consider L<Event::Lib>
273	and L<EV> and the following set-up:	329	and L<EV> and the following set-up:
274		330
275	The event loop is running and has just invoked one of your callback at	331	The event loop is running and has just invoked one of your callbacks at
276	time=500 (assume no other callbacks delay processing). In your callback,	332	time=500 (assume no other callbacks delay processing). In your callback,
277	you wait a second by executing C<sleep 1> (blocking the process for a	333	you wait a second by executing C<sleep 1> (blocking the process for a
278	second) and then (at time=501) you create a relative timer that fires	334	second) and then (at time=501) you create a relative timer that fires
279	after three seconds.	335	after three seconds.
280		336
…		…
298	In either case, if you care (and in most cases, you don't), then you	354	In either case, if you care (and in most cases, you don't), then you
299	can get whatever behaviour you want with any event loop, by taking the	355	can get whatever behaviour you want with any event loop, by taking the
300	difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into	356	difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into
301	account.	357	account.
302		358
		359	=item AnyEvent->now_update
		360
		361	Some event loops (such as L<EV> or L<AnyEvent::Loop>) cache the current
		362	time for each loop iteration (see the discussion of L<< AnyEvent->now >>,
		363	above).
		364
		365	When a callback runs for a long time (or when the process sleeps), then
		366	this "current" time will differ substantially from the real time, which
		367	might affect timers and time-outs.
		368
		369	When this is the case, you can call this method, which will update the
		370	event loop's idea of "current time".
		371
		372	A typical example would be a script in a web server (e.g. C<mod_perl>) -
		373	when mod_perl executes the script, then the event loop will have the wrong
		374	idea about the "current time" (being potentially far in the past, when the
		375	script ran the last time). In that case you should arrange a call to C<<
		376	AnyEvent->now_update >> each time the web server process wakes up again
		377	(e.g. at the start of your script, or in a handler).
		378
		379	Note that updating the time I<might> cause some events to be handled.
		380
303	=back	381	=back
304		382
305	=head2 SIGNAL WATCHERS	383	=head2 SIGNAL WATCHERS
306		384
		385	$w = AnyEvent->signal (signal => <uppercase_signal_name>, cb => <callback>);
		386
307	You can watch for signals using a signal watcher, C<signal> is the signal	387	You can watch for signals using a signal watcher, C<signal> is the signal
308	I<name> without any C<SIG> prefix, C<cb> is the Perl callback to	388	I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl
309	be invoked whenever a signal occurs.	389	callback to be invoked whenever a signal occurs.
310		390
311	Although the callback might get passed parameters, their value and	391	Although the callback might get passed parameters, their value and
312	presence is undefined and you cannot rely on them. Portable AnyEvent	392	presence is undefined and you cannot rely on them. Portable AnyEvent
313	callbacks cannot use arguments passed to signal watcher callbacks.	393	callbacks cannot use arguments passed to signal watcher callbacks.
314		394
…		…
316	invocation, and callback invocation will be synchronous. Synchronous means	396	invocation, and callback invocation will be synchronous. Synchronous means
317	that it might take a while until the signal gets handled by the process,	397	that it might take a while until the signal gets handled by the process,
318	but it is guaranteed not to interrupt any other callbacks.	398	but it is guaranteed not to interrupt any other callbacks.
319		399
320	The main advantage of using these watchers is that you can share a signal	400	The main advantage of using these watchers is that you can share a signal
321	between multiple watchers.	401	between multiple watchers, and AnyEvent will ensure that signals will not
		402	interrupt your program at bad times.
322		403
323	This watcher might use C<%SIG>, so programs overwriting those signals	404	This watcher might use C<%SIG> (depending on the event loop used),
324	directly will likely not work correctly.	405	so programs overwriting those signals directly will likely not work
		406	correctly.
325		407
326	Example: exit on SIGINT	408	Example: exit on SIGINT
327		409
328	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });	410	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
329		411
		412	=head3 Restart Behaviour
		413
		414	While restart behaviour is up to the event loop implementation, most will
		415	not restart syscalls (that includes L<Async::Interrupt> and AnyEvent's
		416	pure perl implementation).
		417
		418	=head3 Safe/Unsafe Signals
		419
		420	Perl signals can be either "safe" (synchronous to opcode handling) or
		421	"unsafe" (asynchronous) - the former might get delayed indefinitely, the
		422	latter might corrupt your memory.
		423
		424	AnyEvent signal handlers are, in addition, synchronous to the event loop,
		425	i.e. they will not interrupt your running perl program but will only be
		426	called as part of the normal event handling (just like timer, I/O etc.
		427	callbacks, too).
		428
		429	=head3 Signal Races, Delays and Workarounds
		430
		431	Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching
		432	callbacks to signals in a generic way, which is a pity, as you cannot
		433	do race-free signal handling in perl, requiring C libraries for
		434	this. AnyEvent will try to do its best, which means in some cases,
		435	signals will be delayed. The maximum time a signal might be delayed is
		436	specified in C<$AnyEvent::MAX_SIGNAL_LATENCY> (default: 10 seconds). This
		437	variable can be changed only before the first signal watcher is created,
		438	and should be left alone otherwise. This variable determines how often
		439	AnyEvent polls for signals (in case a wake-up was missed). Higher values
		440	will cause fewer spurious wake-ups, which is better for power and CPU
		441	saving.
		442
		443	All these problems can be avoided by installing the optional
		444	L<Async::Interrupt> module, which works with most event loops. It will not
		445	work with inherently broken event loops such as L<Event> or L<Event::Lib>
		446	(and not with L<POE> currently, as POE does its own workaround with
		447	one-second latency). For those, you just have to suffer the delays.
		448
330	=head2 CHILD PROCESS WATCHERS	449	=head2 CHILD PROCESS WATCHERS
331		450
		451	$w = AnyEvent->child (pid => <process id>, cb => <callback>);
		452
332	You can also watch on a child process exit and catch its exit status.	453	You can also watch for a child process exit and catch its exit status.
333		454
334	The child process is specified by the C<pid> argument (if set to C<0>, it	455	The child process is specified by the C<pid> argument (on some backends,
335	watches for any child process exit). The watcher will trigger as often	456	using C<0> watches for any child process exit, on others this will
336	as status change for the child are received. This works by installing a	457	croak). The watcher will be triggered only when the child process has
337	signal handler for C<SIGCHLD>. The callback will be called with the pid	458	finished and an exit status is available, not on any trace events
338	and exit status (as returned by waitpid), so unlike other watcher types,	459	(stopped/continued).
339	you I<can> rely on child watcher callback arguments.	460
		461	The callback will be called with the pid and exit status (as returned by
		462	waitpid), so unlike other watcher types, you I<can> rely on child watcher
		463	callback arguments.
		464
		465	This watcher type works by installing a signal handler for C<SIGCHLD>,
		466	and since it cannot be shared, nothing else should use SIGCHLD or reap
		467	random child processes (waiting for specific child processes, e.g. inside
		468	C<system>, is just fine).
340		469
341	There is a slight catch to child watchers, however: you usually start them	470	There is a slight catch to child watchers, however: you usually start them
342	I<after> the child process was created, and this means the process could	471	I<after> the child process was created, and this means the process could
343	have exited already (and no SIGCHLD will be sent anymore).	472	have exited already (and no SIGCHLD will be sent anymore).
344		473
345	Not all event models handle this correctly (POE doesn't), but even for	474	Not all event models handle this correctly (neither POE nor IO::Async do,
		475	see their AnyEvent::Impl manpages for details), but even for event models
346	event models that I<do> handle this correctly, they usually need to be	476	that I<do> handle this correctly, they usually need to be loaded before
347	loaded before the process exits (i.e. before you fork in the first place).	477	the process exits (i.e. before you fork in the first place). AnyEvent's
		478	pure perl event loop handles all cases correctly regardless of when you
		479	start the watcher.
348		480
349	This means you cannot create a child watcher as the very first thing in an	481	This means you cannot create a child watcher as the very first
350	AnyEvent program, you I<have> to create at least one watcher before you	482	thing in an AnyEvent program, you I<have> to create at least one
351	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).	483	watcher before you C<fork> the child (alternatively, you can call
		484	C<AnyEvent::detect>).
		485
		486	As most event loops do not support waiting for child events, they will be
		487	emulated by AnyEvent in most cases, in which case the latency and race
		488	problems mentioned in the description of signal watchers apply.
352		489
353	Example: fork a process and wait for it	490	Example: fork a process and wait for it
354		491
355	my $done = AnyEvent->condvar;	492	my $done = AnyEvent->condvar;
356		493
…		…
366	);	503	);
367		504
368	# do something else, then wait for process exit	505	# do something else, then wait for process exit
369	$done->recv;	506	$done->recv;
370		507
		508	=head2 IDLE WATCHERS
		509
		510	$w = AnyEvent->idle (cb => <callback>);
		511
		512	This will repeatedly invoke the callback after the process becomes idle,
		513	until either the watcher is destroyed or new events have been detected.
		514
		515	Idle watchers are useful when there is a need to do something, but it
		516	is not so important (or wise) to do it instantly. The callback will be
		517	invoked only when there is "nothing better to do", which is usually
		518	defined as "all outstanding events have been handled and no new events
		519	have been detected". That means that idle watchers ideally get invoked
		520	when the event loop has just polled for new events but none have been
		521	detected. Instead of blocking to wait for more events, the idle watchers
		522	will be invoked.
		523
		524	Unfortunately, most event loops do not really support idle watchers (only
		525	EV, Event and Glib do it in a usable fashion) - for the rest, AnyEvent
		526	will simply call the callback "from time to time".
		527
		528	Example: read lines from STDIN, but only process them when the
		529	program is otherwise idle:
		530
		531	my @lines; # read data
		532	my $idle_w;
		533	my $io_w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
		534	push @lines, scalar <STDIN>;
		535
		536	# start an idle watcher, if not already done
		537	$idle_w ||= AnyEvent->idle (cb => sub {
		538	# handle only one line, when there are lines left
		539	if (my $line = shift @lines) {
		540	print "handled when idle: $line";
		541	} else {
		542	# otherwise disable the idle watcher again
		543	undef $idle_w;
		544	}
		545	});
		546	});
		547
371	=head2 CONDITION VARIABLES	548	=head2 CONDITION VARIABLES
		549
		550	$cv = AnyEvent->condvar;
		551
		552	$cv->send (<list>);
		553	my @res = $cv->recv;
372		554
373	If you are familiar with some event loops you will know that all of them	555	If you are familiar with some event loops you will know that all of them
374	require you to run some blocking "loop", "run" or similar function that	556	require you to run some blocking "loop", "run" or similar function that
375	will actively watch for new events and call your callbacks.	557	will actively watch for new events and call your callbacks.
376		558
377	AnyEvent is different, it expects somebody else to run the event loop and	559	AnyEvent is slightly different: it expects somebody else to run the event
378	will only block when necessary (usually when told by the user).	560	loop and will only block when necessary (usually when told by the user).
379		561
380	The instrument to do that is called a "condition variable", so called	562	The tool to do that is called a "condition variable", so called because
381	because they represent a condition that must become true.	563	they represent a condition that must become true.
		564
		565	Now is probably a good time to look at the examples further below.
382		566
383	Condition variables can be created by calling the C<< AnyEvent->condvar	567	Condition variables can be created by calling the C<< AnyEvent->condvar
384	>> method, usually without arguments. The only argument pair allowed is	568	>> method, usually without arguments. The only argument pair allowed is
385	C<cb>, which specifies a callback to be called when the condition variable	569	C<cb>, which specifies a callback to be called when the condition variable
386	becomes true.	570	becomes true, with the condition variable as the first argument (but not
		571	the results).
387		572
388	After creation, the condition variable is "false" until it becomes "true"	573	After creation, the condition variable is "false" until it becomes "true"
389	by calling the C<send> method (or calling the condition variable as if it	574	by calling the C<send> method (or calling the condition variable as if it
390	were a callback, read about the caveats in the description for the C<<	575	were a callback, read about the caveats in the description for the C<<
391	->send >> method).	576	->send >> method).
392		577
393	Condition variables are similar to callbacks, except that you can	578	Since condition variables are the most complex part of the AnyEvent API, here are
394	optionally wait for them. They can also be called merge points - points	579	some different mental models of what they are - pick the ones you can connect to:
395	in time where multiple outstanding events have been processed. And yet	580
396	another way to call them is transactions - each condition variable can be	581	=over 4
397	used to represent a transaction, which finishes at some point and delivers	582
398	a result.	583	=item * Condition variables are like callbacks - you can call them (and pass them instead
		584	of callbacks). Unlike callbacks however, you can also wait for them to be called.
		585
		586	=item * Condition variables are signals - one side can emit or send them,
		587	the other side can wait for them, or install a handler that is called when
		588	the signal fires.
		589
		590	=item * Condition variables are like "Merge Points" - points in your program
		591	where you merge multiple independent results/control flows into one.
		592
		593	=item * Condition variables represent a transaction - functions that start
		594	some kind of transaction can return them, leaving the caller the choice
		595	between waiting in a blocking fashion, or setting a callback.
		596
		597	=item * Condition variables represent future values, or promises to deliver
		598	some result, long before the result is available.
		599
		600	=back
399		601
400	Condition variables are very useful to signal that something has finished,	602	Condition variables are very useful to signal that something has finished,
401	for example, if you write a module that does asynchronous http requests,	603	for example, if you write a module that does asynchronous http requests,
402	then a condition variable would be the ideal candidate to signal the	604	then a condition variable would be the ideal candidate to signal the
403	availability of results. The user can either act when the callback is	605	availability of results. The user can either act when the callback is
…		…
416		618
417	Condition variables are represented by hash refs in perl, and the keys	619	Condition variables are represented by hash refs in perl, and the keys
418	used by AnyEvent itself are all named C<_ae_XXX> to make subclassing	620	used by AnyEvent itself are all named C<_ae_XXX> to make subclassing
419	easy (it is often useful to build your own transaction class on top of	621	easy (it is often useful to build your own transaction class on top of
420	AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call	622	AnyEvent). To subclass, use C<AnyEvent::CondVar> as base class and call
421	it's C<new> method in your own C<new> method.	623	its C<new> method in your own C<new> method.
422		624
423	There are two "sides" to a condition variable - the "producer side" which	625	There are two "sides" to a condition variable - the "producer side" which
424	eventually calls C<< -> send >>, and the "consumer side", which waits	626	eventually calls C<< -> send >>, and the "consumer side", which waits
425	for the send to occur.	627	for the send to occur.
426		628
427	Example: wait for a timer.	629	Example: wait for a timer.
428		630
429	# wait till the result is ready	631	# condition: "wait till the timer is fired"
430	my $result_ready = AnyEvent->condvar;	632	my $timer_fired = AnyEvent->condvar;
431		633
432	# do something such as adding a timer	634	# create the timer - we could wait for, say
433	# or socket watcher the calls $result_ready->send	635	# a handle becomign ready, or even an
434	# when the "result" is ready.	636	# AnyEvent::HTTP request to finish, but
435	# in this case, we simply use a timer:	637	# in this case, we simply use a timer:
436	my $w = AnyEvent->timer (	638	my $w = AnyEvent->timer (
437	after => 1,	639	after => 1,
438	cb => sub { $result_ready->send },	640	cb => sub { $timer_fired->send },
439	);	641	);
440		642
441	# this "blocks" (while handling events) till the callback	643	# this "blocks" (while handling events) till the callback
442	# calls send	644	# calls ->send
443	$result_ready->recv;	645	$timer_fired->recv;
444		646
445	Example: wait for a timer, but take advantage of the fact that	647	Example: wait for a timer, but take advantage of the fact that condition
446	condition variables are also code references.	648	variables are also callable directly.
447		649
448	my $done = AnyEvent->condvar;	650	my $done = AnyEvent->condvar;
449	my $delay = AnyEvent->timer (after => 5, cb => $done);	651	my $delay = AnyEvent->timer (after => 5, cb => $done);
450	$done->recv;	652	$done->recv;
		653
		654	Example: Imagine an API that returns a condvar and doesn't support
		655	callbacks. This is how you make a synchronous call, for example from
		656	the main program:
		657
		658	use AnyEvent::CouchDB;
		659
		660	...
		661
		662	my @info = $couchdb->info->recv;
		663
		664	And this is how you would just set a callback to be called whenever the
		665	results are available:
		666
		667	$couchdb->info->cb (sub {
		668	my @info = $_[0]->recv;
		669	});
451		670
452	=head3 METHODS FOR PRODUCERS	671	=head3 METHODS FOR PRODUCERS
453		672
454	These methods should only be used by the producing side, i.e. the	673	These methods should only be used by the producing side, i.e. the
455	code/module that eventually sends the signal. Note that it is also	674	code/module that eventually sends the signal. Note that it is also
…		…
468	immediately from within send.	687	immediately from within send.
469		688
470	Any arguments passed to the C<send> call will be returned by all	689	Any arguments passed to the C<send> call will be returned by all
471	future C<< ->recv >> calls.	690	future C<< ->recv >> calls.
472		691
473	Condition variables are overloaded so one can call them directly	692	Condition variables are overloaded so one can call them directly (as if
474	(as a code reference). Calling them directly is the same as calling	693	they were a code reference). Calling them directly is the same as calling
475	C<send>. Note, however, that many C-based event loops do not handle	694	C<send>.
476	overloading, so as tempting as it may be, passing a condition variable
477	instead of a callback does not work. Both the pure perl and EV loops
478	support overloading, however, as well as all functions that use perl to
479	invoke a callback (as in L<AnyEvent::Socket> and L<AnyEvent::DNS> for
480	example).
481		695
482	=item $cv->croak ($error)	696	=item $cv->croak ($error)
483		697
484	Similar to send, but causes all call's to C<< ->recv >> to invoke	698	Similar to send, but causes all calls to C<< ->recv >> to invoke
485	C<Carp::croak> with the given error message/object/scalar.	699	C<Carp::croak> with the given error message/object/scalar.
486		700
487	This can be used to signal any errors to the condition variable	701	This can be used to signal any errors to the condition variable
488	user/consumer.	702	user/consumer. Doing it this way instead of calling C<croak> directly
		703	delays the error detection, but has the overwhelming advantage that it
		704	diagnoses the error at the place where the result is expected, and not
		705	deep in some event callback with no connection to the actual code causing
		706	the problem.
489		707
490	=item $cv->begin ([group callback])	708	=item $cv->begin ([group callback])
491		709
492	=item $cv->end	710	=item $cv->end
493
494	These two methods are EXPERIMENTAL and MIGHT CHANGE.
495		711
496	These two methods can be used to combine many transactions/events into	712	These two methods can be used to combine many transactions/events into
497	one. For example, a function that pings many hosts in parallel might want	713	one. For example, a function that pings many hosts in parallel might want
498	to use a condition variable for the whole process.	714	to use a condition variable for the whole process.
499		715
500	Every call to C<< ->begin >> will increment a counter, and every call to	716	Every call to C<< ->begin >> will increment a counter, and every call to
501	C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end	717	C<< ->end >> will decrement it. If the counter reaches C<0> in C<< ->end
502	>>, the (last) callback passed to C<begin> will be executed. That callback	718	>>, the (last) callback passed to C<begin> will be executed, passing the
503	is I<supposed> to call C<< ->send >>, but that is not required. If no	719	condvar as first argument. That callback is I<supposed> to call C<< ->send
504	callback was set, C<send> will be called without any arguments.	720	>>, but that is not required. If no group callback was set, C<send> will
		721	be called without any arguments.
505		722
506	Let's clarify this with the ping example:	723	You can think of C<< $cv->send >> giving you an OR condition (one call
		724	sends), while C<< $cv->begin >> and C<< $cv->end >> giving you an AND
		725	condition (all C<begin> calls must be C<end>'ed before the condvar sends).
		726
		727	Let's start with a simple example: you have two I/O watchers (for example,
		728	STDOUT and STDERR for a program), and you want to wait for both streams to
		729	close before activating a condvar:
507		730
508	my $cv = AnyEvent->condvar;	731	my $cv = AnyEvent->condvar;
509		732
		733	$cv->begin; # first watcher
		734	my $w1 = AnyEvent->io (fh => $fh1, cb => sub {
		735	defined sysread $fh1, my $buf, 4096
		736	or $cv->end;
		737	});
		738
		739	$cv->begin; # second watcher
		740	my $w2 = AnyEvent->io (fh => $fh2, cb => sub {
		741	defined sysread $fh2, my $buf, 4096
		742	or $cv->end;
		743	});
		744
		745	$cv->recv;
		746
		747	This works because for every event source (EOF on file handle), there is
		748	one call to C<begin>, so the condvar waits for all calls to C<end> before
		749	sending.
		750
		751	The ping example mentioned above is slightly more complicated, as the
		752	there are results to be passwd back, and the number of tasks that are
		753	begun can potentially be zero:
		754
		755	my $cv = AnyEvent->condvar;
		756
510	my %result;	757	my %result;
511	$cv->begin (sub { $cv->send (\%result) });	758	$cv->begin (sub { shift->send (\%result) });
512		759
513	for my $host (@list_of_hosts) {	760	for my $host (@list_of_hosts) {
514	$cv->begin;	761	$cv->begin;
515	ping_host_then_call_callback $host, sub {	762	ping_host_then_call_callback $host, sub {
516	$result{$host} = ...;	763	$result{$host} = ...;
…		…
531	loop, which serves two important purposes: first, it sets the callback	778	loop, which serves two important purposes: first, it sets the callback
532	to be called once the counter reaches C<0>, and second, it ensures that	779	to be called once the counter reaches C<0>, and second, it ensures that
533	C<send> is called even when C<no> hosts are being pinged (the loop	780	C<send> is called even when C<no> hosts are being pinged (the loop
534	doesn't execute once).	781	doesn't execute once).
535		782
536	This is the general pattern when you "fan out" into multiple subrequests:	783	This is the general pattern when you "fan out" into multiple (but
537	use an outer C<begin>/C<end> pair to set the callback and ensure C<end>	784	potentially zero) subrequests: use an outer C<begin>/C<end> pair to set
538	is called at least once, and then, for each subrequest you start, call	785	the callback and ensure C<end> is called at least once, and then, for each
539	C<begin> and for each subrequest you finish, call C<end>.	786	subrequest you start, call C<begin> and for each subrequest you finish,
		787	call C<end>.
540		788
541	=back	789	=back
542		790
543	=head3 METHODS FOR CONSUMERS	791	=head3 METHODS FOR CONSUMERS
544		792
…		…
548	=over 4	796	=over 4
549		797
550	=item $cv->recv	798	=item $cv->recv
551		799
552	Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak	800	Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak
553	>> methods have been called on c<$cv>, while servicing other watchers	801	>> methods have been called on C<$cv>, while servicing other watchers
554	normally.	802	normally.
555		803
556	You can only wait once on a condition - additional calls are valid but	804	You can only wait once on a condition - additional calls are valid but
557	will return immediately.	805	will return immediately.
558		806
…		…
560	function will call C<croak>.	808	function will call C<croak>.
561		809
562	In list context, all parameters passed to C<send> will be returned,	810	In list context, all parameters passed to C<send> will be returned,
563	in scalar context only the first one will be returned.	811	in scalar context only the first one will be returned.
564		812
		813	Note that doing a blocking wait in a callback is not supported by any
		814	event loop, that is, recursive invocation of a blocking C<< ->recv
		815	>> is not allowed, and the C<recv> call will C<croak> if such a
		816	condition is detected. This condition can be slightly loosened by using
		817	L<Coro::AnyEvent>, which allows you to do a blocking C<< ->recv >> from
		818	any thread that doesn't run the event loop itself.
		819
565	Not all event models support a blocking wait - some die in that case	820	Not all event models support a blocking wait - some die in that case
566	(programs might want to do that to stay interactive), so I<if you are	821	(programs might want to do that to stay interactive), so I<if you are
567	using this from a module, never require a blocking wait>, but let the	822	using this from a module, never require a blocking wait>. Instead, let the
568	caller decide whether the call will block or not (for example, by coupling	823	caller decide whether the call will block or not (for example, by coupling
569	condition variables with some kind of request results and supporting	824	condition variables with some kind of request results and supporting
570	callbacks so the caller knows that getting the result will not block,	825	callbacks so the caller knows that getting the result will not block,
571	while still supporting blocking waits if the caller so desires).	826	while still supporting blocking waits if the caller so desires).
572		827
573	Another reason I<never> to C<< ->recv >> in a module is that you cannot
574	sensibly have two C<< ->recv >>'s in parallel, as that would require
575	multiple interpreters or coroutines/threads, none of which C<AnyEvent>
576	can supply.
577
578	The L<Coro> module, however, I<can> and I<does> supply coroutines and, in
579	fact, L<Coro::AnyEvent> replaces AnyEvent's condvars by coroutine-safe
580	versions and also integrates coroutines into AnyEvent, making blocking
581	C<< ->recv >> calls perfectly safe as long as they are done from another
582	coroutine (one that doesn't run the event loop).
583
584	You can ensure that C<< -recv >> never blocks by setting a callback and	828	You can ensure that C<< ->recv >> never blocks by setting a callback and
585	only calling C<< ->recv >> from within that callback (or at a later	829	only calling C<< ->recv >> from within that callback (or at a later
586	time). This will work even when the event loop does not support blocking	830	time). This will work even when the event loop does not support blocking
587	waits otherwise.	831	waits otherwise.
588		832
589	=item $bool = $cv->ready	833	=item $bool = $cv->ready
590		834
591	Returns true when the condition is "true", i.e. whether C<send> or	835	Returns true when the condition is "true", i.e. whether C<send> or
592	C<croak> have been called.	836	C<croak> have been called.
593		837
594	=item $cb = $cv->cb ([new callback])	838	=item $cb = $cv->cb ($cb->($cv))
595		839
596	This is a mutator function that returns the callback set and optionally	840	This is a mutator function that returns the callback set and optionally
597	replaces it before doing so.	841	replaces it before doing so.
598		842
599	The callback will be called when the condition becomes "true", i.e. when	843	The callback will be called when the condition becomes "true", i.e. when
600	C<send> or C<croak> are called, with the only argument being the condition	844	C<send> or C<croak> are called, with the only argument being the
601	variable itself. Calling C<recv> inside the callback or at any later time	845	condition variable itself. If the condition is already true, the
602	is guaranteed not to block.	846	callback is called immediately when it is set. Calling C<recv> inside
		847	the callback or at any later time is guaranteed not to block.
603		848
604	=back	849	=back
605		850
		851	=head1 SUPPORTED EVENT LOOPS/BACKENDS
		852
		853	The available backend classes are (every class has its own manpage):
		854
		855	=over 4
		856
		857	=item Backends that are autoprobed when no other event loop can be found.
		858
		859	EV is the preferred backend when no other event loop seems to be in
		860	use. If EV is not installed, then AnyEvent will fall back to its own
		861	pure-perl implementation, which is available everywhere as it comes with
		862	AnyEvent itself.
		863
		864	AnyEvent::Impl::EV based on EV (interface to libev, best choice).
		865	AnyEvent::Impl::Perl pure-perl AnyEvent::Loop, fast and portable.
		866
		867	=item Backends that are transparently being picked up when they are used.
		868
		869	These will be used if they are already loaded when the first watcher
		870	is created, in which case it is assumed that the application is using
		871	them. This means that AnyEvent will automatically pick the right backend
		872	when the main program loads an event module before anything starts to
		873	create watchers. Nothing special needs to be done by the main program.
		874
		875	AnyEvent::Impl::Event based on Event, very stable, few glitches.
		876	AnyEvent::Impl::Glib based on Glib, slow but very stable.
		877	AnyEvent::Impl::Tk based on Tk, very broken.
		878	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
		879	AnyEvent::Impl::POE based on POE, very slow, some limitations.
		880	AnyEvent::Impl::Irssi used when running within irssi.
		881	AnyEvent::Impl::IOAsync based on IO::Async.
		882	AnyEvent::Impl::Cocoa based on Cocoa::EventLoop.
		883	AnyEvent::Impl::FLTK based on FLTK.
		884
		885	=item Backends with special needs.
		886
		887	Qt requires the Qt::Application to be instantiated first, but will
		888	otherwise be picked up automatically. As long as the main program
		889	instantiates the application before any AnyEvent watchers are created,
		890	everything should just work.
		891
		892	AnyEvent::Impl::Qt based on Qt.
		893
		894	=item Event loops that are indirectly supported via other backends.
		895
		896	Some event loops can be supported via other modules:
		897
		898	There is no direct support for WxWidgets (L<Wx>) or L<Prima>.
		899
		900	B<WxWidgets> has no support for watching file handles. However, you can
		901	use WxWidgets through the POE adaptor, as POE has a Wx backend that simply
		902	polls 20 times per second, which was considered to be too horrible to even
		903	consider for AnyEvent.
		904
		905	B<Prima> is not supported as nobody seems to be using it, but it has a POE
		906	backend, so it can be supported through POE.
		907
		908	AnyEvent knows about both L<Prima> and L<Wx>, however, and will try to
		909	load L<POE> when detecting them, in the hope that POE will pick them up,
		910	in which case everything will be automatic.
		911
		912	=back
		913
606	=head1 GLOBAL VARIABLES AND FUNCTIONS	914	=head1 GLOBAL VARIABLES AND FUNCTIONS
607		915
		916	These are not normally required to use AnyEvent, but can be useful to
		917	write AnyEvent extension modules.
		918
608	=over 4	919	=over 4
609		920
610	=item $AnyEvent::MODEL	921	=item $AnyEvent::MODEL
611		922
612	Contains C<undef> until the first watcher is being created. Then it	923	Contains C<undef> until the first watcher is being created, before the
		924	backend has been autodetected.
		925
613	contains the event model that is being used, which is the name of the	926	Afterwards it contains the event model that is being used, which is the
614	Perl class implementing the model. This class is usually one of the	927	name of the Perl class implementing the model. This class is usually one
615	C<AnyEvent::Impl:xxx> modules, but can be any other class in the case	928	of the C<AnyEvent::Impl::xxx> modules, but can be any other class in the
616	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).	929	case AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode> it
617		930	will be C<urxvt::anyevent>).
618	The known classes so far are:
619
620	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
621	AnyEvent::Impl::Event based on Event, second best choice.
622	AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
623	AnyEvent::Impl::Glib based on Glib, third-best choice.
624	AnyEvent::Impl::Tk based on Tk, very bad choice.
625	AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
626	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
627	AnyEvent::Impl::POE based on POE, not generic enough for full support.
628
629	There is no support for WxWidgets, as WxWidgets has no support for
630	watching file handles. However, you can use WxWidgets through the
631	POE Adaptor, as POE has a Wx backend that simply polls 20 times per
632	second, which was considered to be too horrible to even consider for
633	AnyEvent. Likewise, other POE backends can be used by AnyEvent by using
634	it's adaptor.
635
636	AnyEvent knows about L<Prima> and L<Wx> and will try to use L<POE> when
637	autodetecting them.
638		931
639	=item AnyEvent::detect	932	=item AnyEvent::detect
640		933
641	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model	934	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
642	if necessary. You should only call this function right before you would	935	if necessary. You should only call this function right before you would
643	have created an AnyEvent watcher anyway, that is, as late as possible at	936	have created an AnyEvent watcher anyway, that is, as late as possible at
644	runtime.	937	runtime, and not e.g. during initialisation of your module.
		938
		939	If you need to do some initialisation before AnyEvent watchers are
		940	created, use C<post_detect>.
645		941
646	=item $guard = AnyEvent::post_detect { BLOCK }	942	=item $guard = AnyEvent::post_detect { BLOCK }
647		943
648	Arranges for the code block to be executed as soon as the event model is	944	Arranges for the code block to be executed as soon as the event model is
649	autodetected (or immediately if this has already happened).	945	autodetected (or immediately if that has already happened).
		946
		947	The block will be executed I<after> the actual backend has been detected
		948	(C<$AnyEvent::MODEL> is set), but I<before> any watchers have been
		949	created, so it is possible to e.g. patch C<@AnyEvent::ISA> or do
		950	other initialisations - see the sources of L<AnyEvent::Strict> or
		951	L<AnyEvent::AIO> to see how this is used.
		952
		953	The most common usage is to create some global watchers, without forcing
		954	event module detection too early, for example, L<AnyEvent::AIO> creates
		955	and installs the global L<IO::AIO> watcher in a C<post_detect> block to
		956	avoid autodetecting the event module at load time.
650		957
651	If called in scalar or list context, then it creates and returns an object	958	If called in scalar or list context, then it creates and returns an object
652	that automatically removes the callback again when it is destroyed. See	959	that automatically removes the callback again when it is destroyed (or
		960	C<undef> when the hook was immediately executed). See L<AnyEvent::AIO> for
653	L<Coro::BDB> for a case where this is useful.	961	a case where this is useful.
		962
		963	Example: Create a watcher for the IO::AIO module and store it in
		964	C<$WATCHER>, but do so only do so after the event loop is initialised.
		965
		966	our WATCHER;
		967
		968	my $guard = AnyEvent::post_detect {
		969	$WATCHER = AnyEvent->io (fh => IO::AIO::poll_fileno, poll => 'r', cb => \&IO::AIO::poll_cb);
		970	};
		971
		972	# the ||= is important in case post_detect immediately runs the block,
		973	# as to not clobber the newly-created watcher. assigning both watcher and
		974	# post_detect guard to the same variable has the advantage of users being
		975	# able to just C<undef $WATCHER> if the watcher causes them grief.
		976
		977	$WATCHER ||= $guard;
654		978
655	=item @AnyEvent::post_detect	979	=item @AnyEvent::post_detect
656		980
657	If there are any code references in this array (you can C<push> to it	981	If there are any code references in this array (you can C<push> to it
658	before or after loading AnyEvent), then they will called directly after	982	before or after loading AnyEvent), then they will be called directly
659	the event loop has been chosen.	983	after the event loop has been chosen.
660		984
661	You should check C<$AnyEvent::MODEL> before adding to this array, though:	985	You should check C<$AnyEvent::MODEL> before adding to this array, though:
662	if it contains a true value then the event loop has already been detected,	986	if it is defined then the event loop has already been detected, and the
663	and the array will be ignored.	987	array will be ignored.
664		988
665	Best use C<AnyEvent::post_detect { BLOCK }> instead.	989	Best use C<AnyEvent::post_detect { BLOCK }> when your application allows
		990	it, as it takes care of these details.
		991
		992	This variable is mainly useful for modules that can do something useful
		993	when AnyEvent is used and thus want to know when it is initialised, but do
		994	not need to even load it by default. This array provides the means to hook
		995	into AnyEvent passively, without loading it.
		996
		997	Example: To load Coro::AnyEvent whenever Coro and AnyEvent are used
		998	together, you could put this into Coro (this is the actual code used by
		999	Coro to accomplish this):
		1000
		1001	if (defined $AnyEvent::MODEL) {
		1002	# AnyEvent already initialised, so load Coro::AnyEvent
		1003	require Coro::AnyEvent;
		1004	} else {
		1005	# AnyEvent not yet initialised, so make sure to load Coro::AnyEvent
		1006	# as soon as it is
		1007	push @AnyEvent::post_detect, sub { require Coro::AnyEvent };
		1008	}
		1009
		1010	=item AnyEvent::postpone BLOCK
		1011
		1012	Arranges for the block to be executed as soon as possible, but not before
		1013	the call itself returns. In practise, the block will be executed just
		1014	before the event loop polls for new events, or shortly afterwards.
		1015
		1016	This function never returns anything (to make the C<return postpone { ...
		1017	}> idiom more useful.
		1018
		1019	To understand the usefulness of this function, consider a function that
		1020	asynchronously does something for you and returns some transaction
		1021	object or guard to let you cancel the operation. For example,
		1022	C<AnyEvent::Socket::tcp_connect>:
		1023
		1024	# start a conenction attempt unless one is active
		1025	$self->{connect_guard} ||= AnyEvent::Socket::tcp_connect "www.example.net", 80, sub {
		1026	delete $self->{connect_guard};
		1027	...
		1028	};
		1029
		1030	Imagine that this function could instantly call the callback, for
		1031	example, because it detects an obvious error such as a negative port
		1032	number. Invoking the callback before the function returns causes problems
		1033	however: the callback will be called and will try to delete the guard
		1034	object. But since the function hasn't returned yet, there is nothing to
		1035	delete. When the function eventually returns it will assign the guard
		1036	object to C<< $self->{connect_guard} >>, where it will likely never be
		1037	deleted, so the program thinks it is still trying to connect.
		1038
		1039	This is where C<AnyEvent::postpone> should be used. Instead of calling the
		1040	callback directly on error:
		1041
		1042	$cb->(undef), return # signal error to callback, BAD!
		1043	if $some_error_condition;
		1044
		1045	It should use C<postpone>:
		1046
		1047	AnyEvent::postpone { $cb->(undef) }, return # signal error to callback, later
		1048	if $some_error_condition;
666		1049
667	=back	1050	=back
668		1051
669	=head1 WHAT TO DO IN A MODULE	1052	=head1 WHAT TO DO IN A MODULE
670		1053
…		…
681	because it will stall the whole program, and the whole point of using	1064	because it will stall the whole program, and the whole point of using
682	events is to stay interactive.	1065	events is to stay interactive.
683		1066
684	It is fine, however, to call C<< ->recv >> when the user of your module	1067	It is fine, however, to call C<< ->recv >> when the user of your module
685	requests it (i.e. if you create a http request object ad have a method	1068	requests it (i.e. if you create a http request object ad have a method
686	called C<results> that returns the results, it should call C<< ->recv >>	1069	called C<results> that returns the results, it may call C<< ->recv >>
687	freely, as the user of your module knows what she is doing. always).	1070	freely, as the user of your module knows what she is doing. Always).
688		1071
689	=head1 WHAT TO DO IN THE MAIN PROGRAM	1072	=head1 WHAT TO DO IN THE MAIN PROGRAM
690		1073
691	There will always be a single main program - the only place that should	1074	There will always be a single main program - the only place that should
692	dictate which event model to use.	1075	dictate which event model to use.
693		1076
694	If it doesn't care, it can just "use AnyEvent" and use it itself, or not	1077	If the program is not event-based, it need not do anything special, even
695	do anything special (it does not need to be event-based) and let AnyEvent	1078	when it depends on a module that uses an AnyEvent. If the program itself
696	decide which implementation to chose if some module relies on it.	1079	uses AnyEvent, but does not care which event loop is used, all it needs
		1080	to do is C<use AnyEvent>. In either case, AnyEvent will choose the best
		1081	available loop implementation.
697		1082
698	If the main program relies on a specific event model - for example, in	1083	If the main program relies on a specific event model - for example, in
699	Gtk2 programs you have to rely on the Glib module - you should load the	1084	Gtk2 programs you have to rely on the Glib module - you should load the
700	event module before loading AnyEvent or any module that uses it: generally	1085	event module before loading AnyEvent or any module that uses it: generally
701	speaking, you should load it as early as possible. The reason is that	1086	speaking, you should load it as early as possible. The reason is that
702	modules might create watchers when they are loaded, and AnyEvent will	1087	modules might create watchers when they are loaded, and AnyEvent will
703	decide on the event model to use as soon as it creates watchers, and it	1088	decide on the event model to use as soon as it creates watchers, and it
704	might chose the wrong one unless you load the correct one yourself.	1089	might choose the wrong one unless you load the correct one yourself.
705		1090
706	You can chose to use a pure-perl implementation by loading the	1091	You can chose to use a pure-perl implementation by loading the
707	C<AnyEvent::Impl::Perl> module, which gives you similar behaviour	1092	C<AnyEvent::Loop> module, which gives you similar behaviour
708	everywhere, but letting AnyEvent chose the model is generally better.	1093	everywhere, but letting AnyEvent chose the model is generally better.
709		1094
710	=head2 MAINLOOP EMULATION	1095	=head2 MAINLOOP EMULATION
711		1096
712	Sometimes (often for short test scripts, or even standalone programs who	1097	Sometimes (often for short test scripts, or even standalone programs who
…		…
725		1110
726		1111
727	=head1 OTHER MODULES	1112	=head1 OTHER MODULES
728		1113
729	The following is a non-exhaustive list of additional modules that use	1114	The following is a non-exhaustive list of additional modules that use
730	AnyEvent and can therefore be mixed easily with other AnyEvent modules	1115	AnyEvent as a client and can therefore be mixed easily with other AnyEvent
731	in the same program. Some of the modules come with AnyEvent, some are	1116	modules and other event loops in the same program. Some of the modules
732	available via CPAN.	1117	come as part of AnyEvent, the others are available via CPAN.
733		1118
734	=over 4	1119	=over 4
735		1120
736	=item L<AnyEvent::Util>	1121	=item L<AnyEvent::Util>
737		1122
738	Contains various utility functions that replace often-used but blocking	1123	Contains various utility functions that replace often-used blocking
739	functions such as C<inet_aton> by event-/callback-based versions.	1124	functions such as C<inet_aton> with event/callback-based versions.
740		1125
741	=item L<AnyEvent::Socket>	1126	=item L<AnyEvent::Socket>
742		1127
743	Provides various utility functions for (internet protocol) sockets,	1128	Provides various utility functions for (internet protocol) sockets,
744	addresses and name resolution. Also functions to create non-blocking tcp	1129	addresses and name resolution. Also functions to create non-blocking tcp
…		…
746		1131
747	=item L<AnyEvent::Handle>	1132	=item L<AnyEvent::Handle>
748		1133
749	Provide read and write buffers, manages watchers for reads and writes,	1134	Provide read and write buffers, manages watchers for reads and writes,
750	supports raw and formatted I/O, I/O queued and fully transparent and	1135	supports raw and formatted I/O, I/O queued and fully transparent and
751	non-blocking SSL/TLS.	1136	non-blocking SSL/TLS (via L<AnyEvent::TLS>).
752		1137
753	=item L<AnyEvent::DNS>	1138	=item L<AnyEvent::DNS>
754		1139
755	Provides rich asynchronous DNS resolver capabilities.	1140	Provides rich asynchronous DNS resolver capabilities.
756		1141
		1142	=item L<AnyEvent::HTTP>, L<AnyEvent::IRC>, L<AnyEvent::XMPP>, L<AnyEvent::GPSD>, L<AnyEvent::IGS>, L<AnyEvent::FCP>
		1143
		1144	Implement event-based interfaces to the protocols of the same name (for
		1145	the curious, IGS is the International Go Server and FCP is the Freenet
		1146	Client Protocol).
		1147
		1148	=item L<AnyEvent::Handle::UDP>
		1149
		1150	Here be danger!
		1151
		1152	As Pauli would put it, "Not only is it not right, it's not even wrong!" -
		1153	there are so many things wrong with AnyEvent::Handle::UDP, most notably
		1154	its use of a stream-based API with a protocol that isn't streamable, that
		1155	the only way to improve it is to delete it.
		1156
		1157	It features data corruption (but typically only under load) and general
		1158	confusion. On top, the author is not only clueless about UDP but also
		1159	fact-resistant - some gems of his understanding: "connect doesn't work
		1160	with UDP", "UDP packets are not IP packets", "UDP only has datagrams, not
		1161	packets", "I don't need to implement proper error checking as UDP doesn't
		1162	support error checking" and so on - he doesn't even understand what's
		1163	wrong with his module when it is explained to him.
		1164
757	=item L<AnyEvent::HTTP>	1165	=item L<AnyEvent::DBI>
758		1166
759	A simple-to-use HTTP library that is capable of making a lot of concurrent	1167	Executes L<DBI> requests asynchronously in a proxy process for you,
760	HTTP requests.	1168	notifying you in an event-based way when the operation is finished.
		1169
		1170	=item L<AnyEvent::AIO>
		1171
		1172	Truly asynchronous (as opposed to non-blocking) I/O, should be in the
		1173	toolbox of every event programmer. AnyEvent::AIO transparently fuses
		1174	L<IO::AIO> and AnyEvent together, giving AnyEvent access to event-based
		1175	file I/O, and much more.
761		1176
762	=item L<AnyEvent::HTTPD>	1177	=item L<AnyEvent::HTTPD>
763		1178
764	Provides a simple web application server framework.	1179	A simple embedded webserver.
765		1180
766	=item L<AnyEvent::FastPing>	1181	=item L<AnyEvent::FastPing>
767		1182
768	The fastest ping in the west.	1183	The fastest ping in the west.
769		1184
770	=item L<AnyEvent::DBI>
771
772	Executes L<DBI> requests asynchronously in a proxy process.
773
774	=item L<AnyEvent::AIO>
775
776	Truly asynchronous I/O, should be in the toolbox of every event
777	programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
778	together.
779
780	=item L<AnyEvent::BDB>
781
782	Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
783	L<BDB> and AnyEvent together.
784
785	=item L<AnyEvent::GPSD>
786
787	A non-blocking interface to gpsd, a daemon delivering GPS information.
788
789	=item L<AnyEvent::IGS>
790
791	A non-blocking interface to the Internet Go Server protocol (used by
792	L<App::IGS>).
793
794	=item L<Net::IRC3>
795
796	AnyEvent based IRC client module family.
797
798	=item L<Net::XMPP2>
799
800	AnyEvent based XMPP (Jabber protocol) module family.
801
802	=item L<Net::FCP>
803
804	AnyEvent-based implementation of the Freenet Client Protocol, birthplace
805	of AnyEvent.
806
807	=item L<Event::ExecFlow>
808
809	High level API for event-based execution flow control.
810
811	=item L<Coro>	1185	=item L<Coro>
812		1186
813	Has special support for AnyEvent via L<Coro::AnyEvent>.	1187	Has special support for AnyEvent via L<Coro::AnyEvent>.
814		1188
815	=item L<IO::Lambda>
816
817	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
818
819	=back	1189	=back
820		1190
821	=cut	1191	=cut
822		1192
823	package AnyEvent;	1193	package AnyEvent;
824		1194
825	no warnings;	1195	# basically a tuned-down version of common::sense
826	use strict;	1196	sub common_sense {
		1197	# from common:.sense 3.4
		1198	${^WARNING_BITS} ^= ${^WARNING_BITS} ^ "\x3c\x3f\x33\x00\x0f\xf0\x0f\xc0\xf0\xfc\x33\x00";
		1199	# use strict vars subs - NO UTF-8, as Util.pm doesn't like this atm. (uts46data.pl)
		1200	$^H |= 0x00000600;
		1201	}
827		1202
		1203	BEGIN { AnyEvent::common_sense }
		1204
828	use Carp;	1205	use Carp ();
829		1206
830	our $VERSION = 4.2;	1207	our $VERSION = '5.34';
831	our $MODEL;	1208	our $MODEL;
832		1209
833	our $AUTOLOAD;	1210	our $AUTOLOAD;
834	our @ISA;	1211	our @ISA;
835		1212
836	our @REGISTRY;	1213	our @REGISTRY;
837		1214
838	our $WIN32;	1215	our $VERBOSE;
839		1216
840	BEGIN {	1217	BEGIN {
841	my $win32 = ! ! ($^O =~ /mswin32/i);	1218	require "AnyEvent/constants.pl";
842	eval "sub WIN32(){ $win32 }";
843	}
844		1219
		1220	eval "sub TAINT (){" . (${^TAINT}*1) . "}";
		1221
		1222	delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV}
		1223	if ${^TAINT};
		1224
845	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;	1225	$VERBOSE = $ENV{PERL_ANYEVENT_VERBOSE}*1;
		1226
		1227	}
		1228
		1229	our $MAX_SIGNAL_LATENCY = 10;
846		1230
847	our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred	1231	our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred
848		1232
849	{	1233	{
850	my $idx;	1234	my $idx;
…		…
852	for reverse split /\s*,\s*/,	1236	for reverse split /\s*,\s*/,
853	$ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";	1237	$ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";
854	}	1238	}
855		1239
856	my @models = (	1240	my @models = (
857	[EV:: => AnyEvent::Impl::EV::],	1241	[EV:: => AnyEvent::Impl::EV:: , 1],
858	[Event:: => AnyEvent::Impl::Event::],	1242	[AnyEvent::Loop:: => AnyEvent::Impl::Perl:: , 1],
859	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
860	# everything below here will not be autoprobed	1243	# everything below here will not (normally) be autoprobed
861	# as the pureperl backend should work everywhere	1244	# as the pure perl backend should work everywhere
862	# and is usually faster	1245	# and is usually faster
		1246	[Event:: => AnyEvent::Impl::Event::, 1],
		1247	[Glib:: => AnyEvent::Impl::Glib:: , 1], # becomes extremely slow with many watchers
		1248	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
		1249	[Irssi:: => AnyEvent::Impl::Irssi::], # Irssi has a bogus "Event" package
863	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles	1250	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
864	[Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers
865	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
866	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program	1251	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program
867	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza	1252	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
868	[Wx:: => AnyEvent::Impl::POE::],	1253	[Wx:: => AnyEvent::Impl::POE::],
869	[Prima:: => AnyEvent::Impl::POE::],	1254	[Prima:: => AnyEvent::Impl::POE::],
		1255	[IO::Async::Loop:: => AnyEvent::Impl::IOAsync::],
		1256	[Cocoa::EventLoop:: => AnyEvent::Impl::Cocoa::],
		1257	[FLTK:: => AnyEvent::Impl::FLTK::],
870	);	1258	);
871		1259
872	our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY);	1260	our %method = map +($_ => 1),
		1261	qw(io timer time now now_update signal child idle condvar DESTROY);
873		1262
874	our @post_detect;	1263	our @post_detect;
875		1264
876	sub post_detect(&) {	1265	sub post_detect(&) {
877	my ($cb) = @_;	1266	my ($cb) = @_;
878		1267
879	if ($MODEL) {
880	$cb->();
881
882	1
883	} else {
884	push @post_detect, $cb;	1268	push @post_detect, $cb;
885		1269
886	defined wantarray	1270	defined wantarray
887	? bless \$cb, "AnyEvent::Util::PostDetect"	1271	? bless \$cb, "AnyEvent::Util::postdetect"
888	: ()	1272	: ()
		1273	}
		1274
		1275	sub AnyEvent::Util::postdetect::DESTROY {
		1276	@post_detect = grep $_ != ${$_[0]}, @post_detect;
		1277	}
		1278
		1279	sub detect() {
		1280	# free some memory
		1281	*detect = sub () { $MODEL };
		1282
		1283	local $!; # for good measure
		1284	local $SIG{__DIE__};
		1285
		1286	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
		1287	my $model = "AnyEvent::Impl::$1";
		1288	if (eval "require $model") {
		1289	$MODEL = $model;
		1290	warn "AnyEvent: loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.\n" if $VERBOSE >= 2;
		1291	} else {
		1292	warn "AnyEvent: unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@" if $VERBOSE;
		1293	}
889	}	1294	}
890	}
891		1295
892	sub AnyEvent::Util::PostDetect::DESTROY {	1296	# check for already loaded models
893	@post_detect = grep $_ != ${$_[0]}, @post_detect;
894	}
895
896	sub detect() {
897	unless ($MODEL) {	1297	unless ($MODEL) {
898	no strict 'refs';	1298	for (@REGISTRY, @models) {
899	local $SIG{__DIE__};	1299	my ($package, $model) = @$_;
900		1300	if (${"$package\::VERSION"} > 0) {
901	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
902	my $model = "AnyEvent::Impl::$1";
903	if (eval "require $model") {	1301	if (eval "require $model") {
904	$MODEL = $model;	1302	$MODEL = $model;
905	warn "AnyEvent: loaded model '$model' (forced by \$PERL_ANYEVENT_MODEL), using it.\n" if $verbose > 1;	1303	warn "AnyEvent: autodetected model '$model', using it.\n" if $VERBOSE >= 2;
906	} else {	1304	last;
907	warn "AnyEvent: unable to load model '$model' (from \$PERL_ANYEVENT_MODEL):\n$@" if $verbose;	1305	}
908	}	1306	}
909	}	1307	}
910		1308
911	# check for already loaded models
912	unless ($MODEL) {	1309	unless ($MODEL) {
		1310	# try to autoload a model
913	for (@REGISTRY, @models) {	1311	for (@REGISTRY, @models) {
914	my ($package, $model) = @$_;	1312	my ($package, $model, $autoload) = @$_;
		1313	if (
		1314	$autoload
		1315	and eval "require $package"
915	if (${"$package\::VERSION"} > 0) {	1316	and ${"$package\::VERSION"} > 0
916	if (eval "require $model") {	1317	and eval "require $model"
		1318	) {
917	$MODEL = $model;	1319	$MODEL = $model;
918	warn "AnyEvent: autodetected model '$model', using it.\n" if $verbose > 1;	1320	warn "AnyEvent: autoloaded model '$model', using it.\n" if $VERBOSE >= 2;
919	last;	1321	last;
920	}
921	}	1322	}
922	}	1323	}
923		1324
924	unless ($MODEL) {
925	# try to load a model
926
927	for (@REGISTRY, @models) {
928	my ($package, $model) = @$_;
929	if (eval "require $package"
930	and ${"$package\::VERSION"} > 0
931	and eval "require $model") {
932	$MODEL = $model;
933	warn "AnyEvent: autoprobed model '$model', using it.\n" if $verbose > 1;
934	last;
935	}
936	}
937
938	$MODEL	1325	$MODEL
939	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";	1326	or die "AnyEvent: backend autodetection failed - did you properly install AnyEvent?\n";
940	}
941	}	1327	}
942
943	unshift @ISA, $MODEL;
944	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
945
946	(shift @post_detect)->() while @post_detect;
947	}	1328	}
		1329
		1330	@models = (); # free probe data
		1331
		1332	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
		1333	unshift @ISA, $MODEL;
		1334
		1335	# now nuke some methods that are overridden by the backend.
		1336	# SUPER is not allowed.
		1337	for (qw(time signal child idle)) {
		1338	undef &{"AnyEvent::Base::$_"}
		1339	if defined &{"$MODEL\::$_"};
		1340	}
		1341
		1342	if ($ENV{PERL_ANYEVENT_STRICT}) {
		1343	eval { require AnyEvent::Strict };
		1344	warn "AnyEvent: cannot load AnyEvent::Strict: $@"
		1345	if $@ && $VERBOSE;
		1346	}
		1347
		1348	(shift @post_detect)->() while @post_detect;
		1349
		1350	*post_detect = sub(&) {
		1351	shift->();
		1352
		1353	undef
		1354	};
948		1355
949	$MODEL	1356	$MODEL
950	}	1357	}
951		1358
952	sub AUTOLOAD {	1359	sub AUTOLOAD {
953	(my $func = $AUTOLOAD) =~ s/.*://;	1360	(my $func = $AUTOLOAD) =~ s/.*://;
954		1361
955	$method{$func}	1362	$method{$func}
956	or croak "$func: not a valid method for AnyEvent objects";	1363	or Carp::croak "$func: not a valid AnyEvent class method";
957		1364
958	detect unless $MODEL;	1365	detect;
959		1366
960	my $class = shift;	1367	my $class = shift;
961	$class->$func (@_);	1368	$class->$func (@_);
962	}	1369	}
963		1370
		1371	our $POSTPONE_W;
		1372	our @POSTPONE;
		1373
		1374	sub _postpone_exec {
		1375	undef $POSTPONE_W;
		1376	(pop @POSTPONE)->()
		1377	while @POSTPONE;
		1378	}
		1379
		1380	sub postpone(&) {
		1381	push @POSTPONE, shift;
		1382
		1383	$POSTPONE_W ||= AE::timer (0, 0, \&_postpone_exec);
		1384
		1385	()
		1386	}
		1387
		1388	# utility function to dup a filehandle. this is used by many backends
		1389	# to support binding more than one watcher per filehandle (they usually
		1390	# allow only one watcher per fd, so we dup it to get a different one).
		1391	sub _dupfh($$;$$) {
		1392	my ($poll, $fh, $r, $w) = @_;
		1393
		1394	# cygwin requires the fh mode to be matching, unix doesn't
		1395	my ($rw, $mode) = $poll eq "r" ? ($r, "<&") : ($w, ">&");
		1396
		1397	open my $fh2, $mode, $fh
		1398	or die "AnyEvent->io: cannot dup() filehandle in mode '$poll': $!,";
		1399
		1400	# we assume CLOEXEC is already set by perl in all important cases
		1401
		1402	($fh2, $rw)
		1403	}
		1404
		1405	=head1 SIMPLIFIED AE API
		1406
		1407	Starting with version 5.0, AnyEvent officially supports a second, much
		1408	simpler, API that is designed to reduce the calling, typing and memory
		1409	overhead by using function call syntax and a fixed number of parameters.
		1410
		1411	See the L<AE> manpage for details.
		1412
		1413	=cut
		1414
		1415	package AE;
		1416
		1417	our $VERSION = $AnyEvent::VERSION;
		1418
		1419	# fall back to the main API by default - backends and AnyEvent::Base
		1420	# implementations can overwrite these.
		1421
		1422	sub io($$$) {
		1423	AnyEvent->io (fh => $_[0], poll => $_[1] ? "w" : "r", cb => $_[2])
		1424	}
		1425
		1426	sub timer($$$) {
		1427	AnyEvent->timer (after => $_[0], interval => $_[1], cb => $_[2])
		1428	}
		1429
		1430	sub signal($$) {
		1431	AnyEvent->signal (signal => $_[0], cb => $_[1])
		1432	}
		1433
		1434	sub child($$) {
		1435	AnyEvent->child (pid => $_[0], cb => $_[1])
		1436	}
		1437
		1438	sub idle($) {
		1439	AnyEvent->idle (cb => $_[0])
		1440	}
		1441
		1442	sub cv(;&) {
		1443	AnyEvent->condvar (@_ ? (cb => $_[0]) : ())
		1444	}
		1445
		1446	sub now() {
		1447	AnyEvent->now
		1448	}
		1449
		1450	sub now_update() {
		1451	AnyEvent->now_update
		1452	}
		1453
		1454	sub time() {
		1455	AnyEvent->time
		1456	}
		1457
964	package AnyEvent::Base;	1458	package AnyEvent::Base;
965		1459
966	# default implementation for now and time	1460	# default implementations for many methods
967		1461
968	use Time::HiRes ();	1462	sub time {
		1463	eval q{ # poor man's autoloading {}
		1464	# probe for availability of Time::HiRes
		1465	if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {
		1466	warn "AnyEvent: using Time::HiRes for sub-second timing accuracy.\n" if $VERBOSE >= 8;
		1467	*AE::time = \&Time::HiRes::time;
		1468	# if (eval "use POSIX (); (POSIX::times())...
		1469	} else {
		1470	warn "AnyEvent: using built-in time(), WARNING, no sub-second resolution!\n" if $VERBOSE;
		1471	*AE::time = sub (){ time }; # epic fail
		1472	}
969		1473
970	sub time { Time::HiRes::time }	1474	*time = sub { AE::time }; # different prototypes
971	sub now { Time::HiRes::time }	1475	};
		1476	die if $@;
		1477
		1478	&time
		1479	}
		1480
		1481	*now = \&time;
		1482
		1483	sub now_update { }
		1484
		1485	sub _poll {
		1486	Carp::croak "$AnyEvent::MODEL does not support blocking waits. Caught";
		1487	}
972		1488
973	# default implementation for ->condvar	1489	# default implementation for ->condvar
		1490	# in fact, the default should not be overwritten
974		1491
975	sub condvar {	1492	sub condvar {
		1493	eval q{ # poor man's autoloading {}
		1494	*condvar = sub {
976	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::	1495	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar"
		1496	};
		1497
		1498	*AE::cv = sub (;&) {
		1499	bless { @_ ? (_ae_cb => shift) : () }, "AnyEvent::CondVar"
		1500	};
		1501	};
		1502	die if $@;
		1503
		1504	&condvar
977	}	1505	}
978		1506
979	# default implementation for ->signal	1507	# default implementation for ->signal
980		1508
981	our %SIG_CB;	1509	our $HAVE_ASYNC_INTERRUPT;
		1510
		1511	sub _have_async_interrupt() {
		1512	$HAVE_ASYNC_INTERRUPT = 1*(!$ENV{PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT}
		1513	&& eval "use Async::Interrupt 1.02 (); 1")
		1514	unless defined $HAVE_ASYNC_INTERRUPT;
		1515
		1516	$HAVE_ASYNC_INTERRUPT
		1517	}
		1518
		1519	our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO);
		1520	our (%SIG_ASY, %SIG_ASY_W);
		1521	our ($SIG_COUNT, $SIG_TW);
		1522
		1523	# install a dummy wakeup watcher to reduce signal catching latency
		1524	# used by Impls
		1525	sub _sig_add() {
		1526	unless ($SIG_COUNT++) {
		1527	# try to align timer on a full-second boundary, if possible
		1528	my $NOW = AE::now;
		1529
		1530	$SIG_TW = AE::timer
		1531	$MAX_SIGNAL_LATENCY - ($NOW - int $NOW),
		1532	$MAX_SIGNAL_LATENCY,
		1533	sub { } # just for the PERL_ASYNC_CHECK
		1534	;
		1535	}
		1536	}
		1537
		1538	sub _sig_del {
		1539	undef $SIG_TW
		1540	unless --$SIG_COUNT;
		1541	}
		1542
		1543	our $_sig_name_init; $_sig_name_init = sub {
		1544	eval q{ # poor man's autoloading {}
		1545	undef $_sig_name_init;
		1546
		1547	if (_have_async_interrupt) {
		1548	*sig2num = \&Async::Interrupt::sig2num;
		1549	*sig2name = \&Async::Interrupt::sig2name;
		1550	} else {
		1551	require Config;
		1552
		1553	my %signame2num;
		1554	@signame2num{ split ' ', $Config::Config{sig_name} }
		1555	= split ' ', $Config::Config{sig_num};
		1556
		1557	my @signum2name;
		1558	@signum2name[values %signame2num] = keys %signame2num;
		1559
		1560	*sig2num = sub($) {
		1561	$_[0] > 0 ? shift : $signame2num{+shift}
		1562	};
		1563	*sig2name = sub ($) {
		1564	$_[0] > 0 ? $signum2name[+shift] : shift
		1565	};
		1566	}
		1567	};
		1568	die if $@;
		1569	};
		1570
		1571	sub sig2num ($) { &$_sig_name_init; &sig2num }
		1572	sub sig2name($) { &$_sig_name_init; &sig2name }
982		1573
983	sub signal {	1574	sub signal {
		1575	eval q{ # poor man's autoloading {}
		1576	# probe for availability of Async::Interrupt
		1577	if (_have_async_interrupt) {
		1578	warn "AnyEvent: using Async::Interrupt for race-free signal handling.\n" if $VERBOSE >= 8;
		1579
		1580	$SIGPIPE_R = new Async::Interrupt::EventPipe;
		1581	$SIG_IO = AE::io $SIGPIPE_R->fileno, 0, \&_signal_exec;
		1582
		1583	} else {
		1584	warn "AnyEvent: using emulated perl signal handling with latency timer.\n" if $VERBOSE >= 8;
		1585
		1586	if (AnyEvent::WIN32) {
		1587	require AnyEvent::Util;
		1588
		1589	($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
		1590	AnyEvent::Util::fh_nonblocking ($SIGPIPE_R, 1) if $SIGPIPE_R;
		1591	AnyEvent::Util::fh_nonblocking ($SIGPIPE_W, 1) if $SIGPIPE_W; # just in case
		1592	} else {
		1593	pipe $SIGPIPE_R, $SIGPIPE_W;
		1594	fcntl $SIGPIPE_R, AnyEvent::F_SETFL, AnyEvent::O_NONBLOCK if $SIGPIPE_R;
		1595	fcntl $SIGPIPE_W, AnyEvent::F_SETFL, AnyEvent::O_NONBLOCK if $SIGPIPE_W; # just in case
		1596
		1597	# not strictly required, as $^F is normally 2, but let's make sure...
		1598	fcntl $SIGPIPE_R, AnyEvent::F_SETFD, AnyEvent::FD_CLOEXEC;
		1599	fcntl $SIGPIPE_W, AnyEvent::F_SETFD, AnyEvent::FD_CLOEXEC;
		1600	}
		1601
		1602	$SIGPIPE_R
		1603	or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n";
		1604
		1605	$SIG_IO = AE::io $SIGPIPE_R, 0, \&_signal_exec;
		1606	}
		1607
		1608	*signal = $HAVE_ASYNC_INTERRUPT
		1609	? sub {
984	my (undef, %arg) = @_;	1610	my (undef, %arg) = @_;
985		1611
		1612	# async::interrupt
986	my $signal = uc $arg{signal}	1613	my $signal = sig2num $arg{signal};
987	or Carp::croak "required option 'signal' is missing";
988
989	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};	1614	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};
		1615
		1616	$SIG_ASY{$signal} ||= new Async::Interrupt
		1617	cb => sub { undef $SIG_EV{$signal} },
		1618	signal => $signal,
		1619	pipe => [$SIGPIPE_R->filenos],
		1620	pipe_autodrain => 0,
		1621	;
		1622
		1623	bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
		1624	}
		1625	: sub {
		1626	my (undef, %arg) = @_;
		1627
		1628	# pure perl
		1629	my $signal = sig2name $arg{signal};
		1630	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};
		1631
990	$SIG{$signal} ||= sub {	1632	$SIG{$signal} ||= sub {
		1633	local $!;
		1634	syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV;
		1635	undef $SIG_EV{$signal};
		1636	};
		1637
		1638	# can't do signal processing without introducing races in pure perl,
		1639	# so limit the signal latency.
		1640	_sig_add;
		1641
		1642	bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
		1643	}
		1644	;
		1645
		1646	*AnyEvent::Base::signal::DESTROY = sub {
		1647	my ($signal, $cb) = @{$_[0]};
		1648
		1649	_sig_del;
		1650
		1651	delete $SIG_CB{$signal}{$cb};
		1652
		1653	$HAVE_ASYNC_INTERRUPT
		1654	? delete $SIG_ASY{$signal}
		1655	: # delete doesn't work with older perls - they then
		1656	# print weird messages, or just unconditionally exit
		1657	# instead of getting the default action.
		1658	undef $SIG{$signal}
		1659	unless keys %{ $SIG_CB{$signal} };
		1660	};
		1661
		1662	*_signal_exec = sub {
		1663	$HAVE_ASYNC_INTERRUPT
		1664	? $SIGPIPE_R->drain
		1665	: sysread $SIGPIPE_R, (my $dummy), 9;
		1666
		1667	while (%SIG_EV) {
		1668	for (keys %SIG_EV) {
		1669	delete $SIG_EV{$_};
991	$_->() for values %{ $SIG_CB{$signal} || {} };	1670	$_->() for values %{ $SIG_CB{$_} || {} };
		1671	}
		1672	}
		1673	};
992	};	1674	};
		1675	die if $@;
993		1676
994	bless [$signal, $arg{cb}], "AnyEvent::Base::Signal"	1677	&signal
995	}
996
997	sub AnyEvent::Base::Signal::DESTROY {
998	my ($signal, $cb) = @{$_[0]};
999
1000	delete $SIG_CB{$signal}{$cb};
1001
1002	delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
1003	}	1678	}
1004		1679
1005	# default implementation for ->child	1680	# default implementation for ->child
1006		1681
1007	our %PID_CB;	1682	our %PID_CB;
1008	our $CHLD_W;	1683	our $CHLD_W;
1009	our $CHLD_DELAY_W;	1684	our $CHLD_DELAY_W;
1010	our $PID_IDLE;
1011	our $WNOHANG;
1012		1685
1013	sub _child_wait {	1686	# used by many Impl's
1014	while (0 < (my $pid = waitpid -1, $WNOHANG)) {	1687	sub _emit_childstatus($$) {
		1688	my (undef, $rpid, $rstatus) = @_;
		1689
		1690	$_->($rpid, $rstatus)
1015	$_->($pid, $?) for (values %{ $PID_CB{$pid} || {} }),	1691	for values %{ $PID_CB{$rpid} || {} },
1016	(values %{ $PID_CB{0} || {} });	1692	values %{ $PID_CB{0} || {} };
1017	}
1018
1019	undef $PID_IDLE;
1020	}
1021
1022	sub _sigchld {
1023	# make sure we deliver these changes "synchronous" with the event loop.
1024	$CHLD_DELAY_W ||= AnyEvent->timer (after => 0, cb => sub {
1025	undef $CHLD_DELAY_W;
1026	&_child_wait;
1027	});
1028	}	1693	}
1029		1694
1030	sub child {	1695	sub child {
		1696	eval q{ # poor man's autoloading {}
		1697	*_sigchld = sub {
		1698	my $pid;
		1699
		1700	AnyEvent->_emit_childstatus ($pid, $?)
		1701	while ($pid = waitpid -1, WNOHANG) > 0;
		1702	};
		1703
		1704	*child = sub {
1031	my (undef, %arg) = @_;	1705	my (undef, %arg) = @_;
1032		1706
1033	defined (my $pid = $arg{pid} + 0)	1707	my $pid = $arg{pid};
1034	or Carp::croak "required option 'pid' is missing";	1708	my $cb = $arg{cb};
1035		1709
1036	$PID_CB{$pid}{$arg{cb}} = $arg{cb};	1710	$PID_CB{$pid}{$cb+0} = $cb;
1037		1711
1038	unless ($WNOHANG) {
1039	$WNOHANG = eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;
1040	}
1041
1042	unless ($CHLD_W) {	1712	unless ($CHLD_W) {
1043	$CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);	1713	$CHLD_W = AE::signal CHLD => \&_sigchld;
1044	# child could be a zombie already, so make at least one round	1714	# child could be a zombie already, so make at least one round
1045	&_sigchld;	1715	&_sigchld;
1046	}	1716	}
1047		1717
1048	bless [$pid, $arg{cb}], "AnyEvent::Base::Child"	1718	bless [$pid, $cb+0], "AnyEvent::Base::child"
1049	}	1719	};
1050		1720
1051	sub AnyEvent::Base::Child::DESTROY {	1721	*AnyEvent::Base::child::DESTROY = sub {
1052	my ($pid, $cb) = @{$_[0]};	1722	my ($pid, $icb) = @{$_[0]};
1053		1723
1054	delete $PID_CB{$pid}{$cb};	1724	delete $PID_CB{$pid}{$icb};
1055	delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };	1725	delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
1056		1726
1057	undef $CHLD_W unless keys %PID_CB;	1727	undef $CHLD_W unless keys %PID_CB;
		1728	};
		1729	};
		1730	die if $@;
		1731
		1732	&child
		1733	}
		1734
		1735	# idle emulation is done by simply using a timer, regardless
		1736	# of whether the process is idle or not, and not letting
		1737	# the callback use more than 50% of the time.
		1738	sub idle {
		1739	eval q{ # poor man's autoloading {}
		1740	*idle = sub {
		1741	my (undef, %arg) = @_;
		1742
		1743	my ($cb, $w, $rcb) = $arg{cb};
		1744
		1745	$rcb = sub {
		1746	if ($cb) {
		1747	$w = _time;
		1748	&$cb;
		1749	$w = _time - $w;
		1750
		1751	# never use more then 50% of the time for the idle watcher,
		1752	# within some limits
		1753	$w = 0.0001 if $w < 0.0001;
		1754	$w = 5 if $w > 5;
		1755
		1756	$w = AE::timer $w, 0, $rcb;
		1757	} else {
		1758	# clean up...
		1759	undef $w;
		1760	undef $rcb;
		1761	}
		1762	};
		1763
		1764	$w = AE::timer 0.05, 0, $rcb;
		1765
		1766	bless \\$cb, "AnyEvent::Base::idle"
		1767	};
		1768
		1769	*AnyEvent::Base::idle::DESTROY = sub {
		1770	undef $${$_[0]};
		1771	};
		1772	};
		1773	die if $@;
		1774
		1775	&idle
1058	}	1776	}
1059		1777
1060	package AnyEvent::CondVar;	1778	package AnyEvent::CondVar;
1061		1779
1062	our @ISA = AnyEvent::CondVar::Base::;	1780	our @ISA = AnyEvent::CondVar::Base::;
1063		1781
		1782	# only to be used for subclassing
		1783	sub new {
		1784	my $class = shift;
		1785	bless AnyEvent->condvar (@_), $class
		1786	}
		1787
1064	package AnyEvent::CondVar::Base;	1788	package AnyEvent::CondVar::Base;
1065		1789
1066	use overload	1790	#use overload
1067	'&{}' => sub { my $self = shift; sub { $self->send (@_) } },	1791	# '&{}' => sub { my $self = shift; sub { $self->send (@_) } },
1068	fallback => 1;	1792	# fallback => 1;
		1793
		1794	# save 300+ kilobytes by dirtily hardcoding overloading
		1795	${"AnyEvent::CondVar::Base::OVERLOAD"}{dummy}++; # Register with magic by touching.
		1796	*{'AnyEvent::CondVar::Base::()'} = sub { }; # "Make it findable via fetchmethod."
		1797	*{'AnyEvent::CondVar::Base::(&{}'} = sub { my $self = shift; sub { $self->send (@_) } }; # &{}
		1798	${'AnyEvent::CondVar::Base::()'} = 1; # fallback
		1799
		1800	our $WAITING;
1069		1801
1070	sub _send {	1802	sub _send {
1071	# nop	1803	# nop
		1804	}
		1805
		1806	sub _wait {
		1807	AnyEvent->_poll until $_[0]{_ae_sent};
1072	}	1808	}
1073		1809
1074	sub send {	1810	sub send {
1075	my $cv = shift;	1811	my $cv = shift;
1076	$cv->{_ae_sent} = [@_];	1812	$cv->{_ae_sent} = [@_];
…		…
1085		1821
1086	sub ready {	1822	sub ready {
1087	$_[0]{_ae_sent}	1823	$_[0]{_ae_sent}
1088	}	1824	}
1089		1825
1090	sub _wait {
1091	AnyEvent->one_event while !$_[0]{_ae_sent};
1092	}
1093
1094	sub recv {	1826	sub recv {
		1827	unless ($_[0]{_ae_sent}) {
		1828	$WAITING
		1829	and Carp::croak "AnyEvent::CondVar: recursive blocking wait attempted";
		1830
		1831	local $WAITING = 1;
1095	$_[0]->_wait;	1832	$_[0]->_wait;
		1833	}
1096		1834
1097	Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak};	1835	$_[0]{_ae_croak}
1098	wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0]	1836	and Carp::croak $_[0]{_ae_croak};
		1837
		1838	wantarray
		1839	? @{ $_[0]{_ae_sent} }
		1840	: $_[0]{_ae_sent}[0]
1099	}	1841	}
1100		1842
1101	sub cb {	1843	sub cb {
1102	$_[0]{_ae_cb} = $_[1] if @_ > 1;	1844	my $cv = shift;
		1845
		1846	@_
		1847	and $cv->{_ae_cb} = shift
		1848	and $cv->{_ae_sent}
		1849	and (delete $cv->{_ae_cb})->($cv);
		1850
1103	$_[0]{_ae_cb}	1851	$cv->{_ae_cb}
1104	}	1852	}
1105		1853
1106	sub begin {	1854	sub begin {
1107	++$_[0]{_ae_counter};	1855	++$_[0]{_ae_counter};
1108	$_[0]{_ae_end_cb} = $_[1] if @_ > 1;	1856	$_[0]{_ae_end_cb} = $_[1] if @_ > 1;
…		…
1113	&{ $_[0]{_ae_end_cb} || sub { $_[0]->send } };	1861	&{ $_[0]{_ae_end_cb} || sub { $_[0]->send } };
1114	}	1862	}
1115		1863
1116	# undocumented/compatibility with pre-3.4	1864	# undocumented/compatibility with pre-3.4
1117	*broadcast = \&send;	1865	*broadcast = \&send;
1118	*wait = \&_wait;	1866	*wait = \&recv;
		1867
		1868	=head1 ERROR AND EXCEPTION HANDLING
		1869
		1870	In general, AnyEvent does not do any error handling - it relies on the
		1871	caller to do that if required. The L<AnyEvent::Strict> module (see also
		1872	the C<PERL_ANYEVENT_STRICT> environment variable, below) provides strict
		1873	checking of all AnyEvent methods, however, which is highly useful during
		1874	development.
		1875
		1876	As for exception handling (i.e. runtime errors and exceptions thrown while
		1877	executing a callback), this is not only highly event-loop specific, but
		1878	also not in any way wrapped by this module, as this is the job of the main
		1879	program.
		1880
		1881	The pure perl event loop simply re-throws the exception (usually
		1882	within C<< condvar->recv >>), the L<Event> and L<EV> modules call C<<
		1883	$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and
		1884	so on.
		1885
		1886	=head1 ENVIRONMENT VARIABLES
		1887
		1888	The following environment variables are used by this module or its
		1889	submodules.
		1890
		1891	Note that AnyEvent will remove I<all> environment variables starting with
		1892	C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
		1893	enabled.
		1894
		1895	=over 4
		1896
		1897	=item C<PERL_ANYEVENT_VERBOSE>
		1898
		1899	By default, AnyEvent will be completely silent except in fatal
		1900	conditions. You can set this environment variable to make AnyEvent more
		1901	talkative.
		1902
		1903	When set to C<1> or higher, causes AnyEvent to warn about unexpected
		1904	conditions, such as not being able to load the event model specified by
		1905	C<PERL_ANYEVENT_MODEL>.
		1906
		1907	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
		1908	model it chooses.
		1909
		1910	When set to C<8> or higher, then AnyEvent will report extra information on
		1911	which optional modules it loads and how it implements certain features.
		1912
		1913	=item C<PERL_ANYEVENT_STRICT>
		1914
		1915	AnyEvent does not do much argument checking by default, as thorough
		1916	argument checking is very costly. Setting this variable to a true value
		1917	will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
		1918	check the arguments passed to most method calls. If it finds any problems,
		1919	it will croak.
		1920
		1921	In other words, enables "strict" mode.
		1922
		1923	Unlike C<use strict> (or its modern cousin, C<< use L<common::sense>
		1924	>>, it is definitely recommended to keep it off in production. Keeping
		1925	C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs
		1926	can be very useful, however.
		1927
		1928	=item C<PERL_ANYEVENT_MODEL>
		1929
		1930	This can be used to specify the event model to be used by AnyEvent, before
		1931	auto detection and -probing kicks in. It must be a string consisting
		1932	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
		1933	and the resulting module name is loaded and if the load was successful,
		1934	used as event model. If it fails to load AnyEvent will proceed with
		1935	auto detection and -probing.
		1936
		1937	This functionality might change in future versions.
		1938
		1939	For example, to force the pure perl model (L<AnyEvent::Loop::Perl>) you
		1940	could start your program like this:
		1941
		1942	PERL_ANYEVENT_MODEL=Perl perl ...
		1943
		1944	=item C<PERL_ANYEVENT_PROTOCOLS>
		1945
		1946	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
		1947	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
		1948	of auto probing).
		1949
		1950	Must be set to a comma-separated list of protocols or address families,
		1951	current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
		1952	used, and preference will be given to protocols mentioned earlier in the
		1953	list.
		1954
		1955	This variable can effectively be used for denial-of-service attacks
		1956	against local programs (e.g. when setuid), although the impact is likely
		1957	small, as the program has to handle conenction and other failures anyways.
		1958
		1959	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
		1960	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
		1961	- only support IPv4, never try to resolve or contact IPv6
		1962	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
		1963	IPv6, but prefer IPv6 over IPv4.
		1964
		1965	=item C<PERL_ANYEVENT_EDNS0>
		1966
		1967	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
		1968	for DNS. This extension is generally useful to reduce DNS traffic, but
		1969	some (broken) firewalls drop such DNS packets, which is why it is off by
		1970	default.
		1971
		1972	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
		1973	EDNS0 in its DNS requests.
		1974
		1975	=item C<PERL_ANYEVENT_MAX_FORKS>
		1976
		1977	The maximum number of child processes that C<AnyEvent::Util::fork_call>
		1978	will create in parallel.
		1979
		1980	=item C<PERL_ANYEVENT_MAX_OUTSTANDING_DNS>
		1981
		1982	The default value for the C<max_outstanding> parameter for the default DNS
		1983	resolver - this is the maximum number of parallel DNS requests that are
		1984	sent to the DNS server.
		1985
		1986	=item C<PERL_ANYEVENT_RESOLV_CONF>
		1987
		1988	The file to use instead of F</etc/resolv.conf> (or OS-specific
		1989	configuration) in the default resolver. When set to the empty string, no
		1990	default config will be used.
		1991
		1992	=item C<PERL_ANYEVENT_CA_FILE>, C<PERL_ANYEVENT_CA_PATH>.
		1993
		1994	When neither C<ca_file> nor C<ca_path> was specified during
		1995	L<AnyEvent::TLS> context creation, and either of these environment
		1996	variables exist, they will be used to specify CA certificate locations
		1997	instead of a system-dependent default.
		1998
		1999	=item C<PERL_ANYEVENT_AVOID_GUARD> and C<PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT>
		2000
		2001	When these are set to C<1>, then the respective modules are not
		2002	loaded. Mostly good for testing AnyEvent itself.
		2003
		2004	=back
1119		2005
1120	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE	2006	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
1121		2007
1122	This is an advanced topic that you do not normally need to use AnyEvent in	2008	This is an advanced topic that you do not normally need to use AnyEvent in
1123	a module. This section is only of use to event loop authors who want to	2009	a module. This section is only of use to event loop authors who want to
…		…
1157		2043
1158	I<rxvt-unicode> also cheats a bit by not providing blocking access to	2044	I<rxvt-unicode> also cheats a bit by not providing blocking access to
1159	condition variables: code blocking while waiting for a condition will	2045	condition variables: code blocking while waiting for a condition will
1160	C<die>. This still works with most modules/usages, and blocking calls must	2046	C<die>. This still works with most modules/usages, and blocking calls must
1161	not be done in an interactive application, so it makes sense.	2047	not be done in an interactive application, so it makes sense.
1162
1163	=head1 ENVIRONMENT VARIABLES
1164
1165	The following environment variables are used by this module:
1166
1167	=over 4
1168
1169	=item C<PERL_ANYEVENT_VERBOSE>
1170
1171	By default, AnyEvent will be completely silent except in fatal
1172	conditions. You can set this environment variable to make AnyEvent more
1173	talkative.
1174
1175	When set to C<1> or higher, causes AnyEvent to warn about unexpected
1176	conditions, such as not being able to load the event model specified by
1177	C<PERL_ANYEVENT_MODEL>.
1178
1179	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1180	model it chooses.
1181
1182	=item C<PERL_ANYEVENT_MODEL>
1183
1184	This can be used to specify the event model to be used by AnyEvent, before
1185	auto detection and -probing kicks in. It must be a string consisting
1186	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
1187	and the resulting module name is loaded and if the load was successful,
1188	used as event model. If it fails to load AnyEvent will proceed with
1189	auto detection and -probing.
1190
1191	This functionality might change in future versions.
1192
1193	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1194	could start your program like this:
1195
1196	PERL_ANYEVENT_MODEL=Perl perl ...
1197
1198	=item C<PERL_ANYEVENT_PROTOCOLS>
1199
1200	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1201	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
1202	of auto probing).
1203
1204	Must be set to a comma-separated list of protocols or address families,
1205	current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
1206	used, and preference will be given to protocols mentioned earlier in the
1207	list.
1208
1209	This variable can effectively be used for denial-of-service attacks
1210	against local programs (e.g. when setuid), although the impact is likely
1211	small, as the program has to handle connection errors already-
1212
1213	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1214	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1215	- only support IPv4, never try to resolve or contact IPv6
1216	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1217	IPv6, but prefer IPv6 over IPv4.
1218
1219	=item C<PERL_ANYEVENT_EDNS0>
1220
1221	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
1222	for DNS. This extension is generally useful to reduce DNS traffic, but
1223	some (broken) firewalls drop such DNS packets, which is why it is off by
1224	default.
1225
1226	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1227	EDNS0 in its DNS requests.
1228
1229	=item C<PERL_ANYEVENT_MAX_FORKS>
1230
1231	The maximum number of child processes that C<AnyEvent::Util::fork_call>
1232	will create in parallel.
1233
1234	=back
1235		2048
1236	=head1 EXAMPLE PROGRAM	2049	=head1 EXAMPLE PROGRAM
1237		2050
1238	The following program uses an I/O watcher to read data from STDIN, a timer	2051	The following program uses an I/O watcher to read data from STDIN, a timer
1239	to display a message once per second, and a condition variable to quit the	2052	to display a message once per second, and a condition variable to quit the
…		…
1252	warn "read: $input\n"; # output what has been read	2065	warn "read: $input\n"; # output what has been read
1253	$cv->send if $input =~ /^q/i; # quit program if /^q/i	2066	$cv->send if $input =~ /^q/i; # quit program if /^q/i
1254	},	2067	},
1255	);	2068	);
1256		2069
1257	my $time_watcher; # can only be used once
1258
1259	sub new_timer {
1260	$timer = AnyEvent->timer (after => 1, cb => sub {	2070	my $time_watcher = AnyEvent->timer (after => 1, interval => 1, cb => sub {
1261	warn "timeout\n"; # print 'timeout' about every second	2071	warn "timeout\n"; # print 'timeout' at most every second
1262	&new_timer; # and restart the time
1263	});	2072	});
1264	}
1265
1266	new_timer; # create first timer
1267		2073
1268	$cv->recv; # wait until user enters /^q/i	2074	$cv->recv; # wait until user enters /^q/i
1269		2075
1270	=head1 REAL-WORLD EXAMPLE	2076	=head1 REAL-WORLD EXAMPLE
1271		2077
…		…
1344		2150
1345	The actual code goes further and collects all errors (C<die>s, exceptions)	2151	The actual code goes further and collects all errors (C<die>s, exceptions)
1346	that occurred during request processing. The C<result> method detects	2152	that occurred during request processing. The C<result> method detects
1347	whether an exception as thrown (it is stored inside the $txn object)	2153	whether an exception as thrown (it is stored inside the $txn object)
1348	and just throws the exception, which means connection errors and other	2154	and just throws the exception, which means connection errors and other
1349	problems get reported tot he code that tries to use the result, not in a	2155	problems get reported to the code that tries to use the result, not in a
1350	random callback.	2156	random callback.
1351		2157
1352	All of this enables the following usage styles:	2158	All of this enables the following usage styles:
1353		2159
1354	1. Blocking:	2160	1. Blocking:
…		…
1402	through AnyEvent. The benchmark creates a lot of timers (with a zero	2208	through AnyEvent. The benchmark creates a lot of timers (with a zero
1403	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,	2209	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,
1404	which it is), lets them fire exactly once and destroys them again.	2210	which it is), lets them fire exactly once and destroys them again.
1405		2211
1406	Source code for this benchmark is found as F<eg/bench> in the AnyEvent	2212	Source code for this benchmark is found as F<eg/bench> in the AnyEvent
1407	distribution.	2213	distribution. It uses the L<AE> interface, which makes a real difference
		2214	for the EV and Perl backends only.
1408		2215
1409	=head3 Explanation of the columns	2216	=head3 Explanation of the columns
1410		2217
1411	I<watcher> is the number of event watchers created/destroyed. Since	2218	I<watcher> is the number of event watchers created/destroyed. Since
1412	different event models feature vastly different performances, each event	2219	different event models feature vastly different performances, each event
…		…
1433	watcher.	2240	watcher.
1434		2241
1435	=head3 Results	2242	=head3 Results
1436		2243
1437	name watchers bytes create invoke destroy comment	2244	name watchers bytes create invoke destroy comment
1438	EV/EV 400000 244 0.56 0.46 0.31 EV native interface	2245	EV/EV 100000 223 0.47 0.43 0.27 EV native interface
1439	EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers	2246	EV/Any 100000 223 0.48 0.42 0.26 EV + AnyEvent watchers
1440	CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal	2247	Coro::EV/Any 100000 223 0.47 0.42 0.26 coroutines + Coro::Signal
1441	Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation	2248	Perl/Any 100000 431 2.70 0.74 0.92 pure perl implementation
1442	Event/Event 16000 516 31.88 31.30 0.85 Event native interface	2249	Event/Event 16000 516 31.16 31.84 0.82 Event native interface
1443	Event/Any 16000 590 35.75 31.42 1.08 Event + AnyEvent watchers	2250	Event/Any 16000 1203 42.61 34.79 1.80 Event + AnyEvent watchers
		2251	IOAsync/Any 16000 1911 41.92 27.45 16.81 via IO::Async::Loop::IO_Poll
		2252	IOAsync/Any 16000 1726 40.69 26.37 15.25 via IO::Async::Loop::Epoll
1444	Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour	2253	Glib/Any 16000 1118 89.00 12.57 51.17 quadratic behaviour
1445	Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers	2254	Tk/Any 2000 1346 20.96 10.75 8.00 SEGV with >> 2000 watchers
1446	POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event	2255	POE/Any 2000 6951 108.97 795.32 14.24 via POE::Loop::Event
1447	POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select	2256	POE/Any 2000 6648 94.79 774.40 575.51 via POE::Loop::Select
1448		2257
1449	=head3 Discussion	2258	=head3 Discussion
1450		2259
1451	The benchmark does I<not> measure scalability of the event loop very	2260	The benchmark does I<not> measure scalability of the event loop very
1452	well. For example, a select-based event loop (such as the pure perl one)	2261	well. For example, a select-based event loop (such as the pure perl one)
…		…
1464	benchmark machine, handling an event takes roughly 1600 CPU cycles with	2273	benchmark machine, handling an event takes roughly 1600 CPU cycles with
1465	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU	2274	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU
1466	cycles with POE.	2275	cycles with POE.
1467		2276
1468	C<EV> is the sole leader regarding speed and memory use, which are both	2277	C<EV> is the sole leader regarding speed and memory use, which are both
1469	maximal/minimal, respectively. Even when going through AnyEvent, it uses	2278	maximal/minimal, respectively. When using the L<AE> API there is zero
		2279	overhead (when going through the AnyEvent API create is about 5-6 times
		2280	slower, with other times being equal, so still uses far less memory than
1470	far less memory than any other event loop and is still faster than Event	2281	any other event loop and is still faster than Event natively).
1471	natively.
1472		2282
1473	The pure perl implementation is hit in a few sweet spots (both the	2283	The pure perl implementation is hit in a few sweet spots (both the
1474	constant timeout and the use of a single fd hit optimisations in the perl	2284	constant timeout and the use of a single fd hit optimisations in the perl
1475	interpreter and the backend itself). Nevertheless this shows that it	2285	interpreter and the backend itself). Nevertheless this shows that it
1476	adds very little overhead in itself. Like any select-based backend its	2286	adds very little overhead in itself. Like any select-based backend its
1477	performance becomes really bad with lots of file descriptors (and few of	2287	performance becomes really bad with lots of file descriptors (and few of
1478	them active), of course, but this was not subject of this benchmark.	2288	them active), of course, but this was not subject of this benchmark.
1479		2289
1480	The C<Event> module has a relatively high setup and callback invocation	2290	The C<Event> module has a relatively high setup and callback invocation
1481	cost, but overall scores in on the third place.	2291	cost, but overall scores in on the third place.
		2292
		2293	C<IO::Async> performs admirably well, about on par with C<Event>, even
		2294	when using its pure perl backend.
1482		2295
1483	C<Glib>'s memory usage is quite a bit higher, but it features a	2296	C<Glib>'s memory usage is quite a bit higher, but it features a
1484	faster callback invocation and overall ends up in the same class as	2297	faster callback invocation and overall ends up in the same class as
1485	C<Event>. However, Glib scales extremely badly, doubling the number of	2298	C<Event>. However, Glib scales extremely badly, doubling the number of
1486	watchers increases the processing time by more than a factor of four,	2299	watchers increases the processing time by more than a factor of four,
…		…
1547	In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100	2360	In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100
1548	(1%) are active. This mirrors the activity of large servers with many	2361	(1%) are active. This mirrors the activity of large servers with many
1549	connections, most of which are idle at any one point in time.	2362	connections, most of which are idle at any one point in time.
1550		2363
1551	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent	2364	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent
1552	distribution.	2365	distribution. It uses the L<AE> interface, which makes a real difference
		2366	for the EV and Perl backends only.
1553		2367
1554	=head3 Explanation of the columns	2368	=head3 Explanation of the columns
1555		2369
1556	I<sockets> is the number of sockets, and twice the number of "servers" (as	2370	I<sockets> is the number of sockets, and twice the number of "servers" (as
1557	each server has a read and write socket end).	2371	each server has a read and write socket end).
…		…
1564	it to another server. This includes deleting the old timeout and creating	2378	it to another server. This includes deleting the old timeout and creating
1565	a new one that moves the timeout into the future.	2379	a new one that moves the timeout into the future.
1566		2380
1567	=head3 Results	2381	=head3 Results
1568		2382
1569	name sockets create request	2383	name sockets create request
1570	EV 20000 69.01 11.16	2384	EV 20000 62.66 7.99
1571	Perl 20000 73.32 35.87	2385	Perl 20000 68.32 32.64
1572	Event 20000 212.62 257.32	2386	IOAsync 20000 174.06 101.15 epoll
1573	Glib 20000 651.16 1896.30	2387	IOAsync 20000 174.67 610.84 poll
		2388	Event 20000 202.69 242.91
		2389	Glib 20000 557.01 1689.52
1574	POE 20000 349.67 12317.24 uses POE::Loop::Event	2390	POE 20000 341.54 12086.32 uses POE::Loop::Event
1575		2391
1576	=head3 Discussion	2392	=head3 Discussion
1577		2393
1578	This benchmark I<does> measure scalability and overall performance of the	2394	This benchmark I<does> measure scalability and overall performance of the
1579	particular event loop.	2395	particular event loop.
…		…
1581	EV is again fastest. Since it is using epoll on my system, the setup time	2397	EV is again fastest. Since it is using epoll on my system, the setup time
1582	is relatively high, though.	2398	is relatively high, though.
1583		2399
1584	Perl surprisingly comes second. It is much faster than the C-based event	2400	Perl surprisingly comes second. It is much faster than the C-based event
1585	loops Event and Glib.	2401	loops Event and Glib.
		2402
		2403	IO::Async performs very well when using its epoll backend, and still quite
		2404	good compared to Glib when using its pure perl backend.
1586		2405
1587	Event suffers from high setup time as well (look at its code and you will	2406	Event suffers from high setup time as well (look at its code and you will
1588	understand why). Callback invocation also has a high overhead compared to	2407	understand why). Callback invocation also has a high overhead compared to
1589	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event	2408	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event
1590	uses select or poll in basically all documented configurations.	2409	uses select or poll in basically all documented configurations.
…		…
1653	=item * C-based event loops perform very well with small number of	2472	=item * C-based event loops perform very well with small number of
1654	watchers, as the management overhead dominates.	2473	watchers, as the management overhead dominates.
1655		2474
1656	=back	2475	=back
1657		2476
		2477	=head2 THE IO::Lambda BENCHMARK
		2478
		2479	Recently I was told about the benchmark in the IO::Lambda manpage, which
		2480	could be misinterpreted to make AnyEvent look bad. In fact, the benchmark
		2481	simply compares IO::Lambda with POE, and IO::Lambda looks better (which
		2482	shouldn't come as a surprise to anybody). As such, the benchmark is
		2483	fine, and mostly shows that the AnyEvent backend from IO::Lambda isn't
		2484	very optimal. But how would AnyEvent compare when used without the extra
		2485	baggage? To explore this, I wrote the equivalent benchmark for AnyEvent.
		2486
		2487	The benchmark itself creates an echo-server, and then, for 500 times,
		2488	connects to the echo server, sends a line, waits for the reply, and then
		2489	creates the next connection. This is a rather bad benchmark, as it doesn't
		2490	test the efficiency of the framework or much non-blocking I/O, but it is a
		2491	benchmark nevertheless.
		2492
		2493	name runtime
		2494	Lambda/select 0.330 sec
		2495	+ optimized 0.122 sec
		2496	Lambda/AnyEvent 0.327 sec
		2497	+ optimized 0.138 sec
		2498	Raw sockets/select 0.077 sec
		2499	POE/select, components 0.662 sec
		2500	POE/select, raw sockets 0.226 sec
		2501	POE/select, optimized 0.404 sec
		2502
		2503	AnyEvent/select/nb 0.085 sec
		2504	AnyEvent/EV/nb 0.068 sec
		2505	+state machine 0.134 sec
		2506
		2507	The benchmark is also a bit unfair (my fault): the IO::Lambda/POE
		2508	benchmarks actually make blocking connects and use 100% blocking I/O,
		2509	defeating the purpose of an event-based solution. All of the newly
		2510	written AnyEvent benchmarks use 100% non-blocking connects (using
		2511	AnyEvent::Socket::tcp_connect and the asynchronous pure perl DNS
		2512	resolver), so AnyEvent is at a disadvantage here, as non-blocking connects
		2513	generally require a lot more bookkeeping and event handling than blocking
		2514	connects (which involve a single syscall only).
		2515
		2516	The last AnyEvent benchmark additionally uses L<AnyEvent::Handle>, which
		2517	offers similar expressive power as POE and IO::Lambda, using conventional
		2518	Perl syntax. This means that both the echo server and the client are 100%
		2519	non-blocking, further placing it at a disadvantage.
		2520
		2521	As you can see, the AnyEvent + EV combination even beats the
		2522	hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl
		2523	backend easily beats IO::Lambda and POE.
		2524
		2525	And even the 100% non-blocking version written using the high-level (and
		2526	slow :) L<AnyEvent::Handle> abstraction beats both POE and IO::Lambda
		2527	higher level ("unoptimised") abstractions by a large margin, even though
		2528	it does all of DNS, tcp-connect and socket I/O in a non-blocking way.
		2529
		2530	The two AnyEvent benchmarks programs can be found as F<eg/ae0.pl> and
		2531	F<eg/ae2.pl> in the AnyEvent distribution, the remaining benchmarks are
		2532	part of the IO::Lambda distribution and were used without any changes.
		2533
		2534
		2535	=head1 SIGNALS
		2536
		2537	AnyEvent currently installs handlers for these signals:
		2538
		2539	=over 4
		2540
		2541	=item SIGCHLD
		2542
		2543	A handler for C<SIGCHLD> is installed by AnyEvent's child watcher
		2544	emulation for event loops that do not support them natively. Also, some
		2545	event loops install a similar handler.
		2546
		2547	Additionally, when AnyEvent is loaded and SIGCHLD is set to IGNORE, then
		2548	AnyEvent will reset it to default, to avoid losing child exit statuses.
		2549
		2550	=item SIGPIPE
		2551
		2552	A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef>
		2553	when AnyEvent gets loaded.
		2554
		2555	The rationale for this is that AnyEvent users usually do not really depend
		2556	on SIGPIPE delivery (which is purely an optimisation for shell use, or
		2557	badly-written programs), but C<SIGPIPE> can cause spurious and rare
		2558	program exits as a lot of people do not expect C<SIGPIPE> when writing to
		2559	some random socket.
		2560
		2561	The rationale for installing a no-op handler as opposed to ignoring it is
		2562	that this way, the handler will be restored to defaults on exec.
		2563
		2564	Feel free to install your own handler, or reset it to defaults.
		2565
		2566	=back
		2567
		2568	=cut
		2569
		2570	undef $SIG{CHLD}
		2571	if $SIG{CHLD} eq 'IGNORE';
		2572
		2573	$SIG{PIPE} = sub { }
		2574	unless defined $SIG{PIPE};
		2575
		2576	=head1 RECOMMENDED/OPTIONAL MODULES
		2577
		2578	One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and
		2579	its built-in modules) are required to use it.
		2580
		2581	That does not mean that AnyEvent won't take advantage of some additional
		2582	modules if they are installed.
		2583
		2584	This section explains which additional modules will be used, and how they
		2585	affect AnyEvent's operation.
		2586
		2587	=over 4
		2588
		2589	=item L<Async::Interrupt>
		2590
		2591	This slightly arcane module is used to implement fast signal handling: To
		2592	my knowledge, there is no way to do completely race-free and quick
		2593	signal handling in pure perl. To ensure that signals still get
		2594	delivered, AnyEvent will start an interval timer to wake up perl (and
		2595	catch the signals) with some delay (default is 10 seconds, look for
		2596	C<$AnyEvent::MAX_SIGNAL_LATENCY>).
		2597
		2598	If this module is available, then it will be used to implement signal
		2599	catching, which means that signals will not be delayed, and the event loop
		2600	will not be interrupted regularly, which is more efficient (and good for
		2601	battery life on laptops).
		2602
		2603	This affects not just the pure-perl event loop, but also other event loops
		2604	that have no signal handling on their own (e.g. Glib, Tk, Qt).
		2605
		2606	Some event loops (POE, Event, Event::Lib) offer signal watchers natively,
		2607	and either employ their own workarounds (POE) or use AnyEvent's workaround
		2608	(using C<$AnyEvent::MAX_SIGNAL_LATENCY>). Installing L<Async::Interrupt>
		2609	does nothing for those backends.
		2610
		2611	=item L<EV>
		2612
		2613	This module isn't really "optional", as it is simply one of the backend
		2614	event loops that AnyEvent can use. However, it is simply the best event
		2615	loop available in terms of features, speed and stability: It supports
		2616	the AnyEvent API optimally, implements all the watcher types in XS, does
		2617	automatic timer adjustments even when no monotonic clock is available,
		2618	can take avdantage of advanced kernel interfaces such as C<epoll> and
		2619	C<kqueue>, and is the fastest backend I<by far>. You can even embed
		2620	L<Glib>/L<Gtk2> in it (or vice versa, see L<EV::Glib> and L<Glib::EV>).
		2621
		2622	If you only use backends that rely on another event loop (e.g. C<Tk>),
		2623	then this module will do nothing for you.
		2624
		2625	=item L<Guard>
		2626
		2627	The guard module, when used, will be used to implement
		2628	C<AnyEvent::Util::guard>. This speeds up guards considerably (and uses a
		2629	lot less memory), but otherwise doesn't affect guard operation much. It is
		2630	purely used for performance.
		2631
		2632	=item L<JSON> and L<JSON::XS>
		2633
		2634	One of these modules is required when you want to read or write JSON data
		2635	via L<AnyEvent::Handle>. L<JSON> is also written in pure-perl, but can take
		2636	advantage of the ultra-high-speed L<JSON::XS> module when it is installed.
		2637
		2638	=item L<Net::SSLeay>
		2639
		2640	Implementing TLS/SSL in Perl is certainly interesting, but not very
		2641	worthwhile: If this module is installed, then L<AnyEvent::Handle> (with
		2642	the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL.
		2643
		2644	=item L<Time::HiRes>
		2645
		2646	This module is part of perl since release 5.008. It will be used when the
		2647	chosen event library does not come with a timing source of its own. The
		2648	pure-perl event loop (L<AnyEvent::Loop>) will additionally load it to
		2649	try to use a monotonic clock for timing stability.
		2650
		2651	=back
		2652
1658		2653
1659	=head1 FORK	2654	=head1 FORK
1660		2655
1661	Most event libraries are not fork-safe. The ones who are usually are	2656	Most event libraries are not fork-safe. The ones who are usually are
1662	because they rely on inefficient but fork-safe C<select> or C<poll>	2657	because they rely on inefficient but fork-safe C<select> or C<poll> calls
1663	calls. Only L<EV> is fully fork-aware.	2658	- higher performance APIs such as BSD's kqueue or the dreaded Linux epoll
		2659	are usually badly thought-out hacks that are incompatible with fork in
		2660	one way or another. Only L<EV> is fully fork-aware and ensures that you
		2661	continue event-processing in both parent and child (or both, if you know
		2662	what you are doing).
		2663
		2664	This means that, in general, you cannot fork and do event processing in
		2665	the child if the event library was initialised before the fork (which
		2666	usually happens when the first AnyEvent watcher is created, or the library
		2667	is loaded).
1664		2668
1665	If you have to fork, you must either do so I<before> creating your first	2669	If you have to fork, you must either do so I<before> creating your first
1666	watcher OR you must not use AnyEvent at all in the child.	2670	watcher OR you must not use AnyEvent at all in the child OR you must do
		2671	something completely out of the scope of AnyEvent.
		2672
		2673	The problem of doing event processing in the parent I<and> the child
		2674	is much more complicated: even for backends that I<are> fork-aware or
		2675	fork-safe, their behaviour is not usually what you want: fork clones all
		2676	watchers, that means all timers, I/O watchers etc. are active in both
		2677	parent and child, which is almost never what you want. USing C<exec>
		2678	to start worker children from some kind of manage rprocess is usually
		2679	preferred, because it is much easier and cleaner, at the expense of having
		2680	to have another binary.
1667		2681
1668		2682
1669	=head1 SECURITY CONSIDERATIONS	2683	=head1 SECURITY CONSIDERATIONS
1670		2684
1671	AnyEvent can be forced to load any event model via	2685	AnyEvent can be forced to load any event model via
…		…
1682		2696
1683	use AnyEvent;	2697	use AnyEvent;
1684		2698
1685	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can	2699	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1686	be used to probe what backend is used and gain other information (which is	2700	be used to probe what backend is used and gain other information (which is
1687	probably even less useful to an attacker than PERL_ANYEVENT_MODEL).	2701	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
		2702	$ENV{PERL_ANYEVENT_STRICT}.
		2703
		2704	Note that AnyEvent will remove I<all> environment variables starting with
		2705	C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
		2706	enabled.
1688		2707
1689		2708
1690	=head1 BUGS	2709	=head1 BUGS
1691		2710
1692	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard	2711	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
1693	to work around. If you suffer from memleaks, first upgrade to Perl 5.10	2712	to work around. If you suffer from memleaks, first upgrade to Perl 5.10
1694	and check wether the leaks still show up. (Perl 5.10.0 has other annoying	2713	and check wether the leaks still show up. (Perl 5.10.0 has other annoying
1695	mamleaks, such as leaking on C<map> and C<grep> but it is usually not as	2714	memleaks, such as leaking on C<map> and C<grep> but it is usually not as
1696	pronounced).	2715	pronounced).
1697		2716
1698		2717
1699	=head1 SEE ALSO	2718	=head1 SEE ALSO
1700		2719
		2720	Tutorial/Introduction: L<AnyEvent::Intro>.
		2721
		2722	FAQ: L<AnyEvent::FAQ>.
		2723
1701	Utility functions: L<AnyEvent::Util>.	2724	Utility functions: L<AnyEvent::Util>.
1702		2725
1703	Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>,	2726	Event modules: L<AnyEvent::Loop>, L<EV>, L<EV::Glib>, L<Glib::EV>,
1704	L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.	2727	L<Event>, L<Glib::Event>, L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.
1705		2728
1706	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,	2729	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
1707	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,	2730	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
1708	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,	2731	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
1709	L<AnyEvent::Impl::POE>.	2732	L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>, L<Anyevent::Impl::Irssi>.
1710		2733
1711	Non-blocking file handles, sockets, TCP clients and	2734	Non-blocking file handles, sockets, TCP clients and
1712	servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>.	2735	servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>.
1713		2736
1714	Asynchronous DNS: L<AnyEvent::DNS>.	2737	Asynchronous DNS: L<AnyEvent::DNS>.
1715		2738
1716	Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>,	2739	Thread support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>.
1717		2740
1718	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.	2741	Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::IRC>,
		2742	L<AnyEvent::HTTP>.
1719		2743
1720		2744
1721	=head1 AUTHOR	2745	=head1 AUTHOR
1722		2746
1723	Marc Lehmann <schmorp@schmorp.de>	2747	Marc Lehmann <schmorp@schmorp.de>

Diff Legend

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