ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.212 by root, Sun Jun 7 16:48:38 2009 UTC vs.
Revision 1.347 by root, Sun Jan 23 11:15:09 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 and POE are various supported	5	EV, Event, Glib, Tk, Perl, Event::Lib, Irssi, rxvt-unicode, IO::Async, Qt
6	event loops.	6	and POE are various supported event loops/environments.
7		7
8	=head1 SYNOPSIS	8	=head1 SYNOPSIS
9		9
10	use AnyEvent;	10	use AnyEvent;
11		11
		12	# if you prefer function calls, look at the AE manpage for
		13	# an alternative API.
		14
12	# file descriptor readable	15	# file handle or descriptor readable
13	my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... });	16	my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... });
14		17
15	# one-shot or repeating timers	18	# one-shot or repeating timers
16	my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });	19	my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });
17	my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...	20	my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...);
18		21
19	print AnyEvent->now; # prints current event loop time	22	print AnyEvent->now; # prints current event loop time
20	print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.	23	print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
21		24
22	# POSIX signal	25	# POSIX signal
…		…
40	=head1 INTRODUCTION/TUTORIAL	43	=head1 INTRODUCTION/TUTORIAL
41		44
42	This manpage is mainly a reference manual. If you are interested	45	This manpage is mainly a reference manual. If you are interested
43	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
44	L<AnyEvent::Intro> manpage.	47	L<AnyEvent::Intro> manpage.
		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.
45		58
46	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)	59	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
47		60
48	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
49	nowadays. So what is different about AnyEvent?	62	nowadays. So what is different about AnyEvent?
…		…
65	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
66	model you use.	79	model you use.
67		80
68	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
69	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
70	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
71	cannot use anything else, as they are simply incompatible to everything	84	cannot use anything else, as they are simply incompatible to everything
72	that isn't them. What's worse, all the potential users of your	85	that isn't them. What's worse, all the potential users of your
73	module are 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.
74		87
75	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works	88	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
76	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
77	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
78	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
79	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
80	event models it supports (including stuff like IO::Async, as long as those	93	supports (including stuff like IO::Async, as long as those use one of the
81	use one of the supported event loops. It is trivial to add new event loops	94	supported event loops. It is easy to add new event loops to AnyEvent, too,
82	to AnyEvent, too, so it is future-proof).	95	so it is future-proof).
83		96
84	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
85	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
86	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
87	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
88	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
89	technically possible.	102	technically possible.
90		103
91	Of course, AnyEvent comes with a big (and fully optional!) toolbox	104	Of course, AnyEvent comes with a big (and fully optional!) toolbox
92	of useful functionality, such as an asynchronous DNS resolver, 100%	105	of useful functionality, such as an asynchronous DNS resolver, 100%
…		…
98	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
99	model, you should I<not> use this module.	112	model, you should I<not> use this module.
100		113
101	=head1 DESCRIPTION	114	=head1 DESCRIPTION
102		115
103	L<AnyEvent> provides an identical interface to multiple event loops. This	116	L<AnyEvent> provides a uniform interface to various event loops. This
104	allows module authors to utilise an event loop without forcing module	117	allows module authors to use event loop functionality without forcing
105	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
106	peacefully at any one time).	119	than one event loop cannot coexist peacefully).
107		120
108	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>
109	module.	122	module.
110		123
111	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
112	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
113	following modules is already loaded: L<EV>,	126	following modules is already loaded: L<EV>, L<AnyEvent::Impl::Perl>,
114	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
115	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
116	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
117	adaptor should always succeed) in the order given. The first one that can	130	available, the pure-perl L<AnyEvent::Impl::Perl> should always work, so
118	be successfully loaded will be used. If, after this, still none could be	131	the other two are not normally tried.
119	found, AnyEvent will fall back to a pure-perl event loop, which is not
120	very efficient, but should work everywhere.
121		132
122	Because AnyEvent first checks for modules that are already loaded, loading	133	Because AnyEvent first checks for modules that are already loaded, loading
123	an event model explicitly before first using AnyEvent will likely make	134	an event model explicitly before first using AnyEvent will likely make
124	that model the default. For example:	135	that model the default. For example:
125		136
…		…
127	use AnyEvent;	138	use AnyEvent;
128		139
129	# .. AnyEvent will likely default to Tk	140	# .. AnyEvent will likely default to Tk
130		141
131	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
132	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,
133	use AnyEvent so their modules work together with others seamlessly...	144	as very few modules hardcode event loops without announcing this very
		145	loudly.
134		146
135	The pure-perl implementation of AnyEvent is called	147	The pure-perl implementation of AnyEvent is called
136	C<AnyEvent::Impl::Perl>. Like other event modules you can load it	148	C<AnyEvent::Impl::Perl>. Like other event modules you can load it
137	explicitly and enjoy the high availability of that event loop :)	149	explicitly and enjoy the high availability of that event loop :)
138		150
…		…
147	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
148	is in control).	160	is in control).
149		161
150	Note that B<callbacks must not permanently change global variables>	162	Note that B<callbacks must not permanently change global variables>
151	potentially in use by the event loop (such as C<$_> or C<$[>) and that B<<	163	potentially in use by the event loop (such as C<$_> or C<$[>) and that B<<
152	callbacks must not C<die> >>. The former is good programming practise in	164	callbacks must not C<die> >>. The former is good programming practice in
153	Perl and the latter stems from the fact that exception handling differs	165	Perl and the latter stems from the fact that exception handling differs
154	widely between event loops.	166	widely between event loops.
155		167
156	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
157	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
158	to it).	170	to it).
159		171
160	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.
161		173
162	Many watchers either are used with "recursion" (repeating timers for	174	Many watchers either are used with "recursion" (repeating timers for
163	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.
164		176
165	An any way to achieve that is this pattern:	177	One way to achieve that is this pattern:
166		178
167	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {	179	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
168	# you can use $w here, for example to undef it	180	# you can use $w here, for example to undef it
169	undef $w;	181	undef $w;
170	});	182	});
…		…
173	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
174	declared.	186	declared.
175		187
176	=head2 I/O WATCHERS	188	=head2 I/O WATCHERS
177		189
		190	$w = AnyEvent->io (
		191	fh => <filehandle_or_fileno>,
		192	poll => <"r" or "w">,
		193	cb => <callback>,
		194	);
		195
178	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
179	with the following mandatory key-value pairs as arguments:	197	with the following mandatory key-value pairs as arguments:
180		198
181	C<fh> is 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
182	for events (AnyEvent might or might not keep a reference to this file	200	for events (AnyEvent might or might not keep a reference to this file
183	handle). Note that only file handles pointing to things for which	201	handle). Note that only file handles pointing to things for which
184	non-blocking operation makes sense are allowed. This includes sockets,	202	non-blocking operation makes sense are allowed. This includes sockets,
185	most character devices, pipes, fifos and so on, but not for example files	203	most character devices, pipes, fifos and so on, but not for example files
186	or block devices.	204	or block devices.
…		…
196		214
197	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.
198	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
199	underlying file descriptor.	217	underlying file descriptor.
200		218
201	Some event loops issue spurious readyness notifications, so you should	219	Some event loops issue spurious readiness notifications, so you should
202	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
203	handles.	221	handles.
204		222
205	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
206	watcher.	224	watcher.
…		…
211	undef $w;	229	undef $w;
212	});	230	});
213		231
214	=head2 TIME WATCHERS	232	=head2 TIME WATCHERS
215		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
216	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 >>
217	method with the following mandatory arguments:	243	method with the following mandatory arguments:
218		244
219	C<after> specifies after how many seconds (fractional values are	245	C<after> specifies after how many seconds (fractional values are
220	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
…		…
222		248
223	Although the callback might get passed parameters, their value and	249	Although the callback might get passed parameters, their value and
224	presence is undefined and you cannot rely on them. Portable AnyEvent	250	presence is undefined and you cannot rely on them. Portable AnyEvent
225	callbacks cannot use arguments passed to time watcher callbacks.	251	callbacks cannot use arguments passed to time watcher callbacks.
226		252
227	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
228	parameter, C<interval>, as a strictly positive number (> 0), then the	254	parameter, C<interval>, as a strictly positive number (> 0), then the
229	callback will be invoked regularly at that interval (in fractional	255	callback will be invoked regularly at that interval (in fractional
230	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
231	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.
232		258
233	The callback will be rescheduled before invoking the callback, but no	259	The callback will be rescheduled before invoking the callback, but no
234	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
235	only approximate.	261	only approximate.
236		262
237	Example: fire an event after 7.7 seconds.	263	Example: fire an event after 7.7 seconds.
238		264
239	my $w = AnyEvent->timer (after => 7.7, cb => sub {	265	my $w = AnyEvent->timer (after => 7.7, cb => sub {
…		…
257		283
258	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
259	use absolute time internally. This makes a difference when your clock	285	use absolute time internally. This makes a difference when your clock
260	"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
261	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
262	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.
263		289
264	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
265	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
266	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)
267	timers.	293	timers.
268		294
269	AnyEvent always prefers relative timers, if available, matching the	295	AnyEvent always prefers relative timers, if available, matching the
270	AnyEvent API.	296	AnyEvent API.
…		…
292	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
293	function to call when you want to know the current time.>	319	function to call when you want to know the current time.>
294		320
295	This function is also often faster then C<< AnyEvent->time >>, and	321	This function is also often faster then C<< AnyEvent->time >>, and
296	thus the preferred method if you want some timestamp (for example,	322	thus the preferred method if you want some timestamp (for example,
297	L<AnyEvent::Handle> uses this to update it's activity timeouts).	323	L<AnyEvent::Handle> uses this to update its activity timeouts).
298		324
299	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
300	with your timing, you can skip it without bad conscience.	326	with your timing; you can skip it without a bad conscience.
301		327
302	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>
303	and L<EV> and the following set-up:	329	and L<EV> and the following set-up:
304		330
305	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
306	time=500 (assume no other callbacks delay processing). In your callback,	332	time=500 (assume no other callbacks delay processing). In your callback,
307	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
308	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
309	after three seconds.	335	after three seconds.
310		336
…		…
341	might affect timers and time-outs.	367	might affect timers and time-outs.
342		368
343	When this is the case, you can call this method, which will update the	369	When this is the case, you can call this method, which will update the
344	event loop's idea of "current time".	370	event loop's idea of "current time".
345		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
346	Note that updating the time I<might> cause some events to be handled.	379	Note that updating the time I<might> cause some events to be handled.
347		380
348	=back	381	=back
349		382
350	=head2 SIGNAL WATCHERS	383	=head2 SIGNAL WATCHERS
		384
		385	$w = AnyEvent->signal (signal => <uppercase_signal_name>, cb => <callback>);
351		386
352	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
353	I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl	388	I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl
354	callback to be invoked whenever a signal occurs.	389	callback to be invoked whenever a signal occurs.
355		390
…		…
361	invocation, and callback invocation will be synchronous. Synchronous means	396	invocation, and callback invocation will be synchronous. Synchronous means
362	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,
363	but it is guaranteed not to interrupt any other callbacks.	398	but it is guaranteed not to interrupt any other callbacks.
364		399
365	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
366	between multiple watchers.	401	between multiple watchers, and AnyEvent will ensure that signals will not
		402	interrupt your program at bad times.
367		403
368	This watcher might use C<%SIG>, so programs overwriting those signals	404	This watcher might use C<%SIG> (depending on the event loop used),
369	directly will likely not work correctly.	405	so programs overwriting those signals directly will likely not work
		406	correctly.
370		407
371	Example: exit on SIGINT	408	Example: exit on SIGINT
372		409
373	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });	410	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
374		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
375	=head2 CHILD PROCESS WATCHERS	449	=head2 CHILD PROCESS WATCHERS
376		450
		451	$w = AnyEvent->child (pid => <process id>, cb => <callback>);
		452
377	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.
378		454
379	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,
380	watches for any child process exit). The watcher will triggered only when	456	using C<0> watches for any child process exit, on others this will
381	the child process has finished and an exit status is available, not on	457	croak). The watcher will be triggered only when the child process has
382	any trace events (stopped/continued).	458	finished and an exit status is available, not on any trace events
		459	(stopped/continued).
383		460
384	The callback will be called with the pid and exit status (as returned by	461	The callback will be called with the pid and exit status (as returned by
385	waitpid), so unlike other watcher types, you I<can> rely on child watcher	462	waitpid), so unlike other watcher types, you I<can> rely on child watcher
386	callback arguments.	463	callback arguments.
387		464
…		…
392		469
393	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
394	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
395	have exited already (and no SIGCHLD will be sent anymore).	472	have exited already (and no SIGCHLD will be sent anymore).
396		473
397	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
398	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
399	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.
400		480
401	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
402	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
403	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 the latency and race problems
		488	mentioned in the description of signal watchers apply.
404		489
405	Example: fork a process and wait for it	490	Example: fork a process and wait for it
406		491
407	my $done = AnyEvent->condvar;	492	my $done = AnyEvent->condvar;
408		493
…		…
420	# do something else, then wait for process exit	505	# do something else, then wait for process exit
421	$done->recv;	506	$done->recv;
422		507
423	=head2 IDLE WATCHERS	508	=head2 IDLE WATCHERS
424		509
425	Sometimes there is a need to do something, but it is not so important	510	$w = AnyEvent->idle (cb => <callback>);
426	to do it instantly, but only when there is nothing better to do. This
427	"nothing better to do" is usually defined to be "no other events need
428	attention by the event loop".
429		511
430	Idle watchers ideally get invoked when the event loop has nothing	512	This will repeatedly invoke the callback after the process becomes idle,
431	better to do, just before it would block the process to wait for new	513	until either the watcher is destroyed or new events have been detected.
432	events. Instead of blocking, the idle watcher is invoked.
433		514
434	Most event loops unfortunately do not really support idle watchers (only	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
435	EV, Event and Glib do it in a usable fashion) - for the rest, AnyEvent	525	EV, Event and Glib do it in a usable fashion) - for the rest, AnyEvent
436	will simply call the callback "from time to time".	526	will simply call the callback "from time to time".
437		527
438	Example: read lines from STDIN, but only process them when the	528	Example: read lines from STDIN, but only process them when the
439	program is otherwise idle:	529	program is otherwise idle:
…		…
455	});	545	});
456	});	546	});
457		547
458	=head2 CONDITION VARIABLES	548	=head2 CONDITION VARIABLES
459		549
		550	$cv = AnyEvent->condvar;
		551
		552	$cv->send (<list>);
		553	my @res = $cv->recv;
		554
460	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
461	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
462	will actively watch for new events and call your callbacks.	557	will actively watch for new events and call your callbacks.
463		558
464	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
465	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).
466		561
467	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
468	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.
469		566
470	Condition variables can be created by calling the C<< AnyEvent->condvar	567	Condition variables can be created by calling the C<< AnyEvent->condvar
471	>> method, usually without arguments. The only argument pair allowed is	568	>> method, usually without arguments. The only argument pair allowed is
472
473	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
474	becomes true, with the condition variable as the first argument (but not	570	becomes true, with the condition variable as the first argument (but not
475	the results).	571	the results).
476		572
477	After creation, the condition variable is "false" until it becomes "true"	573	After creation, the condition variable is "false" until it becomes "true"
478	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
479	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<<
480	->send >> method).	576	->send >> method).
481		577
482	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
483	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:
484	in time where multiple outstanding events have been processed. And yet	580
485	another way to call them is transactions - each condition variable can be	581	=over 4
486	used to represent a transaction, which finishes at some point and delivers	582
487	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
488		601
489	Condition variables are very useful to signal that something has finished,	602	Condition variables are very useful to signal that something has finished,
490	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,
491	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
492	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
…		…
505		618
506	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
507	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
508	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
509	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
510	it's C<new> method in your own C<new> method.	623	its C<new> method in your own C<new> method.
511		624
512	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
513	eventually calls C<< -> send >>, and the "consumer side", which waits	626	eventually calls C<< -> send >>, and the "consumer side", which waits
514	for the send to occur.	627	for the send to occur.
515		628
516	Example: wait for a timer.	629	Example: wait for a timer.
517		630
518	# wait till the result is ready	631	# condition: "wait till the timer is fired"
519	my $result_ready = AnyEvent->condvar;	632	my $timer_fired = AnyEvent->condvar;
520		633
521	# do something such as adding a timer	634	# create the timer - we could wait for, say
522	# or socket watcher the calls $result_ready->send	635	# a handle becomign ready, or even an
523	# when the "result" is ready.	636	# AnyEvent::HTTP request to finish, but
524	# in this case, we simply use a timer:	637	# in this case, we simply use a timer:
525	my $w = AnyEvent->timer (	638	my $w = AnyEvent->timer (
526	after => 1,	639	after => 1,
527	cb => sub { $result_ready->send },	640	cb => sub { $timer_fired->send },
528	);	641	);
529		642
530	# this "blocks" (while handling events) till the callback	643	# this "blocks" (while handling events) till the callback
531	# calls send	644	# calls ->send
532	$result_ready->recv;	645	$timer_fired->recv;
533		646
534	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
535	condition variables are also code references.	648	variables are also callable directly.
536		649
537	my $done = AnyEvent->condvar;	650	my $done = AnyEvent->condvar;
538	my $delay = AnyEvent->timer (after => 5, cb => $done);	651	my $delay = AnyEvent->timer (after => 5, cb => $done);
539	$done->recv;	652	$done->recv;
540		653
…		…
546		659
547	...	660	...
548		661
549	my @info = $couchdb->info->recv;	662	my @info = $couchdb->info->recv;
550		663
551	And this is how you would just ste a callback to be called whenever the	664	And this is how you would just set a callback to be called whenever the
552	results are available:	665	results are available:
553		666
554	$couchdb->info->cb (sub {	667	$couchdb->info->cb (sub {
555	my @info = $_[0]->recv;	668	my @info = $_[0]->recv;
556	});	669	});
…		…
574	immediately from within send.	687	immediately from within send.
575		688
576	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
577	future C<< ->recv >> calls.	690	future C<< ->recv >> calls.
578		691
579	Condition variables are overloaded so one can call them directly	692	Condition variables are overloaded so one can call them directly (as if
580	(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
581	C<send>. Note, however, that many C-based event loops do not handle	694	C<send>.
582	overloading, so as tempting as it may be, passing a condition variable
583	instead of a callback does not work. Both the pure perl and EV loops
584	support overloading, however, as well as all functions that use perl to
585	invoke a callback (as in L<AnyEvent::Socket> and L<AnyEvent::DNS> for
586	example).
587		695
588	=item $cv->croak ($error)	696	=item $cv->croak ($error)
589		697
590	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
591	C<Carp::croak> with the given error message/object/scalar.	699	C<Carp::croak> with the given error message/object/scalar.
592		700
593	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
594	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.
595		707
596	=item $cv->begin ([group callback])	708	=item $cv->begin ([group callback])
597		709
598	=item $cv->end	710	=item $cv->end
599
600	These two methods are EXPERIMENTAL and MIGHT CHANGE.
601		711
602	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
603	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
604	to use a condition variable for the whole process.	714	to use a condition variable for the whole process.
605		715
606	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
607	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
608	>>, 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
609	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
610	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.
611		722
612	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:
613		730
614	my $cv = AnyEvent->condvar;	731	my $cv = AnyEvent->condvar;
615		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
616	my %result;	757	my %result;
617	$cv->begin (sub { $cv->send (\%result) });	758	$cv->begin (sub { shift->send (\%result) });
618		759
619	for my $host (@list_of_hosts) {	760	for my $host (@list_of_hosts) {
620	$cv->begin;	761	$cv->begin;
621	ping_host_then_call_callback $host, sub {	762	ping_host_then_call_callback $host, sub {
622	$result{$host} = ...;	763	$result{$host} = ...;
…		…
637	loop, which serves two important purposes: first, it sets the callback	778	loop, which serves two important purposes: first, it sets the callback
638	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
639	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
640	doesn't execute once).	781	doesn't execute once).
641		782
642	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
643	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
644	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
645	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>.
646		788
647	=back	789	=back
648		790
649	=head3 METHODS FOR CONSUMERS	791	=head3 METHODS FOR CONSUMERS
650		792
…		…
654	=over 4	796	=over 4
655		797
656	=item $cv->recv	798	=item $cv->recv
657		799
658	Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak	800	Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak
659	>> methods have been called on c<$cv>, while servicing other watchers	801	>> methods have been called on C<$cv>, while servicing other watchers
660	normally.	802	normally.
661		803
662	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
663	will return immediately.	805	will return immediately.
664		806
…		…
666	function will call C<croak>.	808	function will call C<croak>.
667		809
668	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,
669	in scalar context only the first one will be returned.	811	in scalar context only the first one will be returned.
670		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
671	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
672	(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
673	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
674	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
675	condition variables with some kind of request results and supporting	824	condition variables with some kind of request results and supporting
676	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,
677	while still supporting blocking waits if the caller so desires).	826	while still supporting blocking waits if the caller so desires).
678		827
679	Another reason I<never> to C<< ->recv >> in a module is that you cannot
680	sensibly have two C<< ->recv >>'s in parallel, as that would require
681	multiple interpreters or coroutines/threads, none of which C<AnyEvent>
682	can supply.
683
684	The L<Coro> module, however, I<can> and I<does> supply coroutines and, in
685	fact, L<Coro::AnyEvent> replaces AnyEvent's condvars by coroutine-safe
686	versions and also integrates coroutines into AnyEvent, making blocking
687	C<< ->recv >> calls perfectly safe as long as they are done from another
688	coroutine (one that doesn't run the event loop).
689
690	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
691	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
692	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
693	waits otherwise.	831	waits otherwise.
694		832
695	=item $bool = $cv->ready	833	=item $bool = $cv->ready
…		…
701		839
702	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
703	replaces it before doing so.	841	replaces it before doing so.
704		842
705	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
706	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
707	variable itself. Calling C<recv> inside the callback or at any later time	845	condition variable itself. If the condition is already true, the
708	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.
709		848
710	=back	849	=back
711		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 implementation, 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
		884	=item Backends with special needs.
		885
		886	Qt requires the Qt::Application to be instantiated first, but will
		887	otherwise be picked up automatically. As long as the main program
		888	instantiates the application before any AnyEvent watchers are created,
		889	everything should just work.
		890
		891	AnyEvent::Impl::Qt based on Qt.
		892
		893	=item Event loops that are indirectly supported via other backends.
		894
		895	Some event loops can be supported via other modules:
		896
		897	There is no direct support for WxWidgets (L<Wx>) or L<Prima>.
		898
		899	B<WxWidgets> has no support for watching file handles. However, you can
		900	use WxWidgets through the POE adaptor, as POE has a Wx backend that simply
		901	polls 20 times per second, which was considered to be too horrible to even
		902	consider for AnyEvent.
		903
		904	B<Prima> is not supported as nobody seems to be using it, but it has a POE
		905	backend, so it can be supported through POE.
		906
		907	AnyEvent knows about both L<Prima> and L<Wx>, however, and will try to
		908	load L<POE> when detecting them, in the hope that POE will pick them up,
		909	in which case everything will be automatic.
		910
		911	=back
		912
712	=head1 GLOBAL VARIABLES AND FUNCTIONS	913	=head1 GLOBAL VARIABLES AND FUNCTIONS
713		914
		915	These are not normally required to use AnyEvent, but can be useful to
		916	write AnyEvent extension modules.
		917
714	=over 4	918	=over 4
715		919
716	=item $AnyEvent::MODEL	920	=item $AnyEvent::MODEL
717		921
718	Contains C<undef> until the first watcher is being created. Then it	922	Contains C<undef> until the first watcher is being created, before the
		923	backend has been autodetected.
		924
719	contains the event model that is being used, which is the name of the	925	Afterwards it contains the event model that is being used, which is the
720	Perl class implementing the model. This class is usually one of the	926	name of the Perl class implementing the model. This class is usually one
721	C<AnyEvent::Impl:xxx> modules, but can be any other class in the case	927	of the C<AnyEvent::Impl::xxx> modules, but can be any other class in the
722	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).	928	case AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode> it
723		929	will be C<urxvt::anyevent>).
724	The known classes so far are:
725
726	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
727	AnyEvent::Impl::Event based on Event, second best choice.
728	AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
729	AnyEvent::Impl::Glib based on Glib, third-best choice.
730	AnyEvent::Impl::Tk based on Tk, very bad choice.
731	AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
732	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
733	AnyEvent::Impl::POE based on POE, not generic enough for full support.
734
735	There is no support for WxWidgets, as WxWidgets has no support for
736	watching file handles. However, you can use WxWidgets through the
737	POE Adaptor, as POE has a Wx backend that simply polls 20 times per
738	second, which was considered to be too horrible to even consider for
739	AnyEvent. Likewise, other POE backends can be used by AnyEvent by using
740	it's adaptor.
741
742	AnyEvent knows about L<Prima> and L<Wx> and will try to use L<POE> when
743	autodetecting them.
744		930
745	=item AnyEvent::detect	931	=item AnyEvent::detect
746		932
747	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model	933	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
748	if necessary. You should only call this function right before you would	934	if necessary. You should only call this function right before you would
749	have created an AnyEvent watcher anyway, that is, as late as possible at	935	have created an AnyEvent watcher anyway, that is, as late as possible at
750	runtime.	936	runtime, and not e.g. during initialisation of your module.
		937
		938	If you need to do some initialisation before AnyEvent watchers are
		939	created, use C<post_detect>.
751		940
752	=item $guard = AnyEvent::post_detect { BLOCK }	941	=item $guard = AnyEvent::post_detect { BLOCK }
753		942
754	Arranges for the code block to be executed as soon as the event model is	943	Arranges for the code block to be executed as soon as the event model is
755	autodetected (or immediately if this has already happened).	944	autodetected (or immediately if that has already happened).
		945
		946	The block will be executed I<after> the actual backend has been detected
		947	(C<$AnyEvent::MODEL> is set), but I<before> any watchers have been
		948	created, so it is possible to e.g. patch C<@AnyEvent::ISA> or do
		949	other initialisations - see the sources of L<AnyEvent::Strict> or
		950	L<AnyEvent::AIO> to see how this is used.
		951
		952	The most common usage is to create some global watchers, without forcing
		953	event module detection too early, for example, L<AnyEvent::AIO> creates
		954	and installs the global L<IO::AIO> watcher in a C<post_detect> block to
		955	avoid autodetecting the event module at load time.
756		956
757	If called in scalar or list context, then it creates and returns an object	957	If called in scalar or list context, then it creates and returns an object
758	that automatically removes the callback again when it is destroyed. See	958	that automatically removes the callback again when it is destroyed (or
		959	C<undef> when the hook was immediately executed). See L<AnyEvent::AIO> for
759	L<Coro::BDB> for a case where this is useful.	960	a case where this is useful.
		961
		962	Example: Create a watcher for the IO::AIO module and store it in
		963	C<$WATCHER>, but do so only do so after the event loop is initialised.
		964
		965	our WATCHER;
		966
		967	my $guard = AnyEvent::post_detect {
		968	$WATCHER = AnyEvent->io (fh => IO::AIO::poll_fileno, poll => 'r', cb => \&IO::AIO::poll_cb);
		969	};
		970
		971	# the ||= is important in case post_detect immediately runs the block,
		972	# as to not clobber the newly-created watcher. assigning both watcher and
		973	# post_detect guard to the same variable has the advantage of users being
		974	# able to just C<undef $WATCHER> if the watcher causes them grief.
		975
		976	$WATCHER ||= $guard;
760		977
761	=item @AnyEvent::post_detect	978	=item @AnyEvent::post_detect
762		979
763	If there are any code references in this array (you can C<push> to it	980	If there are any code references in this array (you can C<push> to it
764	before or after loading AnyEvent), then they will called directly after	981	before or after loading AnyEvent), then they will be called directly
765	the event loop has been chosen.	982	after the event loop has been chosen.
766		983
767	You should check C<$AnyEvent::MODEL> before adding to this array, though:	984	You should check C<$AnyEvent::MODEL> before adding to this array, though:
768	if it contains a true value then the event loop has already been detected,	985	if it is defined then the event loop has already been detected, and the
769	and the array will be ignored.	986	array will be ignored.
770		987
771	Best use C<AnyEvent::post_detect { BLOCK }> instead.	988	Best use C<AnyEvent::post_detect { BLOCK }> when your application allows
		989	it, as it takes care of these details.
		990
		991	This variable is mainly useful for modules that can do something useful
		992	when AnyEvent is used and thus want to know when it is initialised, but do
		993	not need to even load it by default. This array provides the means to hook
		994	into AnyEvent passively, without loading it.
		995
		996	Example: To load Coro::AnyEvent whenever Coro and AnyEvent are used
		997	together, you could put this into Coro (this is the actual code used by
		998	Coro to accomplish this):
		999
		1000	if (defined $AnyEvent::MODEL) {
		1001	# AnyEvent already initialised, so load Coro::AnyEvent
		1002	require Coro::AnyEvent;
		1003	} else {
		1004	# AnyEvent not yet initialised, so make sure to load Coro::AnyEvent
		1005	# as soon as it is
		1006	push @AnyEvent::post_detect, sub { require Coro::AnyEvent };
		1007	}
772		1008
773	=back	1009	=back
774		1010
775	=head1 WHAT TO DO IN A MODULE	1011	=head1 WHAT TO DO IN A MODULE
776		1012
…		…
787	because it will stall the whole program, and the whole point of using	1023	because it will stall the whole program, and the whole point of using
788	events is to stay interactive.	1024	events is to stay interactive.
789		1025
790	It is fine, however, to call C<< ->recv >> when the user of your module	1026	It is fine, however, to call C<< ->recv >> when the user of your module
791	requests it (i.e. if you create a http request object ad have a method	1027	requests it (i.e. if you create a http request object ad have a method
792	called C<results> that returns the results, it should call C<< ->recv >>	1028	called C<results> that returns the results, it may call C<< ->recv >>
793	freely, as the user of your module knows what she is doing. always).	1029	freely, as the user of your module knows what she is doing. Always).
794		1030
795	=head1 WHAT TO DO IN THE MAIN PROGRAM	1031	=head1 WHAT TO DO IN THE MAIN PROGRAM
796		1032
797	There will always be a single main program - the only place that should	1033	There will always be a single main program - the only place that should
798	dictate which event model to use.	1034	dictate which event model to use.
799		1035
800	If it doesn't care, it can just "use AnyEvent" and use it itself, or not	1036	If the program is not event-based, it need not do anything special, even
801	do anything special (it does not need to be event-based) and let AnyEvent	1037	when it depends on a module that uses an AnyEvent. If the program itself
802	decide which implementation to chose if some module relies on it.	1038	uses AnyEvent, but does not care which event loop is used, all it needs
		1039	to do is C<use AnyEvent>. In either case, AnyEvent will choose the best
		1040	available loop implementation.
803		1041
804	If the main program relies on a specific event model - for example, in	1042	If the main program relies on a specific event model - for example, in
805	Gtk2 programs you have to rely on the Glib module - you should load the	1043	Gtk2 programs you have to rely on the Glib module - you should load the
806	event module before loading AnyEvent or any module that uses it: generally	1044	event module before loading AnyEvent or any module that uses it: generally
807	speaking, you should load it as early as possible. The reason is that	1045	speaking, you should load it as early as possible. The reason is that
808	modules might create watchers when they are loaded, and AnyEvent will	1046	modules might create watchers when they are loaded, and AnyEvent will
809	decide on the event model to use as soon as it creates watchers, and it	1047	decide on the event model to use as soon as it creates watchers, and it
810	might chose the wrong one unless you load the correct one yourself.	1048	might choose the wrong one unless you load the correct one yourself.
811		1049
812	You can chose to use a pure-perl implementation by loading the	1050	You can chose to use a pure-perl implementation by loading the
813	C<AnyEvent::Impl::Perl> module, which gives you similar behaviour	1051	C<AnyEvent::Impl::Perl> module, which gives you similar behaviour
814	everywhere, but letting AnyEvent chose the model is generally better.	1052	everywhere, but letting AnyEvent chose the model is generally better.
815		1053
…		…
831		1069
832		1070
833	=head1 OTHER MODULES	1071	=head1 OTHER MODULES
834		1072
835	The following is a non-exhaustive list of additional modules that use	1073	The following is a non-exhaustive list of additional modules that use
836	AnyEvent and can therefore be mixed easily with other AnyEvent modules	1074	AnyEvent as a client and can therefore be mixed easily with other AnyEvent
837	in the same program. Some of the modules come with AnyEvent, some are	1075	modules and other event loops in the same program. Some of the modules
838	available via CPAN.	1076	come as part of AnyEvent, the others are available via CPAN.
839		1077
840	=over 4	1078	=over 4
841		1079
842	=item L<AnyEvent::Util>	1080	=item L<AnyEvent::Util>
843		1081
844	Contains various utility functions that replace often-used but blocking	1082	Contains various utility functions that replace often-used blocking
845	functions such as C<inet_aton> by event-/callback-based versions.	1083	functions such as C<inet_aton> with event/callback-based versions.
846		1084
847	=item L<AnyEvent::Socket>	1085	=item L<AnyEvent::Socket>
848		1086
849	Provides various utility functions for (internet protocol) sockets,	1087	Provides various utility functions for (internet protocol) sockets,
850	addresses and name resolution. Also functions to create non-blocking tcp	1088	addresses and name resolution. Also functions to create non-blocking tcp
…		…
852		1090
853	=item L<AnyEvent::Handle>	1091	=item L<AnyEvent::Handle>
854		1092
855	Provide read and write buffers, manages watchers for reads and writes,	1093	Provide read and write buffers, manages watchers for reads and writes,
856	supports raw and formatted I/O, I/O queued and fully transparent and	1094	supports raw and formatted I/O, I/O queued and fully transparent and
857	non-blocking SSL/TLS.	1095	non-blocking SSL/TLS (via L<AnyEvent::TLS>).
858		1096
859	=item L<AnyEvent::DNS>	1097	=item L<AnyEvent::DNS>
860		1098
861	Provides rich asynchronous DNS resolver capabilities.	1099	Provides rich asynchronous DNS resolver capabilities.
862		1100
		1101	=item L<AnyEvent::HTTP>, L<AnyEvent::IRC>, L<AnyEvent::XMPP>, L<AnyEvent::GPSD>, L<AnyEvent::IGS>, L<AnyEvent::FCP>
		1102
		1103	Implement event-based interfaces to the protocols of the same name (for
		1104	the curious, IGS is the International Go Server and FCP is the Freenet
		1105	Client Protocol).
		1106
		1107	=item L<AnyEvent::Handle::UDP>
		1108
		1109	Here be danger!
		1110
		1111	As Pauli would put it, "Not only is it not right, it's not even wrong!" -
		1112	there are so many things wrong with AnyEvent::Handle::UDP, most notably
		1113	its use of a stream-based API with a protocol that isn't streamable, that
		1114	the only way to improve it is to delete it.
		1115
		1116	It features data corruption (but typically only under load) and general
		1117	confusion. On top, the author is not only clueless about UDP but also
		1118	fact-resistant - some gems of his understanding: "connect doesn't work
		1119	with UDP", "UDP packets are not IP packets", "UDP only has datagrams, not
		1120	packets", "I don't need to implement proper error checking as UDP doesn't
		1121	support error checking" and so on - he doesn't even understand what's
		1122	wrong with his module when it is explained to him.
		1123
863	=item L<AnyEvent::HTTP>	1124	=item L<AnyEvent::DBI>
864		1125
865	A simple-to-use HTTP library that is capable of making a lot of concurrent	1126	Executes L<DBI> requests asynchronously in a proxy process for you,
866	HTTP requests.	1127	notifying you in an event-based way when the operation is finished.
		1128
		1129	=item L<AnyEvent::AIO>
		1130
		1131	Truly asynchronous (as opposed to non-blocking) I/O, should be in the
		1132	toolbox of every event programmer. AnyEvent::AIO transparently fuses
		1133	L<IO::AIO> and AnyEvent together, giving AnyEvent access to event-based
		1134	file I/O, and much more.
867		1135
868	=item L<AnyEvent::HTTPD>	1136	=item L<AnyEvent::HTTPD>
869		1137
870	Provides a simple web application server framework.	1138	A simple embedded webserver.
871		1139
872	=item L<AnyEvent::FastPing>	1140	=item L<AnyEvent::FastPing>
873		1141
874	The fastest ping in the west.	1142	The fastest ping in the west.
875		1143
876	=item L<AnyEvent::DBI>
877
878	Executes L<DBI> requests asynchronously in a proxy process.
879
880	=item L<AnyEvent::AIO>
881
882	Truly asynchronous I/O, should be in the toolbox of every event
883	programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
884	together.
885
886	=item L<AnyEvent::BDB>
887
888	Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
889	L<BDB> and AnyEvent together.
890
891	=item L<AnyEvent::GPSD>
892
893	A non-blocking interface to gpsd, a daemon delivering GPS information.
894
895	=item L<AnyEvent::IGS>
896
897	A non-blocking interface to the Internet Go Server protocol (used by
898	L<App::IGS>).
899
900	=item L<AnyEvent::IRC>
901
902	AnyEvent based IRC client module family (replacing the older Net::IRC3).
903
904	=item L<Net::XMPP2>
905
906	AnyEvent based XMPP (Jabber protocol) module family.
907
908	=item L<Net::FCP>
909
910	AnyEvent-based implementation of the Freenet Client Protocol, birthplace
911	of AnyEvent.
912
913	=item L<Event::ExecFlow>
914
915	High level API for event-based execution flow control.
916
917	=item L<Coro>	1144	=item L<Coro>
918		1145
919	Has special support for AnyEvent via L<Coro::AnyEvent>.	1146	Has special support for AnyEvent via L<Coro::AnyEvent>.
920		1147
921	=item L<IO::Lambda>
922
923	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
924
925	=back	1148	=back
926		1149
927	=cut	1150	=cut
928		1151
929	package AnyEvent;	1152	package AnyEvent;
930		1153
931	no warnings;	1154	# basically a tuned-down version of common::sense
932	use strict qw(vars subs);	1155	sub common_sense {
		1156	# from common:.sense 3.4
		1157	${^WARNING_BITS} ^= ${^WARNING_BITS} ^ "\x3c\x3f\x33\x00\x0f\xf0\x0f\xc0\xf0\xfc\x33\x00";
		1158	# use strict vars subs - NO UTF-8, as Util.pm doesn't like this atm. (uts46data.pl)
		1159	$^H |= 0x00000600;
		1160	}
933		1161
		1162	BEGIN { AnyEvent::common_sense }
		1163
934	use Carp;	1164	use Carp ();
935		1165
936	our $VERSION = 4.411;	1166	our $VERSION = '5.31';
937	our $MODEL;	1167	our $MODEL;
938		1168
939	our $AUTOLOAD;	1169	our $AUTOLOAD;
940	our @ISA;	1170	our @ISA;
941		1171
942	our @REGISTRY;	1172	our @REGISTRY;
943		1173
944	our $WIN32;	1174	our $VERBOSE;
945		1175
946	BEGIN {	1176	BEGIN {
947	my $win32 = ! ! ($^O =~ /mswin32/i);	1177	require "AnyEvent/constants.pl";
948	eval "sub WIN32(){ $win32 }";
949	}
950		1178
		1179	eval "sub TAINT (){" . (${^TAINT}*1) . "}";
		1180
		1181	delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV}
		1182	if ${^TAINT};
		1183
951	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;	1184	$VERBOSE = $ENV{PERL_ANYEVENT_VERBOSE}*1;
		1185
		1186	}
		1187
		1188	our $MAX_SIGNAL_LATENCY = 10;
952		1189
953	our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred	1190	our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred
954		1191
955	{	1192	{
956	my $idx;	1193	my $idx;
…		…
958	for reverse split /\s*,\s*/,	1195	for reverse split /\s*,\s*/,
959	$ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";	1196	$ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";
960	}	1197	}
961		1198
962	my @models = (	1199	my @models = (
963	[EV:: => AnyEvent::Impl::EV::],	1200	[EV:: => AnyEvent::Impl::EV:: , 1],
964	[Event:: => AnyEvent::Impl::Event::],
965	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],	1201	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl:: , 1],
966	# everything below here will not be autoprobed	1202	# everything below here will not (normally) be autoprobed
967	# as the pureperl backend should work everywhere	1203	# as the pureperl backend should work everywhere
968	# and is usually faster	1204	# and is usually faster
		1205	[Event:: => AnyEvent::Impl::Event::, 1],
		1206	[Glib:: => AnyEvent::Impl::Glib:: , 1], # becomes extremely slow with many watchers
		1207	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
		1208	[Irssi:: => AnyEvent::Impl::Irssi::], # Irssi has a bogus "Event" package
969	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles	1209	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
970	[Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers
971	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
972	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program	1210	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program
973	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza	1211	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
974	[Wx:: => AnyEvent::Impl::POE::],	1212	[Wx:: => AnyEvent::Impl::POE::],
975	[Prima:: => AnyEvent::Impl::POE::],	1213	[Prima:: => AnyEvent::Impl::POE::],
		1214	[IO::Async::Loop:: => AnyEvent::Impl::IOAsync::],
		1215	[Cocoa::EventLoop:: => AnyEvent::Impl::Cocoa::],
976	);	1216	);
977		1217
978	our %method = map +($_ => 1),	1218	our %method = map +($_ => 1),
979	qw(io timer time now now_update signal child idle condvar one_event DESTROY);	1219	qw(io timer time now now_update signal child idle condvar one_event DESTROY);
980		1220
981	our @post_detect;	1221	our @post_detect;
982		1222
983	sub post_detect(&) {	1223	sub post_detect(&) {
984	my ($cb) = @_;	1224	my ($cb) = @_;
985		1225
986	if ($MODEL) {
987	$cb->();
988
989	1
990	} else {
991	push @post_detect, $cb;	1226	push @post_detect, $cb;
992		1227
993	defined wantarray	1228	defined wantarray
994	? bless \$cb, "AnyEvent::Util::postdetect"	1229	? bless \$cb, "AnyEvent::Util::postdetect"
995	: ()	1230	: ()
996	}
997	}	1231	}
998		1232
999	sub AnyEvent::Util::postdetect::DESTROY {	1233	sub AnyEvent::Util::postdetect::DESTROY {
1000	@post_detect = grep $_ != ${$_[0]}, @post_detect;	1234	@post_detect = grep $_ != ${$_[0]}, @post_detect;
1001	}	1235	}
1002		1236
1003	sub detect() {	1237	sub detect() {
		1238	# free some memory
		1239	*detect = sub () { $MODEL };
		1240
		1241	local $!; # for good measure
		1242	local $SIG{__DIE__};
		1243
		1244	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
		1245	my $model = "AnyEvent::Impl::$1";
		1246	if (eval "require $model") {
		1247	$MODEL = $model;
		1248	warn "AnyEvent: loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.\n" if $VERBOSE >= 2;
		1249	} else {
		1250	warn "AnyEvent: unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@" if $VERBOSE;
		1251	}
		1252	}
		1253
		1254	# check for already loaded models
1004	unless ($MODEL) {	1255	unless ($MODEL) {
1005	no strict 'refs';	1256	for (@REGISTRY, @models) {
1006	local $SIG{__DIE__};	1257	my ($package, $model) = @$_;
1007		1258	if (${"$package\::VERSION"} > 0) {
1008	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
1009	my $model = "AnyEvent::Impl::$1";
1010	if (eval "require $model") {	1259	if (eval "require $model") {
1011	$MODEL = $model;	1260	$MODEL = $model;
1012	warn "AnyEvent: loaded model '$model' (forced by \$PERL_ANYEVENT_MODEL), using it.\n" if $verbose > 1;	1261	warn "AnyEvent: autodetected model '$model', using it.\n" if $VERBOSE >= 2;
1013	} else {	1262	last;
1014	warn "AnyEvent: unable to load model '$model' (from \$PERL_ANYEVENT_MODEL):\n$@" if $verbose;	1263	}
1015	}	1264	}
1016	}	1265	}
1017		1266
1018	# check for already loaded models
1019	unless ($MODEL) {	1267	unless ($MODEL) {
		1268	# try to autoload a model
1020	for (@REGISTRY, @models) {	1269	for (@REGISTRY, @models) {
1021	my ($package, $model) = @$_;	1270	my ($package, $model, $autoload) = @$_;
		1271	if (
		1272	$autoload
		1273	and eval "require $package"
1022	if (${"$package\::VERSION"} > 0) {	1274	and ${"$package\::VERSION"} > 0
1023	if (eval "require $model") {	1275	and eval "require $model"
		1276	) {
1024	$MODEL = $model;	1277	$MODEL = $model;
1025	warn "AnyEvent: autodetected model '$model', using it.\n" if $verbose > 1;	1278	warn "AnyEvent: autoloaded model '$model', using it.\n" if $VERBOSE >= 2;
1026	last;	1279	last;
1027	}
1028	}	1280	}
1029	}	1281	}
1030		1282
1031	unless ($MODEL) {
1032	# try to load a model
1033
1034	for (@REGISTRY, @models) {
1035	my ($package, $model) = @$_;
1036	if (eval "require $package"
1037	and ${"$package\::VERSION"} > 0
1038	and eval "require $model") {
1039	$MODEL = $model;
1040	warn "AnyEvent: autoprobed model '$model', using it.\n" if $verbose > 1;
1041	last;
1042	}
1043	}
1044
1045	$MODEL	1283	$MODEL
1046	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.\n";	1284	or die "AnyEvent: backend autodetection failed - did you properly install AnyEvent?\n";
1047	}
1048	}	1285	}
1049
1050	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
1051
1052	unshift @ISA, $MODEL;
1053
1054	require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
1055
1056	(shift @post_detect)->() while @post_detect;
1057	}	1286	}
		1287
		1288	@models = (); # free probe data
		1289
		1290	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
		1291	unshift @ISA, $MODEL;
		1292
		1293	# now nuke some methods that are overridden by the backend.
		1294	# SUPER is not allowed.
		1295	for (qw(time signal child idle)) {
		1296	undef &{"AnyEvent::Base::$_"}
		1297	if defined &{"$MODEL\::$_"};
		1298	}
		1299
		1300	if ($ENV{PERL_ANYEVENT_STRICT}) {
		1301	eval { require AnyEvent::Strict };
		1302	warn "AnyEvent: cannot load AnyEvent::Strict: $@"
		1303	if $@ && $VERBOSE;
		1304	}
		1305
		1306	(shift @post_detect)->() while @post_detect;
		1307
		1308	*post_detect = sub(&) {
		1309	shift->();
		1310
		1311	undef
		1312	};
1058		1313
1059	$MODEL	1314	$MODEL
1060	}	1315	}
1061		1316
1062	sub AUTOLOAD {	1317	sub AUTOLOAD {
1063	(my $func = $AUTOLOAD) =~ s/.*://;	1318	(my $func = $AUTOLOAD) =~ s/.*://;
1064		1319
1065	$method{$func}	1320	$method{$func}
1066	or croak "$func: not a valid method for AnyEvent objects";	1321	or Carp::croak "$func: not a valid AnyEvent class method";
1067		1322
1068	detect unless $MODEL;	1323	detect;
1069		1324
1070	my $class = shift;	1325	my $class = shift;
1071	$class->$func (@_);	1326	$class->$func (@_);
1072	}	1327	}
1073		1328
1074	# utility function to dup a filehandle. this is used by many backends	1329	# utility function to dup a filehandle. this is used by many backends
1075	# to support binding more than one watcher per filehandle (they usually	1330	# to support binding more than one watcher per filehandle (they usually
1076	# allow only one watcher per fd, so we dup it to get a different one).	1331	# allow only one watcher per fd, so we dup it to get a different one).
1077	sub _dupfh($$$$) {	1332	sub _dupfh($$;$$) {
1078	my ($poll, $fh, $r, $w) = @_;	1333	my ($poll, $fh, $r, $w) = @_;
1079		1334
1080	# cygwin requires the fh mode to be matching, unix doesn't	1335	# cygwin requires the fh mode to be matching, unix doesn't
1081	my ($rw, $mode) = $poll eq "r" ? ($r, "<")	1336	my ($rw, $mode) = $poll eq "r" ? ($r, "<&") : ($w, ">&");
1082	: $poll eq "w" ? ($w, ">")
1083	: Carp::croak "AnyEvent->io requires poll set to either 'r' or 'w'";
1084		1337
1085	open my $fh2, "$mode&" . fileno $fh	1338	open my $fh2, $mode, $fh
1086	or die "cannot dup() filehandle: $!,";	1339	or die "AnyEvent->io: cannot dup() filehandle in mode '$poll': $!,";
1087		1340
1088	# we assume CLOEXEC is already set by perl in all important cases	1341	# we assume CLOEXEC is already set by perl in all important cases
1089		1342
1090	($fh2, $rw)	1343	($fh2, $rw)
1091	}	1344	}
1092		1345
		1346	=head1 SIMPLIFIED AE API
		1347
		1348	Starting with version 5.0, AnyEvent officially supports a second, much
		1349	simpler, API that is designed to reduce the calling, typing and memory
		1350	overhead by using function call syntax and a fixed number of parameters.
		1351
		1352	See the L<AE> manpage for details.
		1353
		1354	=cut
		1355
		1356	package AE;
		1357
		1358	our $VERSION = $AnyEvent::VERSION;
		1359
		1360	# fall back to the main API by default - backends and AnyEvent::Base
		1361	# implementations can overwrite these.
		1362
		1363	sub io($$$) {
		1364	AnyEvent->io (fh => $_[0], poll => $_[1] ? "w" : "r", cb => $_[2])
		1365	}
		1366
		1367	sub timer($$$) {
		1368	AnyEvent->timer (after => $_[0], interval => $_[1], cb => $_[2])
		1369	}
		1370
		1371	sub signal($$) {
		1372	AnyEvent->signal (signal => $_[0], cb => $_[1])
		1373	}
		1374
		1375	sub child($$) {
		1376	AnyEvent->child (pid => $_[0], cb => $_[1])
		1377	}
		1378
		1379	sub idle($) {
		1380	AnyEvent->idle (cb => $_[0])
		1381	}
		1382
		1383	sub cv(;&) {
		1384	AnyEvent->condvar (@_ ? (cb => $_[0]) : ())
		1385	}
		1386
		1387	sub now() {
		1388	AnyEvent->now
		1389	}
		1390
		1391	sub now_update() {
		1392	AnyEvent->now_update
		1393	}
		1394
		1395	sub time() {
		1396	AnyEvent->time
		1397	}
		1398
1093	package AnyEvent::Base;	1399	package AnyEvent::Base;
1094		1400
1095	# default implementations for many methods	1401	# default implementations for many methods
1096		1402
1097	BEGIN {	1403	sub time {
		1404	eval q{ # poor man's autoloading {}
		1405	# probe for availability of Time::HiRes
1098	if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {	1406	if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {
		1407	warn "AnyEvent: using Time::HiRes for sub-second timing accuracy.\n" if $VERBOSE >= 8;
1099	*_time = \&Time::HiRes::time;	1408	*AE::time = \&Time::HiRes::time;
1100	# if (eval "use POSIX (); (POSIX::times())...	1409	# if (eval "use POSIX (); (POSIX::times())...
1101	} else {	1410	} else {
		1411	warn "AnyEvent: using built-in time(), WARNING, no sub-second resolution!\n" if $VERBOSE;
1102	*_time = sub { time }; # epic fail	1412	*AE::time = sub (){ time }; # epic fail
		1413	}
		1414
		1415	*time = sub { AE::time }; # different prototypes
		1416	};
		1417	die if $@;
		1418
		1419	&time
		1420	}
		1421
		1422	*now = \&time;
		1423
		1424	sub now_update { }
		1425
		1426	# default implementation for ->condvar
		1427
		1428	sub condvar {
		1429	eval q{ # poor man's autoloading {}
		1430	*condvar = sub {
		1431	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar"
		1432	};
		1433
		1434	*AE::cv = sub (;&) {
		1435	bless { @_ ? (_ae_cb => shift) : () }, "AnyEvent::CondVar"
		1436	};
		1437	};
		1438	die if $@;
		1439
		1440	&condvar
		1441	}
		1442
		1443	# default implementation for ->signal
		1444
		1445	our $HAVE_ASYNC_INTERRUPT;
		1446
		1447	sub _have_async_interrupt() {
		1448	$HAVE_ASYNC_INTERRUPT = 1*(!$ENV{PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT}
		1449	&& eval "use Async::Interrupt 1.02 (); 1")
		1450	unless defined $HAVE_ASYNC_INTERRUPT;
		1451
		1452	$HAVE_ASYNC_INTERRUPT
		1453	}
		1454
		1455	our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO);
		1456	our (%SIG_ASY, %SIG_ASY_W);
		1457	our ($SIG_COUNT, $SIG_TW);
		1458
		1459	# install a dummy wakeup watcher to reduce signal catching latency
		1460	# used by Impls
		1461	sub _sig_add() {
		1462	unless ($SIG_COUNT++) {
		1463	# try to align timer on a full-second boundary, if possible
		1464	my $NOW = AE::now;
		1465
		1466	$SIG_TW = AE::timer
		1467	$MAX_SIGNAL_LATENCY - ($NOW - int $NOW),
		1468	$MAX_SIGNAL_LATENCY,
		1469	sub { } # just for the PERL_ASYNC_CHECK
		1470	;
1103	}	1471	}
1104	}	1472	}
1105		1473
1106	sub time { _time }	1474	sub _sig_del {
1107	sub now { _time }	1475	undef $SIG_TW
1108	sub now_update { }	1476	unless --$SIG_COUNT;
1109
1110	# default implementation for ->condvar
1111
1112	sub condvar {
1113	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar"
1114	}	1477	}
1115		1478
1116	# default implementation for ->signal	1479	our $_sig_name_init; $_sig_name_init = sub {
		1480	eval q{ # poor man's autoloading {}
		1481	undef $_sig_name_init;
1117		1482
1118	our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO);	1483	if (_have_async_interrupt) {
		1484	*sig2num = \&Async::Interrupt::sig2num;
		1485	*sig2name = \&Async::Interrupt::sig2name;
		1486	} else {
		1487	require Config;
1119		1488
1120	sub _signal_exec {	1489	my %signame2num;
1121	sysread $SIGPIPE_R, my $dummy, 4;	1490	@signame2num{ split ' ', $Config::Config{sig_name} }
		1491	= split ' ', $Config::Config{sig_num};
1122		1492
1123	while (%SIG_EV) {	1493	my @signum2name;
1124	for (keys %SIG_EV) {	1494	@signum2name[values %signame2num] = keys %signame2num;
1125	delete $SIG_EV{$_};	1495
1126	$_->() for values %{ $SIG_CB{$_} || {} };	1496	*sig2num = sub($) {
		1497	$_[0] > 0 ? shift : $signame2num{+shift}
		1498	};
		1499	*sig2name = sub ($) {
		1500	$_[0] > 0 ? $signum2name[+shift] : shift
		1501	};
1127	}	1502	}
1128	}	1503	};
1129	}	1504	die if $@;
		1505	};
		1506
		1507	sub sig2num ($) { &$_sig_name_init; &sig2num }
		1508	sub sig2name($) { &$_sig_name_init; &sig2name }
1130		1509
1131	sub signal {	1510	sub signal {
1132	my (undef, %arg) = @_;	1511	eval q{ # poor man's autoloading {}
		1512	# probe for availability of Async::Interrupt
		1513	if (_have_async_interrupt) {
		1514	warn "AnyEvent: using Async::Interrupt for race-free signal handling.\n" if $VERBOSE >= 8;
1133		1515
1134	unless ($SIGPIPE_R) {	1516	$SIGPIPE_R = new Async::Interrupt::EventPipe;
1135	require Fcntl;	1517	$SIG_IO = AE::io $SIGPIPE_R->fileno, 0, \&_signal_exec;
1136		1518
1137	if (AnyEvent::WIN32) {
1138	require AnyEvent::Util;
1139
1140	($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
1141	AnyEvent::Util::fh_nonblocking ($SIGPIPE_R) if $SIGPIPE_R;
1142	AnyEvent::Util::fh_nonblocking ($SIGPIPE_W) if $SIGPIPE_W; # just in case
1143	} else {	1519	} else {
		1520	warn "AnyEvent: using emulated perl signal handling with latency timer.\n" if $VERBOSE >= 8;
		1521
		1522	if (AnyEvent::WIN32) {
		1523	require AnyEvent::Util;
		1524
		1525	($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
		1526	AnyEvent::Util::fh_nonblocking ($SIGPIPE_R, 1) if $SIGPIPE_R;
		1527	AnyEvent::Util::fh_nonblocking ($SIGPIPE_W, 1) if $SIGPIPE_W; # just in case
		1528	} else {
1144	pipe $SIGPIPE_R, $SIGPIPE_W;	1529	pipe $SIGPIPE_R, $SIGPIPE_W;
1145	fcntl $SIGPIPE_R, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_R;	1530	fcntl $SIGPIPE_R, AnyEvent::F_SETFL, AnyEvent::O_NONBLOCK if $SIGPIPE_R;
1146	fcntl $SIGPIPE_W, &Fcntl::F_SETFL, &Fcntl::O_NONBLOCK if $SIGPIPE_W; # just in case	1531	fcntl $SIGPIPE_W, AnyEvent::F_SETFL, AnyEvent::O_NONBLOCK if $SIGPIPE_W; # just in case
1147		1532
1148	# not strictly required, as $^F is normally 2, but let's make sure...	1533	# not strictly required, as $^F is normally 2, but let's make sure...
1149	fcntl $SIGPIPE_R, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC;	1534	fcntl $SIGPIPE_R, AnyEvent::F_SETFD, AnyEvent::FD_CLOEXEC;
1150	fcntl $SIGPIPE_W, &Fcntl::F_SETFD, &Fcntl::FD_CLOEXEC;	1535	fcntl $SIGPIPE_W, AnyEvent::F_SETFD, AnyEvent::FD_CLOEXEC;
		1536	}
		1537
		1538	$SIGPIPE_R
		1539	or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n";
		1540
		1541	$SIG_IO = AE::io $SIGPIPE_R, 0, \&_signal_exec;
1151	}	1542	}
1152		1543
1153	$SIGPIPE_R	1544	*signal = $HAVE_ASYNC_INTERRUPT
1154	or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n";	1545	? sub {
		1546	my (undef, %arg) = @_;
1155		1547
1156	$SIG_IO = AnyEvent->io (fh => $SIGPIPE_R, poll => "r", cb => \&_signal_exec);	1548	# async::interrupt
1157	}
1158
1159	my $signal = uc $arg{signal}	1549	my $signal = sig2num $arg{signal};
1160	or Carp::croak "required option 'signal' is missing";
1161
1162	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};	1550	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};
		1551
		1552	$SIG_ASY{$signal} ||= new Async::Interrupt
		1553	cb => sub { undef $SIG_EV{$signal} },
		1554	signal => $signal,
		1555	pipe => [$SIGPIPE_R->filenos],
		1556	pipe_autodrain => 0,
		1557	;
		1558
		1559	bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
		1560	}
		1561	: sub {
		1562	my (undef, %arg) = @_;
		1563
		1564	# pure perl
		1565	my $signal = sig2name $arg{signal};
		1566	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};
		1567
1163	$SIG{$signal} ||= sub {	1568	$SIG{$signal} ||= sub {
1164	local $!;	1569	local $!;
1165	syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV;	1570	syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV;
1166	undef $SIG_EV{$signal};	1571	undef $SIG_EV{$signal};
		1572	};
		1573
		1574	# can't do signal processing without introducing races in pure perl,
		1575	# so limit the signal latency.
		1576	_sig_add;
		1577
		1578	bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
		1579	}
		1580	;
		1581
		1582	*AnyEvent::Base::signal::DESTROY = sub {
		1583	my ($signal, $cb) = @{$_[0]};
		1584
		1585	_sig_del;
		1586
		1587	delete $SIG_CB{$signal}{$cb};
		1588
		1589	$HAVE_ASYNC_INTERRUPT
		1590	? delete $SIG_ASY{$signal}
		1591	: # delete doesn't work with older perls - they then
		1592	# print weird messages, or just unconditionally exit
		1593	# instead of getting the default action.
		1594	undef $SIG{$signal}
		1595	unless keys %{ $SIG_CB{$signal} };
		1596	};
		1597
		1598	*_signal_exec = sub {
		1599	$HAVE_ASYNC_INTERRUPT
		1600	? $SIGPIPE_R->drain
		1601	: sysread $SIGPIPE_R, (my $dummy), 9;
		1602
		1603	while (%SIG_EV) {
		1604	for (keys %SIG_EV) {
		1605	delete $SIG_EV{$_};
		1606	$_->() for values %{ $SIG_CB{$_} || {} };
		1607	}
		1608	}
		1609	};
1167	};	1610	};
		1611	die if $@;
1168		1612
1169	bless [$signal, $arg{cb}], "AnyEvent::Base::signal"	1613	&signal
1170	}
1171
1172	sub AnyEvent::Base::signal::DESTROY {
1173	my ($signal, $cb) = @{$_[0]};
1174
1175	delete $SIG_CB{$signal}{$cb};
1176
1177	# delete doesn't work with older perls - they then
1178	# print weird messages, or just unconditionally exit
1179	# instead of getting the default action.
1180	undef $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
1181	}	1614	}
1182		1615
1183	# default implementation for ->child	1616	# default implementation for ->child
1184		1617
1185	our %PID_CB;	1618	our %PID_CB;
1186	our $CHLD_W;	1619	our $CHLD_W;
1187	our $CHLD_DELAY_W;	1620	our $CHLD_DELAY_W;
1188	our $WNOHANG;
1189		1621
1190	sub _sigchld {	1622	# used by many Impl's
1191	while (0 < (my $pid = waitpid -1, $WNOHANG)) {	1623	sub _emit_childstatus($$) {
		1624	my (undef, $rpid, $rstatus) = @_;
		1625
		1626	$_->($rpid, $rstatus)
1192	$_->($pid, $?) for (values %{ $PID_CB{$pid} || {} }),	1627	for values %{ $PID_CB{$rpid} || {} },
1193	(values %{ $PID_CB{0} || {} });	1628	values %{ $PID_CB{0} || {} };
1194	}
1195	}	1629	}
1196		1630
1197	sub child {	1631	sub child {
		1632	eval q{ # poor man's autoloading {}
		1633	*_sigchld = sub {
		1634	my $pid;
		1635
		1636	AnyEvent->_emit_childstatus ($pid, $?)
		1637	while ($pid = waitpid -1, WNOHANG) > 0;
		1638	};
		1639
		1640	*child = sub {
1198	my (undef, %arg) = @_;	1641	my (undef, %arg) = @_;
1199		1642
1200	defined (my $pid = $arg{pid} + 0)	1643	defined (my $pid = $arg{pid} + 0)
1201	or Carp::croak "required option 'pid' is missing";	1644	or Carp::croak "required option 'pid' is missing";
1202		1645
1203	$PID_CB{$pid}{$arg{cb}} = $arg{cb};	1646	$PID_CB{$pid}{$arg{cb}} = $arg{cb};
1204		1647
1205	$WNOHANG ||= eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;
1206
1207	unless ($CHLD_W) {	1648	unless ($CHLD_W) {
1208	$CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);	1649	$CHLD_W = AE::signal CHLD => \&_sigchld;
1209	# child could be a zombie already, so make at least one round	1650	# child could be a zombie already, so make at least one round
1210	&_sigchld;	1651	&_sigchld;
1211	}	1652	}
1212		1653
1213	bless [$pid, $arg{cb}], "AnyEvent::Base::child"	1654	bless [$pid, $arg{cb}], "AnyEvent::Base::child"
1214	}	1655	};
1215		1656
1216	sub AnyEvent::Base::child::DESTROY {	1657	*AnyEvent::Base::child::DESTROY = sub {
1217	my ($pid, $cb) = @{$_[0]};	1658	my ($pid, $cb) = @{$_[0]};
1218		1659
1219	delete $PID_CB{$pid}{$cb};	1660	delete $PID_CB{$pid}{$cb};
1220	delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };	1661	delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
1221		1662
1222	undef $CHLD_W unless keys %PID_CB;	1663	undef $CHLD_W unless keys %PID_CB;
		1664	};
		1665	};
		1666	die if $@;
		1667
		1668	&child
1223	}	1669	}
1224		1670
1225	# idle emulation is done by simply using a timer, regardless	1671	# idle emulation is done by simply using a timer, regardless
1226	# of whether the process is idle or not, and not letting	1672	# of whether the process is idle or not, and not letting
1227	# the callback use more than 50% of the time.	1673	# the callback use more than 50% of the time.
1228	sub idle {	1674	sub idle {
		1675	eval q{ # poor man's autoloading {}
		1676	*idle = sub {
1229	my (undef, %arg) = @_;	1677	my (undef, %arg) = @_;
1230		1678
1231	my ($cb, $w, $rcb) = $arg{cb};	1679	my ($cb, $w, $rcb) = $arg{cb};
1232		1680
1233	$rcb = sub {	1681	$rcb = sub {
1234	if ($cb) {	1682	if ($cb) {
1235	$w = _time;	1683	$w = _time;
1236	&$cb;	1684	&$cb;
1237	$w = _time - $w;	1685	$w = _time - $w;
1238		1686
1239	# never use more then 50% of the time for the idle watcher,	1687	# never use more then 50% of the time for the idle watcher,
1240	# within some limits	1688	# within some limits
1241	$w = 0.0001 if $w < 0.0001;	1689	$w = 0.0001 if $w < 0.0001;
1242	$w = 5 if $w > 5;	1690	$w = 5 if $w > 5;
1243		1691
1244	$w = AnyEvent->timer (after => $w, cb => $rcb);	1692	$w = AE::timer $w, 0, $rcb;
1245	} else {	1693	} else {
1246	# clean up...	1694	# clean up...
1247	undef $w;	1695	undef $w;
1248	undef $rcb;	1696	undef $rcb;
		1697	}
		1698	};
		1699
		1700	$w = AE::timer 0.05, 0, $rcb;
		1701
		1702	bless \\$cb, "AnyEvent::Base::idle"
1249	}	1703	};
		1704
		1705	*AnyEvent::Base::idle::DESTROY = sub {
		1706	undef $${$_[0]};
		1707	};
1250	};	1708	};
		1709	die if $@;
1251		1710
1252	$w = AnyEvent->timer (after => 0.05, cb => $rcb);	1711	&idle
1253
1254	bless \\$cb, "AnyEvent::Base::idle"
1255	}
1256
1257	sub AnyEvent::Base::idle::DESTROY {
1258	undef $${$_[0]};
1259	}	1712	}
1260		1713
1261	package AnyEvent::CondVar;	1714	package AnyEvent::CondVar;
1262		1715
1263	our @ISA = AnyEvent::CondVar::Base::;	1716	our @ISA = AnyEvent::CondVar::Base::;
1264		1717
		1718	# only to be used for subclassing
		1719	sub new {
		1720	my $class = shift;
		1721	bless AnyEvent->condvar (@_), $class
		1722	}
		1723
1265	package AnyEvent::CondVar::Base;	1724	package AnyEvent::CondVar::Base;
1266		1725
1267	use overload	1726	#use overload
1268	'&{}' => sub { my $self = shift; sub { $self->send (@_) } },	1727	# '&{}' => sub { my $self = shift; sub { $self->send (@_) } },
1269	fallback => 1;	1728	# fallback => 1;
		1729
		1730	# save 300+ kilobytes by dirtily hardcoding overloading
		1731	${"AnyEvent::CondVar::Base::OVERLOAD"}{dummy}++; # Register with magic by touching.
		1732	*{'AnyEvent::CondVar::Base::()'} = sub { }; # "Make it findable via fetchmethod."
		1733	*{'AnyEvent::CondVar::Base::(&{}'} = sub { my $self = shift; sub { $self->send (@_) } }; # &{}
		1734	${'AnyEvent::CondVar::Base::()'} = 1; # fallback
		1735
		1736	our $WAITING;
1270		1737
1271	sub _send {	1738	sub _send {
1272	# nop	1739	# nop
1273	}	1740	}
1274		1741
…		…
1287	sub ready {	1754	sub ready {
1288	$_[0]{_ae_sent}	1755	$_[0]{_ae_sent}
1289	}	1756	}
1290		1757
1291	sub _wait {	1758	sub _wait {
		1759	$WAITING
		1760	and !$_[0]{_ae_sent}
		1761	and Carp::croak "AnyEvent::CondVar: recursive blocking wait detected";
		1762
		1763	local $WAITING = 1;
1292	AnyEvent->one_event while !$_[0]{_ae_sent};	1764	AnyEvent->one_event while !$_[0]{_ae_sent};
1293	}	1765	}
1294		1766
1295	sub recv {	1767	sub recv {
1296	$_[0]->_wait;	1768	$_[0]->_wait;
…		…
1298	Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak};	1770	Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak};
1299	wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0]	1771	wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0]
1300	}	1772	}
1301		1773
1302	sub cb {	1774	sub cb {
1303	$_[0]{_ae_cb} = $_[1] if @_ > 1;	1775	my $cv = shift;
		1776
		1777	@_
		1778	and $cv->{_ae_cb} = shift
		1779	and $cv->{_ae_sent}
		1780	and (delete $cv->{_ae_cb})->($cv);
		1781
1304	$_[0]{_ae_cb}	1782	$cv->{_ae_cb}
1305	}	1783	}
1306		1784
1307	sub begin {	1785	sub begin {
1308	++$_[0]{_ae_counter};	1786	++$_[0]{_ae_counter};
1309	$_[0]{_ae_end_cb} = $_[1] if @_ > 1;	1787	$_[0]{_ae_end_cb} = $_[1] if @_ > 1;
…		…
1337	so on.	1815	so on.
1338		1816
1339	=head1 ENVIRONMENT VARIABLES	1817	=head1 ENVIRONMENT VARIABLES
1340		1818
1341	The following environment variables are used by this module or its	1819	The following environment variables are used by this module or its
1342	submodules:	1820	submodules.
		1821
		1822	Note that AnyEvent will remove I<all> environment variables starting with
		1823	C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
		1824	enabled.
1343		1825
1344	=over 4	1826	=over 4
1345		1827
1346	=item C<PERL_ANYEVENT_VERBOSE>	1828	=item C<PERL_ANYEVENT_VERBOSE>
1347		1829
…		…
1354	C<PERL_ANYEVENT_MODEL>.	1836	C<PERL_ANYEVENT_MODEL>.
1355		1837
1356	When set to C<2> or higher, cause AnyEvent to report to STDERR which event	1838	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1357	model it chooses.	1839	model it chooses.
1358		1840
		1841	When set to C<8> or higher, then AnyEvent will report extra information on
		1842	which optional modules it loads and how it implements certain features.
		1843
1359	=item C<PERL_ANYEVENT_STRICT>	1844	=item C<PERL_ANYEVENT_STRICT>
1360		1845
1361	AnyEvent does not do much argument checking by default, as thorough	1846	AnyEvent does not do much argument checking by default, as thorough
1362	argument checking is very costly. Setting this variable to a true value	1847	argument checking is very costly. Setting this variable to a true value
1363	will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly	1848	will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
1364	check the arguments passed to most method calls. If it finds any problems	1849	check the arguments passed to most method calls. If it finds any problems,
1365	it will croak.	1850	it will croak.
1366		1851
1367	In other words, enables "strict" mode.	1852	In other words, enables "strict" mode.
1368		1853
1369	Unlike C<use strict>, it is definitely recommended ot keep it off in	1854	Unlike C<use strict> (or its modern cousin, C<< use L<common::sense>
1370	production. Keeping C<PERL_ANYEVENT_STRICT=1> in your environment while	1855	>>, it is definitely recommended to keep it off in production. Keeping
1371	developing programs can be very useful, however.	1856	C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs
		1857	can be very useful, however.
1372		1858
1373	=item C<PERL_ANYEVENT_MODEL>	1859	=item C<PERL_ANYEVENT_MODEL>
1374		1860
1375	This can be used to specify the event model to be used by AnyEvent, before	1861	This can be used to specify the event model to be used by AnyEvent, before
1376	auto detection and -probing kicks in. It must be a string consisting	1862	auto detection and -probing kicks in. It must be a string consisting
…		…
1419		1905
1420	=item C<PERL_ANYEVENT_MAX_FORKS>	1906	=item C<PERL_ANYEVENT_MAX_FORKS>
1421		1907
1422	The maximum number of child processes that C<AnyEvent::Util::fork_call>	1908	The maximum number of child processes that C<AnyEvent::Util::fork_call>
1423	will create in parallel.	1909	will create in parallel.
		1910
		1911	=item C<PERL_ANYEVENT_MAX_OUTSTANDING_DNS>
		1912
		1913	The default value for the C<max_outstanding> parameter for the default DNS
		1914	resolver - this is the maximum number of parallel DNS requests that are
		1915	sent to the DNS server.
		1916
		1917	=item C<PERL_ANYEVENT_RESOLV_CONF>
		1918
		1919	The file to use instead of F</etc/resolv.conf> (or OS-specific
		1920	configuration) in the default resolver. When set to the empty string, no
		1921	default config will be used.
		1922
		1923	=item C<PERL_ANYEVENT_CA_FILE>, C<PERL_ANYEVENT_CA_PATH>.
		1924
		1925	When neither C<ca_file> nor C<ca_path> was specified during
		1926	L<AnyEvent::TLS> context creation, and either of these environment
		1927	variables exist, they will be used to specify CA certificate locations
		1928	instead of a system-dependent default.
		1929
		1930	=item C<PERL_ANYEVENT_AVOID_GUARD> and C<PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT>
		1931
		1932	When these are set to C<1>, then the respective modules are not
		1933	loaded. Mostly good for testing AnyEvent itself.
1424		1934
1425	=back	1935	=back
1426		1936
1427	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE	1937	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
1428		1938
…		…
1486	warn "read: $input\n"; # output what has been read	1996	warn "read: $input\n"; # output what has been read
1487	$cv->send if $input =~ /^q/i; # quit program if /^q/i	1997	$cv->send if $input =~ /^q/i; # quit program if /^q/i
1488	},	1998	},
1489	);	1999	);
1490		2000
1491	my $time_watcher; # can only be used once
1492
1493	sub new_timer {
1494	$timer = AnyEvent->timer (after => 1, cb => sub {	2001	my $time_watcher = AnyEvent->timer (after => 1, interval => 1, cb => sub {
1495	warn "timeout\n"; # print 'timeout' about every second	2002	warn "timeout\n"; # print 'timeout' at most every second
1496	&new_timer; # and restart the time
1497	});	2003	});
1498	}
1499
1500	new_timer; # create first timer
1501		2004
1502	$cv->recv; # wait until user enters /^q/i	2005	$cv->recv; # wait until user enters /^q/i
1503		2006
1504	=head1 REAL-WORLD EXAMPLE	2007	=head1 REAL-WORLD EXAMPLE
1505		2008
…		…
1578		2081
1579	The actual code goes further and collects all errors (C<die>s, exceptions)	2082	The actual code goes further and collects all errors (C<die>s, exceptions)
1580	that occurred during request processing. The C<result> method detects	2083	that occurred during request processing. The C<result> method detects
1581	whether an exception as thrown (it is stored inside the $txn object)	2084	whether an exception as thrown (it is stored inside the $txn object)
1582	and just throws the exception, which means connection errors and other	2085	and just throws the exception, which means connection errors and other
1583	problems get reported tot he code that tries to use the result, not in a	2086	problems get reported to the code that tries to use the result, not in a
1584	random callback.	2087	random callback.
1585		2088
1586	All of this enables the following usage styles:	2089	All of this enables the following usage styles:
1587		2090
1588	1. Blocking:	2091	1. Blocking:
…		…
1636	through AnyEvent. The benchmark creates a lot of timers (with a zero	2139	through AnyEvent. The benchmark creates a lot of timers (with a zero
1637	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,	2140	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,
1638	which it is), lets them fire exactly once and destroys them again.	2141	which it is), lets them fire exactly once and destroys them again.
1639		2142
1640	Source code for this benchmark is found as F<eg/bench> in the AnyEvent	2143	Source code for this benchmark is found as F<eg/bench> in the AnyEvent
1641	distribution.	2144	distribution. It uses the L<AE> interface, which makes a real difference
		2145	for the EV and Perl backends only.
1642		2146
1643	=head3 Explanation of the columns	2147	=head3 Explanation of the columns
1644		2148
1645	I<watcher> is the number of event watchers created/destroyed. Since	2149	I<watcher> is the number of event watchers created/destroyed. Since
1646	different event models feature vastly different performances, each event	2150	different event models feature vastly different performances, each event
…		…
1667	watcher.	2171	watcher.
1668		2172
1669	=head3 Results	2173	=head3 Results
1670		2174
1671	name watchers bytes create invoke destroy comment	2175	name watchers bytes create invoke destroy comment
1672	EV/EV 400000 224 0.47 0.35 0.27 EV native interface	2176	EV/EV 100000 223 0.47 0.43 0.27 EV native interface
1673	EV/Any 100000 224 2.88 0.34 0.27 EV + AnyEvent watchers	2177	EV/Any 100000 223 0.48 0.42 0.26 EV + AnyEvent watchers
1674	CoroEV/Any 100000 224 2.85 0.35 0.28 coroutines + Coro::Signal	2178	Coro::EV/Any 100000 223 0.47 0.42 0.26 coroutines + Coro::Signal
1675	Perl/Any 100000 452 4.13 0.73 0.95 pure perl implementation	2179	Perl/Any 100000 431 2.70 0.74 0.92 pure perl implementation
1676	Event/Event 16000 517 32.20 31.80 0.81 Event native interface	2180	Event/Event 16000 516 31.16 31.84 0.82 Event native interface
1677	Event/Any 16000 590 35.85 31.55 1.06 Event + AnyEvent watchers	2181	Event/Any 16000 1203 42.61 34.79 1.80 Event + AnyEvent watchers
		2182	IOAsync/Any 16000 1911 41.92 27.45 16.81 via IO::Async::Loop::IO_Poll
		2183	IOAsync/Any 16000 1726 40.69 26.37 15.25 via IO::Async::Loop::Epoll
1678	Glib/Any 16000 1357 102.33 12.31 51.00 quadratic behaviour	2184	Glib/Any 16000 1118 89.00 12.57 51.17 quadratic behaviour
1679	Tk/Any 2000 1860 27.20 66.31 14.00 SEGV with >> 2000 watchers	2185	Tk/Any 2000 1346 20.96 10.75 8.00 SEGV with >> 2000 watchers
1680	POE/Event 2000 6328 109.99 751.67 14.02 via POE::Loop::Event	2186	POE/Any 2000 6951 108.97 795.32 14.24 via POE::Loop::Event
1681	POE/Select 2000 6027 94.54 809.13 579.80 via POE::Loop::Select	2187	POE/Any 2000 6648 94.79 774.40 575.51 via POE::Loop::Select
1682		2188
1683	=head3 Discussion	2189	=head3 Discussion
1684		2190
1685	The benchmark does I<not> measure scalability of the event loop very	2191	The benchmark does I<not> measure scalability of the event loop very
1686	well. For example, a select-based event loop (such as the pure perl one)	2192	well. For example, a select-based event loop (such as the pure perl one)
…		…
1698	benchmark machine, handling an event takes roughly 1600 CPU cycles with	2204	benchmark machine, handling an event takes roughly 1600 CPU cycles with
1699	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU	2205	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU
1700	cycles with POE.	2206	cycles with POE.
1701		2207
1702	C<EV> is the sole leader regarding speed and memory use, which are both	2208	C<EV> is the sole leader regarding speed and memory use, which are both
1703	maximal/minimal, respectively. Even when going through AnyEvent, it uses	2209	maximal/minimal, respectively. When using the L<AE> API there is zero
		2210	overhead (when going through the AnyEvent API create is about 5-6 times
		2211	slower, with other times being equal, so still uses far less memory than
1704	far less memory than any other event loop and is still faster than Event	2212	any other event loop and is still faster than Event natively).
1705	natively.
1706		2213
1707	The pure perl implementation is hit in a few sweet spots (both the	2214	The pure perl implementation is hit in a few sweet spots (both the
1708	constant timeout and the use of a single fd hit optimisations in the perl	2215	constant timeout and the use of a single fd hit optimisations in the perl
1709	interpreter and the backend itself). Nevertheless this shows that it	2216	interpreter and the backend itself). Nevertheless this shows that it
1710	adds very little overhead in itself. Like any select-based backend its	2217	adds very little overhead in itself. Like any select-based backend its
1711	performance becomes really bad with lots of file descriptors (and few of	2218	performance becomes really bad with lots of file descriptors (and few of
1712	them active), of course, but this was not subject of this benchmark.	2219	them active), of course, but this was not subject of this benchmark.
1713		2220
1714	The C<Event> module has a relatively high setup and callback invocation	2221	The C<Event> module has a relatively high setup and callback invocation
1715	cost, but overall scores in on the third place.	2222	cost, but overall scores in on the third place.
		2223
		2224	C<IO::Async> performs admirably well, about on par with C<Event>, even
		2225	when using its pure perl backend.
1716		2226
1717	C<Glib>'s memory usage is quite a bit higher, but it features a	2227	C<Glib>'s memory usage is quite a bit higher, but it features a
1718	faster callback invocation and overall ends up in the same class as	2228	faster callback invocation and overall ends up in the same class as
1719	C<Event>. However, Glib scales extremely badly, doubling the number of	2229	C<Event>. However, Glib scales extremely badly, doubling the number of
1720	watchers increases the processing time by more than a factor of four,	2230	watchers increases the processing time by more than a factor of four,
…		…
1781	In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100	2291	In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100
1782	(1%) are active. This mirrors the activity of large servers with many	2292	(1%) are active. This mirrors the activity of large servers with many
1783	connections, most of which are idle at any one point in time.	2293	connections, most of which are idle at any one point in time.
1784		2294
1785	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent	2295	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent
1786	distribution.	2296	distribution. It uses the L<AE> interface, which makes a real difference
		2297	for the EV and Perl backends only.
1787		2298
1788	=head3 Explanation of the columns	2299	=head3 Explanation of the columns
1789		2300
1790	I<sockets> is the number of sockets, and twice the number of "servers" (as	2301	I<sockets> is the number of sockets, and twice the number of "servers" (as
1791	each server has a read and write socket end).	2302	each server has a read and write socket end).
…		…
1798	it to another server. This includes deleting the old timeout and creating	2309	it to another server. This includes deleting the old timeout and creating
1799	a new one that moves the timeout into the future.	2310	a new one that moves the timeout into the future.
1800		2311
1801	=head3 Results	2312	=head3 Results
1802		2313
1803	name sockets create request	2314	name sockets create request
1804	EV 20000 69.01 11.16	2315	EV 20000 62.66 7.99
1805	Perl 20000 73.32 35.87	2316	Perl 20000 68.32 32.64
1806	Event 20000 212.62 257.32	2317	IOAsync 20000 174.06 101.15 epoll
1807	Glib 20000 651.16 1896.30	2318	IOAsync 20000 174.67 610.84 poll
		2319	Event 20000 202.69 242.91
		2320	Glib 20000 557.01 1689.52
1808	POE 20000 349.67 12317.24 uses POE::Loop::Event	2321	POE 20000 341.54 12086.32 uses POE::Loop::Event
1809		2322
1810	=head3 Discussion	2323	=head3 Discussion
1811		2324
1812	This benchmark I<does> measure scalability and overall performance of the	2325	This benchmark I<does> measure scalability and overall performance of the
1813	particular event loop.	2326	particular event loop.
…		…
1815	EV is again fastest. Since it is using epoll on my system, the setup time	2328	EV is again fastest. Since it is using epoll on my system, the setup time
1816	is relatively high, though.	2329	is relatively high, though.
1817		2330
1818	Perl surprisingly comes second. It is much faster than the C-based event	2331	Perl surprisingly comes second. It is much faster than the C-based event
1819	loops Event and Glib.	2332	loops Event and Glib.
		2333
		2334	IO::Async performs very well when using its epoll backend, and still quite
		2335	good compared to Glib when using its pure perl backend.
1820		2336
1821	Event suffers from high setup time as well (look at its code and you will	2337	Event suffers from high setup time as well (look at its code and you will
1822	understand why). Callback invocation also has a high overhead compared to	2338	understand why). Callback invocation also has a high overhead compared to
1823	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event	2339	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event
1824	uses select or poll in basically all documented configurations.	2340	uses select or poll in basically all documented configurations.
…		…
1887	=item * C-based event loops perform very well with small number of	2403	=item * C-based event loops perform very well with small number of
1888	watchers, as the management overhead dominates.	2404	watchers, as the management overhead dominates.
1889		2405
1890	=back	2406	=back
1891		2407
		2408	=head2 THE IO::Lambda BENCHMARK
		2409
		2410	Recently I was told about the benchmark in the IO::Lambda manpage, which
		2411	could be misinterpreted to make AnyEvent look bad. In fact, the benchmark
		2412	simply compares IO::Lambda with POE, and IO::Lambda looks better (which
		2413	shouldn't come as a surprise to anybody). As such, the benchmark is
		2414	fine, and mostly shows that the AnyEvent backend from IO::Lambda isn't
		2415	very optimal. But how would AnyEvent compare when used without the extra
		2416	baggage? To explore this, I wrote the equivalent benchmark for AnyEvent.
		2417
		2418	The benchmark itself creates an echo-server, and then, for 500 times,
		2419	connects to the echo server, sends a line, waits for the reply, and then
		2420	creates the next connection. This is a rather bad benchmark, as it doesn't
		2421	test the efficiency of the framework or much non-blocking I/O, but it is a
		2422	benchmark nevertheless.
		2423
		2424	name runtime
		2425	Lambda/select 0.330 sec
		2426	+ optimized 0.122 sec
		2427	Lambda/AnyEvent 0.327 sec
		2428	+ optimized 0.138 sec
		2429	Raw sockets/select 0.077 sec
		2430	POE/select, components 0.662 sec
		2431	POE/select, raw sockets 0.226 sec
		2432	POE/select, optimized 0.404 sec
		2433
		2434	AnyEvent/select/nb 0.085 sec
		2435	AnyEvent/EV/nb 0.068 sec
		2436	+state machine 0.134 sec
		2437
		2438	The benchmark is also a bit unfair (my fault): the IO::Lambda/POE
		2439	benchmarks actually make blocking connects and use 100% blocking I/O,
		2440	defeating the purpose of an event-based solution. All of the newly
		2441	written AnyEvent benchmarks use 100% non-blocking connects (using
		2442	AnyEvent::Socket::tcp_connect and the asynchronous pure perl DNS
		2443	resolver), so AnyEvent is at a disadvantage here, as non-blocking connects
		2444	generally require a lot more bookkeeping and event handling than blocking
		2445	connects (which involve a single syscall only).
		2446
		2447	The last AnyEvent benchmark additionally uses L<AnyEvent::Handle>, which
		2448	offers similar expressive power as POE and IO::Lambda, using conventional
		2449	Perl syntax. This means that both the echo server and the client are 100%
		2450	non-blocking, further placing it at a disadvantage.
		2451
		2452	As you can see, the AnyEvent + EV combination even beats the
		2453	hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl
		2454	backend easily beats IO::Lambda and POE.
		2455
		2456	And even the 100% non-blocking version written using the high-level (and
		2457	slow :) L<AnyEvent::Handle> abstraction beats both POE and IO::Lambda
		2458	higher level ("unoptimised") abstractions by a large margin, even though
		2459	it does all of DNS, tcp-connect and socket I/O in a non-blocking way.
		2460
		2461	The two AnyEvent benchmarks programs can be found as F<eg/ae0.pl> and
		2462	F<eg/ae2.pl> in the AnyEvent distribution, the remaining benchmarks are
		2463	part of the IO::Lambda distribution and were used without any changes.
		2464
1892		2465
1893	=head1 SIGNALS	2466	=head1 SIGNALS
1894		2467
1895	AnyEvent currently installs handlers for these signals:	2468	AnyEvent currently installs handlers for these signals:
1896		2469
…		…
1899	=item SIGCHLD	2472	=item SIGCHLD
1900		2473
1901	A handler for C<SIGCHLD> is installed by AnyEvent's child watcher	2474	A handler for C<SIGCHLD> is installed by AnyEvent's child watcher
1902	emulation for event loops that do not support them natively. Also, some	2475	emulation for event loops that do not support them natively. Also, some
1903	event loops install a similar handler.	2476	event loops install a similar handler.
		2477
		2478	Additionally, when AnyEvent is loaded and SIGCHLD is set to IGNORE, then
		2479	AnyEvent will reset it to default, to avoid losing child exit statuses.
1904		2480
1905	=item SIGPIPE	2481	=item SIGPIPE
1906		2482
1907	A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef>	2483	A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef>
1908	when AnyEvent gets loaded.	2484	when AnyEvent gets loaded.
…		…
1920		2496
1921	=back	2497	=back
1922		2498
1923	=cut	2499	=cut
1924		2500
		2501	undef $SIG{CHLD}
		2502	if $SIG{CHLD} eq 'IGNORE';
		2503
1925	$SIG{PIPE} = sub { }	2504	$SIG{PIPE} = sub { }
1926	unless defined $SIG{PIPE};	2505	unless defined $SIG{PIPE};
1927		2506
		2507	=head1 RECOMMENDED/OPTIONAL MODULES
		2508
		2509	One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and
		2510	its built-in modules) are required to use it.
		2511
		2512	That does not mean that AnyEvent won't take advantage of some additional
		2513	modules if they are installed.
		2514
		2515	This section explains which additional modules will be used, and how they
		2516	affect AnyEvent's operation.
		2517
		2518	=over 4
		2519
		2520	=item L<Async::Interrupt>
		2521
		2522	This slightly arcane module is used to implement fast signal handling: To
		2523	my knowledge, there is no way to do completely race-free and quick
		2524	signal handling in pure perl. To ensure that signals still get
		2525	delivered, AnyEvent will start an interval timer to wake up perl (and
		2526	catch the signals) with some delay (default is 10 seconds, look for
		2527	C<$AnyEvent::MAX_SIGNAL_LATENCY>).
		2528
		2529	If this module is available, then it will be used to implement signal
		2530	catching, which means that signals will not be delayed, and the event loop
		2531	will not be interrupted regularly, which is more efficient (and good for
		2532	battery life on laptops).
		2533
		2534	This affects not just the pure-perl event loop, but also other event loops
		2535	that have no signal handling on their own (e.g. Glib, Tk, Qt).
		2536
		2537	Some event loops (POE, Event, Event::Lib) offer signal watchers natively,
		2538	and either employ their own workarounds (POE) or use AnyEvent's workaround
		2539	(using C<$AnyEvent::MAX_SIGNAL_LATENCY>). Installing L<Async::Interrupt>
		2540	does nothing for those backends.
		2541
		2542	=item L<EV>
		2543
		2544	This module isn't really "optional", as it is simply one of the backend
		2545	event loops that AnyEvent can use. However, it is simply the best event
		2546	loop available in terms of features, speed and stability: It supports
		2547	the AnyEvent API optimally, implements all the watcher types in XS, does
		2548	automatic timer adjustments even when no monotonic clock is available,
		2549	can take avdantage of advanced kernel interfaces such as C<epoll> and
		2550	C<kqueue>, and is the fastest backend I<by far>. You can even embed
		2551	L<Glib>/L<Gtk2> in it (or vice versa, see L<EV::Glib> and L<Glib::EV>).
		2552
		2553	If you only use backends that rely on another event loop (e.g. C<Tk>),
		2554	then this module will do nothing for you.
		2555
		2556	=item L<Guard>
		2557
		2558	The guard module, when used, will be used to implement
		2559	C<AnyEvent::Util::guard>. This speeds up guards considerably (and uses a
		2560	lot less memory), but otherwise doesn't affect guard operation much. It is
		2561	purely used for performance.
		2562
		2563	=item L<JSON> and L<JSON::XS>
		2564
		2565	One of these modules is required when you want to read or write JSON data
		2566	via L<AnyEvent::Handle>. L<JSON> is also written in pure-perl, but can take
		2567	advantage of the ultra-high-speed L<JSON::XS> module when it is installed.
		2568
		2569	=item L<Net::SSLeay>
		2570
		2571	Implementing TLS/SSL in Perl is certainly interesting, but not very
		2572	worthwhile: If this module is installed, then L<AnyEvent::Handle> (with
		2573	the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL.
		2574
		2575	=item L<Time::HiRes>
		2576
		2577	This module is part of perl since release 5.008. It will be used when the
		2578	chosen event library does not come with a timing source of its own. The
		2579	pure-perl event loop (L<AnyEvent::Impl::Perl>) will additionally use it to
		2580	try to use a monotonic clock for timing stability.
		2581
		2582	=back
		2583
1928		2584
1929	=head1 FORK	2585	=head1 FORK
1930		2586
1931	Most event libraries are not fork-safe. The ones who are usually are	2587	Most event libraries are not fork-safe. The ones who are usually are
1932	because they rely on inefficient but fork-safe C<select> or C<poll>	2588	because they rely on inefficient but fork-safe C<select> or C<poll> calls
1933	calls. Only L<EV> is fully fork-aware.	2589	- higher performance APIs such as BSD's kqueue or the dreaded Linux epoll
		2590	are usually badly thought-out hacks that are incompatible with fork in
		2591	one way or another. Only L<EV> is fully fork-aware and ensures that you
		2592	continue event-processing in both parent and child (or both, if you know
		2593	what you are doing).
		2594
		2595	This means that, in general, you cannot fork and do event processing in
		2596	the child if the event library was initialised before the fork (which
		2597	usually happens when the first AnyEvent watcher is created, or the library
		2598	is loaded).
1934		2599
1935	If you have to fork, you must either do so I<before> creating your first	2600	If you have to fork, you must either do so I<before> creating your first
1936	watcher OR you must not use AnyEvent at all in the child.	2601	watcher OR you must not use AnyEvent at all in the child OR you must do
		2602	something completely out of the scope of AnyEvent.
		2603
		2604	The problem of doing event processing in the parent I<and> the child
		2605	is much more complicated: even for backends that I<are> fork-aware or
		2606	fork-safe, their behaviour is not usually what you want: fork clones all
		2607	watchers, that means all timers, I/O watchers etc. are active in both
		2608	parent and child, which is almost never what you want. USing C<exec>
		2609	to start worker children from some kind of manage rprocess is usually
		2610	preferred, because it is much easier and cleaner, at the expense of having
		2611	to have another binary.
1937		2612
1938		2613
1939	=head1 SECURITY CONSIDERATIONS	2614	=head1 SECURITY CONSIDERATIONS
1940		2615
1941	AnyEvent can be forced to load any event model via	2616	AnyEvent can be forced to load any event model via
…		…
1953	use AnyEvent;	2628	use AnyEvent;
1954		2629
1955	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can	2630	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1956	be used to probe what backend is used and gain other information (which is	2631	be used to probe what backend is used and gain other information (which is
1957	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and	2632	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
1958	$ENV{PERL_ANYEGENT_STRICT}.	2633	$ENV{PERL_ANYEVENT_STRICT}.
		2634
		2635	Note that AnyEvent will remove I<all> environment variables starting with
		2636	C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
		2637	enabled.
1959		2638
1960		2639
1961	=head1 BUGS	2640	=head1 BUGS
1962		2641
1963	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard	2642	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
…		…
1967	pronounced).	2646	pronounced).
1968		2647
1969		2648
1970	=head1 SEE ALSO	2649	=head1 SEE ALSO
1971		2650
		2651	Tutorial/Introduction: L<AnyEvent::Intro>.
		2652
		2653	FAQ: L<AnyEvent::FAQ>.
		2654
1972	Utility functions: L<AnyEvent::Util>.	2655	Utility functions: L<AnyEvent::Util>.
1973		2656
1974	Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>,	2657	Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>,
1975	L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.	2658	L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.
1976		2659
1977	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,	2660	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
1978	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,	2661	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
1979	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,	2662	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
1980	L<AnyEvent::Impl::POE>.	2663	L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>, L<Anyevent::Impl::Irssi>.
1981		2664
1982	Non-blocking file handles, sockets, TCP clients and	2665	Non-blocking file handles, sockets, TCP clients and
1983	servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>.	2666	servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>.
1984		2667
1985	Asynchronous DNS: L<AnyEvent::DNS>.	2668	Asynchronous DNS: L<AnyEvent::DNS>.
1986		2669
1987	Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>,	2670	Thread support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>.
1988		2671
1989	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.	2672	Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::IRC>,
		2673	L<AnyEvent::HTTP>.
1990		2674
1991		2675
1992	=head1 AUTHOR	2676	=head1 AUTHOR
1993		2677
1994	Marc Lehmann <schmorp@schmorp.de>	2678	Marc Lehmann <schmorp@schmorp.de>

Diff Legend

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