ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.176 by root, Wed Aug 20 12:37:21 2008 UTC vs.
Revision 1.378 by root, Fri Aug 26 18:08:07 2011 UTC

1	=head1 NAME	1	=head1 NAME
2		2
3	AnyEvent - provide framework for multiple event loops	3	AnyEvent - the DBI of event loop programming
4		4
5	EV, Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops	5	EV, Event, Glib, Tk, Perl, Event::Lib, Irssi, rxvt-unicode, IO::Async, Qt,
		6	FLTK and POE are various supported event loops/environments.
6		7
7	=head1 SYNOPSIS	8	=head1 SYNOPSIS
8		9
9	use AnyEvent;	10	use AnyEvent;
10		11
		12	# if you prefer function calls, look at the AE manpage for
		13	# an alternative API.
		14
		15	# file handle or descriptor readable
11	my $w = AnyEvent->io (fh => $fh, poll => "r|w", cb => sub { ... });	16	my $w = AnyEvent->io (fh => $fh, poll => "r", cb => sub { ... });
12		17
		18	# one-shot or repeating timers
13	my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });	19	my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });
14	my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...	20	my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...);
15		21
16	print AnyEvent->now; # prints current event loop time	22	print AnyEvent->now; # prints current event loop time
17	print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.	23	print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
18		24
		25	# POSIX signal
19	my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... });	26	my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... });
20		27
		28	# child process exit
21	my $w = AnyEvent->child (pid => $pid, cb => sub {	29	my $w = AnyEvent->child (pid => $pid, cb => sub {
22	my ($pid, $status) = @_;	30	my ($pid, $status) = @_;
23	...	31	...
24	});	32	});
		33
		34	# called when event loop idle (if applicable)
		35	my $w = AnyEvent->idle (cb => sub { ... });
25		36
26	my $w = AnyEvent->condvar; # stores whether a condition was flagged	37	my $w = AnyEvent->condvar; # stores whether a condition was flagged
27	$w->send; # wake up current and all future recv's	38	$w->send; # wake up current and all future recv's
28	$w->recv; # enters "main loop" till $condvar gets ->send	39	$w->recv; # enters "main loop" till $condvar gets ->send
29	# use a condvar in callback mode:	40	# use a condvar in callback mode:
…		…
32	=head1 INTRODUCTION/TUTORIAL	43	=head1 INTRODUCTION/TUTORIAL
33		44
34	This manpage is mainly a reference manual. If you are interested	45	This manpage is mainly a reference manual. If you are interested
35	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
36	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.
37		58
38	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)	59	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
39		60
40	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
41	nowadays. So what is different about AnyEvent?	62	nowadays. So what is different about AnyEvent?
…		…
57	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
58	model you use.	79	model you use.
59		80
60	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
61	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
62	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
63	cannot use anything else, as they are simply incompatible to everything	84	cannot use anything else, as they are simply incompatible to everything
64	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
65	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.
66		87
67	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works	88	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
68	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
69	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
70	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
71	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
72	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
73	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,
74	to AnyEvent, too, so it is future-proof).	95	so it is future-proof).
75		96
76	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
77	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
78	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
79	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
80	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
81	technically possible.	102	technically possible.
82		103
83	Of course, AnyEvent comes with a big (and fully optional!) toolbox	104	Of course, AnyEvent comes with a big (and fully optional!) toolbox
84	of useful functionality, such as an asynchronous DNS resolver, 100%	105	of useful functionality, such as an asynchronous DNS resolver, 100%
…		…
90	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
91	model, you should I<not> use this module.	112	model, you should I<not> use this module.
92		113
93	=head1 DESCRIPTION	114	=head1 DESCRIPTION
94		115
95	L<AnyEvent> provides an identical interface to multiple event loops. This	116	L<AnyEvent> provides a uniform interface to various event loops. This
96	allows module authors to utilise an event loop without forcing module	117	allows module authors to use event loop functionality without forcing
97	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
98	peacefully at any one time).	119	than one event loop cannot coexist peacefully).
99		120
100	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>
101	module.	122	module.
102		123
103	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
104	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
105	following modules is already loaded: L<EV>,	126	following modules is already loaded: L<EV>, L<AnyEvent::Loop>,
106	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
107	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
108	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
109	adaptor should always succeed) in the order given. The first one that can	130	available, the pure-perl L<AnyEvent::Loop> should always work, so
110	be successfully loaded will be used. If, after this, still none could be	131	the other two are not normally tried.
111	found, AnyEvent will fall back to a pure-perl event loop, which is not
112	very efficient, but should work everywhere.
113		132
114	Because AnyEvent first checks for modules that are already loaded, loading	133	Because AnyEvent first checks for modules that are already loaded, loading
115	an event model explicitly before first using AnyEvent will likely make	134	an event model explicitly before first using AnyEvent will likely make
116	that model the default. For example:	135	that model the default. For example:
117		136
…		…
119	use AnyEvent;	138	use AnyEvent;
120		139
121	# .. AnyEvent will likely default to Tk	140	# .. AnyEvent will likely default to Tk
122		141
123	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
124	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,
125	use AnyEvent so their modules work together with others seamlessly...	144	as very few modules hardcode event loops without announcing this very
		145	loudly.
126		146
127	The pure-perl implementation of AnyEvent is called	147	The pure-perl implementation of AnyEvent is called C<AnyEvent::Loop>. Like
128	C<AnyEvent::Impl::Perl>. Like other event modules you can load it	148	other event modules you can load it explicitly and enjoy the high
129	explicitly and enjoy the high availability of that event loop :)	149	availability of that event loop :)
130		150
131	=head1 WATCHERS	151	=head1 WATCHERS
132		152
133	AnyEvent has the central concept of a I<watcher>, which is an object that	153	AnyEvent has the central concept of a I<watcher>, which is an object that
134	stores relevant data for each kind of event you are waiting for, such as	154	stores relevant data for each kind of event you are waiting for, such as
…		…
137	These watchers are normal Perl objects with normal Perl lifetime. After	157	These watchers are normal Perl objects with normal Perl lifetime. After
138	creating a watcher it will immediately "watch" for events and invoke the	158	creating a watcher it will immediately "watch" for events and invoke the
139	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
140	is in control).	160	is in control).
141		161
		162	Note that B<callbacks must not permanently change global variables>
		163	potentially in use by the event loop (such as C<$_> or C<$[>) and that B<<
		164	callbacks must not C<die> >>. The former is good programming practice in
		165	Perl and the latter stems from the fact that exception handling differs
		166	widely between event loops.
		167
142	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
143	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
144	to it).	170	to it).
145		171
146	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.
147		173
148	Many watchers either are used with "recursion" (repeating timers for	174	Many watchers either are used with "recursion" (repeating timers for
149	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.
150		176
151	An any way to achieve that is this pattern:	177	One way to achieve that is this pattern:
152		178
153	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {	179	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
154	# you can use $w here, for example to undef it	180	# you can use $w here, for example to undef it
155	undef $w;	181	undef $w;
156	});	182	});
…		…
159	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
160	declared.	186	declared.
161		187
162	=head2 I/O WATCHERS	188	=head2 I/O WATCHERS
163		189
		190	$w = AnyEvent->io (
		191	fh => <filehandle_or_fileno>,
		192	poll => <"r" or "w">,
		193	cb => <callback>,
		194	);
		195
164	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
165	with the following mandatory key-value pairs as arguments:	197	with the following mandatory key-value pairs as arguments:
166		198
167	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for events	199	C<fh> is the Perl I<file handle> (or a naked file descriptor) to watch
168	(AnyEvent might or might not keep a reference to this file handle). C<poll>	200	for events (AnyEvent might or might not keep a reference to this file
		201	handle). Note that only file handles pointing to things for which
		202	non-blocking operation makes sense are allowed. This includes sockets,
		203	most character devices, pipes, fifos and so on, but not for example files
		204	or block devices.
		205
169	must be a string that is either C<r> or C<w>, which creates a watcher	206	C<poll> must be a string that is either C<r> or C<w>, which creates a
170	waiting for "r"eadable or "w"ritable events, respectively. C<cb> is the	207	watcher waiting for "r"eadable or "w"ritable events, respectively.
		208
171	callback to invoke each time the file handle becomes ready.	209	C<cb> is the callback to invoke each time the file handle becomes ready.
172		210
173	Although the callback might get passed parameters, their value and	211	Although the callback might get passed parameters, their value and
174	presence is undefined and you cannot rely on them. Portable AnyEvent	212	presence is undefined and you cannot rely on them. Portable AnyEvent
175	callbacks cannot use arguments passed to I/O watcher callbacks.	213	callbacks cannot use arguments passed to I/O watcher callbacks.
176		214
177	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.
178	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
179	underlying file descriptor.	217	underlying file descriptor.
180		218
181	Some event loops issue spurious readyness notifications, so you should	219	Some event loops issue spurious readiness notifications, so you should
182	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
183	handles.	221	handles.
184		222
185	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
186	watcher.	224	watcher.
…		…
191	undef $w;	229	undef $w;
192	});	230	});
193		231
194	=head2 TIME WATCHERS	232	=head2 TIME WATCHERS
195		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
196	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 >>
197	method with the following mandatory arguments:	243	method with the following mandatory arguments:
198		244
199	C<after> specifies after how many seconds (fractional values are	245	C<after> specifies after how many seconds (fractional values are
200	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
…		…
202		248
203	Although the callback might get passed parameters, their value and	249	Although the callback might get passed parameters, their value and
204	presence is undefined and you cannot rely on them. Portable AnyEvent	250	presence is undefined and you cannot rely on them. Portable AnyEvent
205	callbacks cannot use arguments passed to time watcher callbacks.	251	callbacks cannot use arguments passed to time watcher callbacks.
206		252
207	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
208	parameter, C<interval>, as a strictly positive number (> 0), then the	254	parameter, C<interval>, as a strictly positive number (> 0), then the
209	callback will be invoked regularly at that interval (in fractional	255	callback will be invoked regularly at that interval (in fractional
210	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
211	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.
212		258
213	The callback will be rescheduled before invoking the callback, but no	259	The callback will be rescheduled before invoking the callback, but no
214	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
215	only approximate.	261	only approximate.
216		262
217	Example: fire an event after 7.7 seconds.	263	Example: fire an event after 7.7 seconds.
218		264
219	my $w = AnyEvent->timer (after => 7.7, cb => sub {	265	my $w = AnyEvent->timer (after => 7.7, cb => sub {
…		…
237		283
238	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
239	use absolute time internally. This makes a difference when your clock	285	use absolute time internally. This makes a difference when your clock
240	"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
241	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
242	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.
243		289
244	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
245	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
246	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)
247	timers.	293	timers.
248		294
249	AnyEvent always prefers relative timers, if available, matching the	295	AnyEvent always prefers relative timers, if available, matching the
250	AnyEvent API.	296	AnyEvent API.
…		…
272	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
273	function to call when you want to know the current time.>	319	function to call when you want to know the current time.>
274		320
275	This function is also often faster then C<< AnyEvent->time >>, and	321	This function is also often faster then C<< AnyEvent->time >>, and
276	thus the preferred method if you want some timestamp (for example,	322	thus the preferred method if you want some timestamp (for example,
277	L<AnyEvent::Handle> uses this to update it's activity timeouts).	323	L<AnyEvent::Handle> uses this to update its activity timeouts).
278		324
279	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
280	with your timing, you can skip it without bad conscience.	326	with your timing; you can skip it without a bad conscience.
281		327
282	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>
283	and L<EV> and the following set-up:	329	and L<EV> and the following set-up:
284		330
285	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
286	time=500 (assume no other callbacks delay processing). In your callback,	332	time=500 (assume no other callbacks delay processing). In your callback,
287	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
288	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
289	after three seconds.	335	after three seconds.
290		336
…		…
308	In either case, if you care (and in most cases, you don't), then you	354	In either case, if you care (and in most cases, you don't), then you
309	can get whatever behaviour you want with any event loop, by taking the	355	can get whatever behaviour you want with any event loop, by taking the
310	difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into	356	difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into
311	account.	357	account.
312		358
		359	=item AnyEvent->now_update
		360
		361	Some event loops (such as L<EV> or L<AnyEvent::Loop>) cache the current
		362	time for each loop iteration (see the discussion of L<< AnyEvent->now >>,
		363	above).
		364
		365	When a callback runs for a long time (or when the process sleeps), then
		366	this "current" time will differ substantially from the real time, which
		367	might affect timers and time-outs.
		368
		369	When this is the case, you can call this method, which will update the
		370	event loop's idea of "current time".
		371
		372	A typical example would be a script in a web server (e.g. C<mod_perl>) -
		373	when mod_perl executes the script, then the event loop will have the wrong
		374	idea about the "current time" (being potentially far in the past, when the
		375	script ran the last time). In that case you should arrange a call to C<<
		376	AnyEvent->now_update >> each time the web server process wakes up again
		377	(e.g. at the start of your script, or in a handler).
		378
		379	Note that updating the time I<might> cause some events to be handled.
		380
313	=back	381	=back
314		382
315	=head2 SIGNAL WATCHERS	383	=head2 SIGNAL WATCHERS
		384
		385	$w = AnyEvent->signal (signal => <uppercase_signal_name>, cb => <callback>);
316		386
317	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
318	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
319	callback to be invoked whenever a signal occurs.	389	callback to be invoked whenever a signal occurs.
320		390
…		…
326	invocation, and callback invocation will be synchronous. Synchronous means	396	invocation, and callback invocation will be synchronous. Synchronous means
327	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,
328	but it is guaranteed not to interrupt any other callbacks.	398	but it is guaranteed not to interrupt any other callbacks.
329		399
330	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
331	between multiple watchers.	401	between multiple watchers, and AnyEvent will ensure that signals will not
		402	interrupt your program at bad times.
332		403
333	This watcher might use C<%SIG>, so programs overwriting those signals	404	This watcher might use C<%SIG> (depending on the event loop used),
334	directly will likely not work correctly.	405	so programs overwriting those signals directly will likely not work
		406	correctly.
335		407
336	Example: exit on SIGINT	408	Example: exit on SIGINT
337		409
338	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });	410	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
339		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
340	=head2 CHILD PROCESS WATCHERS	449	=head2 CHILD PROCESS WATCHERS
341		450
		451	$w = AnyEvent->child (pid => <process id>, cb => <callback>);
		452
342	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.
343		454
344	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,
345	watches for any child process exit). The watcher will trigger as often	456	using C<0> watches for any child process exit, on others this will
346	as status change for the child are received. This works by installing a	457	croak). The watcher will be triggered only when the child process has
347	signal handler for C<SIGCHLD>. The callback will be called with the pid	458	finished and an exit status is available, not on any trace events
348	and exit status (as returned by waitpid), so unlike other watcher types,	459	(stopped/continued).
349	you I<can> rely on child watcher callback arguments.	460
		461	The callback will be called with the pid and exit status (as returned by
		462	waitpid), so unlike other watcher types, you I<can> rely on child watcher
		463	callback arguments.
		464
		465	This watcher type works by installing a signal handler for C<SIGCHLD>,
		466	and since it cannot be shared, nothing else should use SIGCHLD or reap
		467	random child processes (waiting for specific child processes, e.g. inside
		468	C<system>, is just fine).
350		469
351	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
352	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
353	have exited already (and no SIGCHLD will be sent anymore).	472	have exited already (and no SIGCHLD will be sent anymore).
354		473
355	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
356	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
357	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.
358		480
359	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
360	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
361	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).	483	watcher before you C<fork> the child (alternatively, you can call
		484	C<AnyEvent::detect>).
		485
		486	As most event loops do not support waiting for child events, they will be
		487	emulated by AnyEvent in most cases, in which case the latency and race
		488	problems mentioned in the description of signal watchers apply.
362		489
363	Example: fork a process and wait for it	490	Example: fork a process and wait for it
364		491
365	my $done = AnyEvent->condvar;	492	my $done = AnyEvent->condvar;
366		493
…		…
376	);	503	);
377		504
378	# do something else, then wait for process exit	505	# do something else, then wait for process exit
379	$done->recv;	506	$done->recv;
380		507
		508	=head2 IDLE WATCHERS
		509
		510	$w = AnyEvent->idle (cb => <callback>);
		511
		512	This will repeatedly invoke the callback after the process becomes idle,
		513	until either the watcher is destroyed or new events have been detected.
		514
		515	Idle watchers are useful when there is a need to do something, but it
		516	is not so important (or wise) to do it instantly. The callback will be
		517	invoked only when there is "nothing better to do", which is usually
		518	defined as "all outstanding events have been handled and no new events
		519	have been detected". That means that idle watchers ideally get invoked
		520	when the event loop has just polled for new events but none have been
		521	detected. Instead of blocking to wait for more events, the idle watchers
		522	will be invoked.
		523
		524	Unfortunately, most event loops do not really support idle watchers (only
		525	EV, Event and Glib do it in a usable fashion) - for the rest, AnyEvent
		526	will simply call the callback "from time to time".
		527
		528	Example: read lines from STDIN, but only process them when the
		529	program is otherwise idle:
		530
		531	my @lines; # read data
		532	my $idle_w;
		533	my $io_w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
		534	push @lines, scalar <STDIN>;
		535
		536	# start an idle watcher, if not already done
		537	$idle_w ||= AnyEvent->idle (cb => sub {
		538	# handle only one line, when there are lines left
		539	if (my $line = shift @lines) {
		540	print "handled when idle: $line";
		541	} else {
		542	# otherwise disable the idle watcher again
		543	undef $idle_w;
		544	}
		545	});
		546	});
		547
381	=head2 CONDITION VARIABLES	548	=head2 CONDITION VARIABLES
		549
		550	$cv = AnyEvent->condvar;
		551
		552	$cv->send (<list>);
		553	my @res = $cv->recv;
382		554
383	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
384	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
385	will actively watch for new events and call your callbacks.	557	will actively watch for new events and call your callbacks.
386		558
387	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
388	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).
389		561
390	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
391	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.
392		566
393	Condition variables can be created by calling the C<< AnyEvent->condvar	567	Condition variables can be created by calling the C<< AnyEvent->condvar
394	>> method, usually without arguments. The only argument pair allowed is	568	>> method, usually without arguments. The only argument pair allowed is
395
396	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
397	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
398	the results).	571	the results).
399		572
400	After creation, the condition variable is "false" until it becomes "true"	573	After creation, the condition variable is "false" until it becomes "true"
401	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
402	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<<
403	->send >> method).	576	->send >> method).
404		577
405	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
406	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:
407	in time where multiple outstanding events have been processed. And yet	580
408	another way to call them is transactions - each condition variable can be	581	=over 4
409	used to represent a transaction, which finishes at some point and delivers	582
410	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
411		601
412	Condition variables are very useful to signal that something has finished,	602	Condition variables are very useful to signal that something has finished,
413	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,
414	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
415	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
…		…
428		618
429	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
430	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
431	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
432	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
433	it's C<new> method in your own C<new> method.	623	its C<new> method in your own C<new> method.
434		624
435	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
436	eventually calls C<< -> send >>, and the "consumer side", which waits	626	eventually calls C<< -> send >>, and the "consumer side", which waits
437	for the send to occur.	627	for the send to occur.
438		628
439	Example: wait for a timer.	629	Example: wait for a timer.
440		630
441	# wait till the result is ready	631	# condition: "wait till the timer is fired"
442	my $result_ready = AnyEvent->condvar;	632	my $timer_fired = AnyEvent->condvar;
443		633
444	# do something such as adding a timer	634	# create the timer - we could wait for, say
445	# or socket watcher the calls $result_ready->send	635	# a handle becomign ready, or even an
446	# when the "result" is ready.	636	# AnyEvent::HTTP request to finish, but
447	# in this case, we simply use a timer:	637	# in this case, we simply use a timer:
448	my $w = AnyEvent->timer (	638	my $w = AnyEvent->timer (
449	after => 1,	639	after => 1,
450	cb => sub { $result_ready->send },	640	cb => sub { $timer_fired->send },
451	);	641	);
452		642
453	# this "blocks" (while handling events) till the callback	643	# this "blocks" (while handling events) till the callback
454	# calls send	644	# calls ->send
455	$result_ready->recv;	645	$timer_fired->recv;
456		646
457	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
458	condition variables are also code references.	648	variables are also callable directly.
459		649
460	my $done = AnyEvent->condvar;	650	my $done = AnyEvent->condvar;
461	my $delay = AnyEvent->timer (after => 5, cb => $done);	651	my $delay = AnyEvent->timer (after => 5, cb => $done);
462	$done->recv;	652	$done->recv;
463		653
…		…
469		659
470	...	660	...
471		661
472	my @info = $couchdb->info->recv;	662	my @info = $couchdb->info->recv;
473		663
474	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
475	results are available:	665	results are available:
476		666
477	$couchdb->info->cb (sub {	667	$couchdb->info->cb (sub {
478	my @info = $_[0]->recv;	668	my @info = $_[0]->recv;
479	});	669	});
…		…
497	immediately from within send.	687	immediately from within send.
498		688
499	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
500	future C<< ->recv >> calls.	690	future C<< ->recv >> calls.
501		691
502	Condition variables are overloaded so one can call them directly	692	Condition variables are overloaded so one can call them directly (as if
503	(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
504	C<send>. Note, however, that many C-based event loops do not handle	694	C<send>.
505	overloading, so as tempting as it may be, passing a condition variable
506	instead of a callback does not work. Both the pure perl and EV loops
507	support overloading, however, as well as all functions that use perl to
508	invoke a callback (as in L<AnyEvent::Socket> and L<AnyEvent::DNS> for
509	example).
510		695
511	=item $cv->croak ($error)	696	=item $cv->croak ($error)
512		697
513	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
514	C<Carp::croak> with the given error message/object/scalar.	699	C<Carp::croak> with the given error message/object/scalar.
515		700
516	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
517	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.
518		707
519	=item $cv->begin ([group callback])	708	=item $cv->begin ([group callback])
520		709
521	=item $cv->end	710	=item $cv->end
522
523	These two methods are EXPERIMENTAL and MIGHT CHANGE.
524		711
525	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
526	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
527	to use a condition variable for the whole process.	714	to use a condition variable for the whole process.
528		715
529	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
530	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
531	>>, 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
532	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
533	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.
534		722
535	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:
536		730
537	my $cv = AnyEvent->condvar;	731	my $cv = AnyEvent->condvar;
538		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
539	my %result;	757	my %result;
540	$cv->begin (sub { $cv->send (\%result) });	758	$cv->begin (sub { shift->send (\%result) });
541		759
542	for my $host (@list_of_hosts) {	760	for my $host (@list_of_hosts) {
543	$cv->begin;	761	$cv->begin;
544	ping_host_then_call_callback $host, sub {	762	ping_host_then_call_callback $host, sub {
545	$result{$host} = ...;	763	$result{$host} = ...;
…		…
560	loop, which serves two important purposes: first, it sets the callback	778	loop, which serves two important purposes: first, it sets the callback
561	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
562	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
563	doesn't execute once).	781	doesn't execute once).
564		782
565	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
566	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
567	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
568	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>.
569		788
570	=back	789	=back
571		790
572	=head3 METHODS FOR CONSUMERS	791	=head3 METHODS FOR CONSUMERS
573		792
…		…
577	=over 4	796	=over 4
578		797
579	=item $cv->recv	798	=item $cv->recv
580		799
581	Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak	800	Wait (blocking if necessary) until the C<< ->send >> or C<< ->croak
582	>> methods have been called on c<$cv>, while servicing other watchers	801	>> methods have been called on C<$cv>, while servicing other watchers
583	normally.	802	normally.
584		803
585	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
586	will return immediately.	805	will return immediately.
587		806
…		…
589	function will call C<croak>.	808	function will call C<croak>.
590		809
591	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,
592	in scalar context only the first one will be returned.	811	in scalar context only the first one will be returned.
593		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
594	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
595	(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
596	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
597	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
598	condition variables with some kind of request results and supporting	824	condition variables with some kind of request results and supporting
599	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,
600	while still supporting blocking waits if the caller so desires).	826	while still supporting blocking waits if the caller so desires).
601		827
602	Another reason I<never> to C<< ->recv >> in a module is that you cannot
603	sensibly have two C<< ->recv >>'s in parallel, as that would require
604	multiple interpreters or coroutines/threads, none of which C<AnyEvent>
605	can supply.
606
607	The L<Coro> module, however, I<can> and I<does> supply coroutines and, in
608	fact, L<Coro::AnyEvent> replaces AnyEvent's condvars by coroutine-safe
609	versions and also integrates coroutines into AnyEvent, making blocking
610	C<< ->recv >> calls perfectly safe as long as they are done from another
611	coroutine (one that doesn't run the event loop).
612
613	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
614	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
615	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
616	waits otherwise.	831	waits otherwise.
617		832
618	=item $bool = $cv->ready	833	=item $bool = $cv->ready
…		…
624		839
625	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
626	replaces it before doing so.	841	replaces it before doing so.
627		842
628	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
629	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
630	variable itself. Calling C<recv> inside the callback or at any later time	845	condition variable itself. If the condition is already true, the
631	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.
632		848
633	=back	849	=back
634		850
		851	=head1 SUPPORTED EVENT LOOPS/BACKENDS
		852
		853	The available backend classes are (every class has its own manpage):
		854
		855	=over 4
		856
		857	=item Backends that are autoprobed when no other event loop can be found.
		858
		859	EV is the preferred backend when no other event loop seems to be in
		860	use. If EV is not installed, then AnyEvent will fall back to its own
		861	pure-perl implementation, which is available everywhere as it comes with
		862	AnyEvent itself.
		863
		864	AnyEvent::Impl::EV based on EV (interface to libev, best choice).
		865	AnyEvent::Impl::Perl pure-perl AnyEvent::Loop, fast and portable.
		866
		867	=item Backends that are transparently being picked up when they are used.
		868
		869	These will be used if they are already loaded when the first watcher
		870	is created, in which case it is assumed that the application is using
		871	them. This means that AnyEvent will automatically pick the right backend
		872	when the main program loads an event module before anything starts to
		873	create watchers. Nothing special needs to be done by the main program.
		874
		875	AnyEvent::Impl::Event based on Event, very stable, few glitches.
		876	AnyEvent::Impl::Glib based on Glib, slow but very stable.
		877	AnyEvent::Impl::Tk based on Tk, very broken.
		878	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
		879	AnyEvent::Impl::POE based on POE, very slow, some limitations.
		880	AnyEvent::Impl::Irssi used when running within irssi.
		881	AnyEvent::Impl::IOAsync based on IO::Async.
		882	AnyEvent::Impl::Cocoa based on Cocoa::EventLoop.
		883	AnyEvent::Impl::FLTK based on FLTK (fltk 2 binding).
		884
		885	=item Backends with special needs.
		886
		887	Qt requires the Qt::Application to be instantiated first, but will
		888	otherwise be picked up automatically. As long as the main program
		889	instantiates the application before any AnyEvent watchers are created,
		890	everything should just work.
		891
		892	AnyEvent::Impl::Qt based on Qt.
		893
		894	=item Event loops that are indirectly supported via other backends.
		895
		896	Some event loops can be supported via other modules:
		897
		898	There is no direct support for WxWidgets (L<Wx>) or L<Prima>.
		899
		900	B<WxWidgets> has no support for watching file handles. However, you can
		901	use WxWidgets through the POE adaptor, as POE has a Wx backend that simply
		902	polls 20 times per second, which was considered to be too horrible to even
		903	consider for AnyEvent.
		904
		905	B<Prima> is not supported as nobody seems to be using it, but it has a POE
		906	backend, so it can be supported through POE.
		907
		908	AnyEvent knows about both L<Prima> and L<Wx>, however, and will try to
		909	load L<POE> when detecting them, in the hope that POE will pick them up,
		910	in which case everything will be automatic.
		911
		912	=back
		913
635	=head1 GLOBAL VARIABLES AND FUNCTIONS	914	=head1 GLOBAL VARIABLES AND FUNCTIONS
636		915
		916	These are not normally required to use AnyEvent, but can be useful to
		917	write AnyEvent extension modules.
		918
637	=over 4	919	=over 4
638		920
639	=item $AnyEvent::MODEL	921	=item $AnyEvent::MODEL
640		922
641	Contains C<undef> until the first watcher is being created. Then it	923	Contains C<undef> until the first watcher is being created, before the
		924	backend has been autodetected.
		925
642	contains the event model that is being used, which is the name of the	926	Afterwards it contains the event model that is being used, which is the
643	Perl class implementing the model. This class is usually one of the	927	name of the Perl class implementing the model. This class is usually one
644	C<AnyEvent::Impl:xxx> modules, but can be any other class in the case	928	of the C<AnyEvent::Impl::xxx> modules, but can be any other class in the
645	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).	929	case AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode> it
646		930	will be C<urxvt::anyevent>).
647	The known classes so far are:
648
649	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
650	AnyEvent::Impl::Event based on Event, second best choice.
651	AnyEvent::Impl::Perl pure-perl implementation, fast and portable.
652	AnyEvent::Impl::Glib based on Glib, third-best choice.
653	AnyEvent::Impl::Tk based on Tk, very bad choice.
654	AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
655	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
656	AnyEvent::Impl::POE based on POE, not generic enough for full support.
657
658	There is no support for WxWidgets, as WxWidgets has no support for
659	watching file handles. However, you can use WxWidgets through the
660	POE Adaptor, as POE has a Wx backend that simply polls 20 times per
661	second, which was considered to be too horrible to even consider for
662	AnyEvent. Likewise, other POE backends can be used by AnyEvent by using
663	it's adaptor.
664
665	AnyEvent knows about L<Prima> and L<Wx> and will try to use L<POE> when
666	autodetecting them.
667		931
668	=item AnyEvent::detect	932	=item AnyEvent::detect
669		933
670	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model	934	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
671	if necessary. You should only call this function right before you would	935	if necessary. You should only call this function right before you would
672	have created an AnyEvent watcher anyway, that is, as late as possible at	936	have created an AnyEvent watcher anyway, that is, as late as possible at
673	runtime.	937	runtime, and not e.g. during initialisation of your module.
		938
		939	The effect of calling this function is as if a watcher had been created
		940	(specifically, actions that happen "when the first watcher is created"
		941	happen when calling detetc as well).
		942
		943	If you need to do some initialisation before AnyEvent watchers are
		944	created, use C<post_detect>.
674		945
675	=item $guard = AnyEvent::post_detect { BLOCK }	946	=item $guard = AnyEvent::post_detect { BLOCK }
676		947
677	Arranges for the code block to be executed as soon as the event model is	948	Arranges for the code block to be executed as soon as the event model is
678	autodetected (or immediately if this has already happened).	949	autodetected (or immediately if that has already happened).
		950
		951	The block will be executed I<after> the actual backend has been detected
		952	(C<$AnyEvent::MODEL> is set), but I<before> any watchers have been
		953	created, so it is possible to e.g. patch C<@AnyEvent::ISA> or do
		954	other initialisations - see the sources of L<AnyEvent::Strict> or
		955	L<AnyEvent::AIO> to see how this is used.
		956
		957	The most common usage is to create some global watchers, without forcing
		958	event module detection too early, for example, L<AnyEvent::AIO> creates
		959	and installs the global L<IO::AIO> watcher in a C<post_detect> block to
		960	avoid autodetecting the event module at load time.
679		961
680	If called in scalar or list context, then it creates and returns an object	962	If called in scalar or list context, then it creates and returns an object
681	that automatically removes the callback again when it is destroyed. See	963	that automatically removes the callback again when it is destroyed (or
		964	C<undef> when the hook was immediately executed). See L<AnyEvent::AIO> for
682	L<Coro::BDB> for a case where this is useful.	965	a case where this is useful.
		966
		967	Example: Create a watcher for the IO::AIO module and store it in
		968	C<$WATCHER>, but do so only do so after the event loop is initialised.
		969
		970	our WATCHER;
		971
		972	my $guard = AnyEvent::post_detect {
		973	$WATCHER = AnyEvent->io (fh => IO::AIO::poll_fileno, poll => 'r', cb => \&IO::AIO::poll_cb);
		974	};
		975
		976	# the ||= is important in case post_detect immediately runs the block,
		977	# as to not clobber the newly-created watcher. assigning both watcher and
		978	# post_detect guard to the same variable has the advantage of users being
		979	# able to just C<undef $WATCHER> if the watcher causes them grief.
		980
		981	$WATCHER ||= $guard;
683		982
684	=item @AnyEvent::post_detect	983	=item @AnyEvent::post_detect
685		984
686	If there are any code references in this array (you can C<push> to it	985	If there are any code references in this array (you can C<push> to it
687	before or after loading AnyEvent), then they will called directly after	986	before or after loading AnyEvent), then they will be called directly
688	the event loop has been chosen.	987	after the event loop has been chosen.
689		988
690	You should check C<$AnyEvent::MODEL> before adding to this array, though:	989	You should check C<$AnyEvent::MODEL> before adding to this array, though:
691	if it contains a true value then the event loop has already been detected,	990	if it is defined then the event loop has already been detected, and the
692	and the array will be ignored.	991	array will be ignored.
693		992
694	Best use C<AnyEvent::post_detect { BLOCK }> instead.	993	Best use C<AnyEvent::post_detect { BLOCK }> when your application allows
		994	it, as it takes care of these details.
		995
		996	This variable is mainly useful for modules that can do something useful
		997	when AnyEvent is used and thus want to know when it is initialised, but do
		998	not need to even load it by default. This array provides the means to hook
		999	into AnyEvent passively, without loading it.
		1000
		1001	Example: To load Coro::AnyEvent whenever Coro and AnyEvent are used
		1002	together, you could put this into Coro (this is the actual code used by
		1003	Coro to accomplish this):
		1004
		1005	if (defined $AnyEvent::MODEL) {
		1006	# AnyEvent already initialised, so load Coro::AnyEvent
		1007	require Coro::AnyEvent;
		1008	} else {
		1009	# AnyEvent not yet initialised, so make sure to load Coro::AnyEvent
		1010	# as soon as it is
		1011	push @AnyEvent::post_detect, sub { require Coro::AnyEvent };
		1012	}
		1013
		1014	=item AnyEvent::postpone { BLOCK }
		1015
		1016	Arranges for the block to be executed as soon as possible, but not before
		1017	the call itself returns. In practise, the block will be executed just
		1018	before the event loop polls for new events, or shortly afterwards.
		1019
		1020	This function never returns anything (to make the C<return postpone { ...
		1021	}> idiom more useful.
		1022
		1023	To understand the usefulness of this function, consider a function that
		1024	asynchronously does something for you and returns some transaction
		1025	object or guard to let you cancel the operation. For example,
		1026	C<AnyEvent::Socket::tcp_connect>:
		1027
		1028	# start a conenction attempt unless one is active
		1029	$self->{connect_guard} ||= AnyEvent::Socket::tcp_connect "www.example.net", 80, sub {
		1030	delete $self->{connect_guard};
		1031	...
		1032	};
		1033
		1034	Imagine that this function could instantly call the callback, for
		1035	example, because it detects an obvious error such as a negative port
		1036	number. Invoking the callback before the function returns causes problems
		1037	however: the callback will be called and will try to delete the guard
		1038	object. But since the function hasn't returned yet, there is nothing to
		1039	delete. When the function eventually returns it will assign the guard
		1040	object to C<< $self->{connect_guard} >>, where it will likely never be
		1041	deleted, so the program thinks it is still trying to connect.
		1042
		1043	This is where C<AnyEvent::postpone> should be used. Instead of calling the
		1044	callback directly on error:
		1045
		1046	$cb->(undef), return # signal error to callback, BAD!
		1047	if $some_error_condition;
		1048
		1049	It should use C<postpone>:
		1050
		1051	AnyEvent::postpone { $cb->(undef) }, return # signal error to callback, later
		1052	if $some_error_condition;
		1053
		1054	=item AnyEvent::log $level, $msg[, @args]
		1055
		1056	Log the given C<$msg> at the given C<$level>.
		1057
		1058	If L<AnyEvent::Log> is not loaded then this function makes a simple test
		1059	to see whether the message will be logged. If the test succeeds it will
		1060	load AnyEvent::Log and call C<AnyEvent::Log::log> - consequently, look at
		1061	the L<AnyEvent::Log> documentation for details.
		1062
		1063	If the test fails it will simply return.
		1064
		1065	If you want to sprinkle loads of logging calls around your code, consider
		1066	creating a logger callback with the C<AnyEvent::Log::logger> function,
		1067	which can reduce typing, codesize and can reduce the logging overhead
		1068	enourmously.
695		1069
696	=back	1070	=back
697		1071
698	=head1 WHAT TO DO IN A MODULE	1072	=head1 WHAT TO DO IN A MODULE
699		1073
…		…
710	because it will stall the whole program, and the whole point of using	1084	because it will stall the whole program, and the whole point of using
711	events is to stay interactive.	1085	events is to stay interactive.
712		1086
713	It is fine, however, to call C<< ->recv >> when the user of your module	1087	It is fine, however, to call C<< ->recv >> when the user of your module
714	requests it (i.e. if you create a http request object ad have a method	1088	requests it (i.e. if you create a http request object ad have a method
715	called C<results> that returns the results, it should call C<< ->recv >>	1089	called C<results> that returns the results, it may call C<< ->recv >>
716	freely, as the user of your module knows what she is doing. always).	1090	freely, as the user of your module knows what she is doing. Always).
717		1091
718	=head1 WHAT TO DO IN THE MAIN PROGRAM	1092	=head1 WHAT TO DO IN THE MAIN PROGRAM
719		1093
720	There will always be a single main program - the only place that should	1094	There will always be a single main program - the only place that should
721	dictate which event model to use.	1095	dictate which event model to use.
722		1096
723	If it doesn't care, it can just "use AnyEvent" and use it itself, or not	1097	If the program is not event-based, it need not do anything special, even
724	do anything special (it does not need to be event-based) and let AnyEvent	1098	when it depends on a module that uses an AnyEvent. If the program itself
725	decide which implementation to chose if some module relies on it.	1099	uses AnyEvent, but does not care which event loop is used, all it needs
		1100	to do is C<use AnyEvent>. In either case, AnyEvent will choose the best
		1101	available loop implementation.
726		1102
727	If the main program relies on a specific event model - for example, in	1103	If the main program relies on a specific event model - for example, in
728	Gtk2 programs you have to rely on the Glib module - you should load the	1104	Gtk2 programs you have to rely on the Glib module - you should load the
729	event module before loading AnyEvent or any module that uses it: generally	1105	event module before loading AnyEvent or any module that uses it: generally
730	speaking, you should load it as early as possible. The reason is that	1106	speaking, you should load it as early as possible. The reason is that
731	modules might create watchers when they are loaded, and AnyEvent will	1107	modules might create watchers when they are loaded, and AnyEvent will
732	decide on the event model to use as soon as it creates watchers, and it	1108	decide on the event model to use as soon as it creates watchers, and it
733	might chose the wrong one unless you load the correct one yourself.	1109	might choose the wrong one unless you load the correct one yourself.
734		1110
735	You can chose to use a pure-perl implementation by loading the	1111	You can chose to use a pure-perl implementation by loading the
736	C<AnyEvent::Impl::Perl> module, which gives you similar behaviour	1112	C<AnyEvent::Loop> module, which gives you similar behaviour
737	everywhere, but letting AnyEvent chose the model is generally better.	1113	everywhere, but letting AnyEvent chose the model is generally better.
738		1114
739	=head2 MAINLOOP EMULATION	1115	=head2 MAINLOOP EMULATION
740		1116
741	Sometimes (often for short test scripts, or even standalone programs who	1117	Sometimes (often for short test scripts, or even standalone programs who
…		…
754		1130
755		1131
756	=head1 OTHER MODULES	1132	=head1 OTHER MODULES
757		1133
758	The following is a non-exhaustive list of additional modules that use	1134	The following is a non-exhaustive list of additional modules that use
759	AnyEvent and can therefore be mixed easily with other AnyEvent modules	1135	AnyEvent as a client and can therefore be mixed easily with other
760	in the same program. Some of the modules come with AnyEvent, some are	1136	AnyEvent modules and other event loops in the same program. Some of the
761	available via CPAN.	1137	modules come as part of AnyEvent, the others are available via CPAN (see
		1138	L<http://search.cpan.org/search?m=module&q=anyevent%3A%3A*> for
		1139	a longer non-exhaustive list), and the list is heavily biased towards
		1140	modules of the AnyEvent author himself :)
762		1141
763	=over 4	1142	=over 4
764		1143
765	=item L<AnyEvent::Util>	1144	=item L<AnyEvent::Util>
766		1145
767	Contains various utility functions that replace often-used but blocking	1146	Contains various utility functions that replace often-used blocking
768	functions such as C<inet_aton> by event-/callback-based versions.	1147	functions such as C<inet_aton> with event/callback-based versions.
769		1148
770	=item L<AnyEvent::Socket>	1149	=item L<AnyEvent::Socket>
771		1150
772	Provides various utility functions for (internet protocol) sockets,	1151	Provides various utility functions for (internet protocol) sockets,
773	addresses and name resolution. Also functions to create non-blocking tcp	1152	addresses and name resolution. Also functions to create non-blocking tcp
…		…
775		1154
776	=item L<AnyEvent::Handle>	1155	=item L<AnyEvent::Handle>
777		1156
778	Provide read and write buffers, manages watchers for reads and writes,	1157	Provide read and write buffers, manages watchers for reads and writes,
779	supports raw and formatted I/O, I/O queued and fully transparent and	1158	supports raw and formatted I/O, I/O queued and fully transparent and
780	non-blocking SSL/TLS.	1159	non-blocking SSL/TLS (via L<AnyEvent::TLS>).
781		1160
782	=item L<AnyEvent::DNS>	1161	=item L<AnyEvent::DNS>
783		1162
784	Provides rich asynchronous DNS resolver capabilities.	1163	Provides rich asynchronous DNS resolver capabilities.
785		1164
		1165	=item L<AnyEvent::HTTP>, L<AnyEvent::IRC>, L<AnyEvent::XMPP>, L<AnyEvent::GPSD>, L<AnyEvent::IGS>, L<AnyEvent::FCP>
		1166
		1167	Implement event-based interfaces to the protocols of the same name (for
		1168	the curious, IGS is the International Go Server and FCP is the Freenet
		1169	Client Protocol).
		1170
786	=item L<AnyEvent::HTTP>	1171	=item L<AnyEvent::AIO>
787		1172
788	A simple-to-use HTTP library that is capable of making a lot of concurrent	1173	Truly asynchronous (as opposed to non-blocking) I/O, should be in the
789	HTTP requests.	1174	toolbox of every event programmer. AnyEvent::AIO transparently fuses
		1175	L<IO::AIO> and AnyEvent together, giving AnyEvent access to event-based
		1176	file I/O, and much more.
		1177
		1178	=item L<AnyEvent::Filesys::Notify>
		1179
		1180	AnyEvent is good for non-blocking stuff, but it can't detect file or
		1181	path changes (e.g. "watch this directory for new files", "watch this
		1182	file for changes"). The L<AnyEvent::Filesys::Notify> module promises to
		1183	do just that in a portbale fashion, supporting inotify on GNU/Linux and
		1184	some weird, without doubt broken, stuff on OS X to monitor files. It can
		1185	fall back to blocking scans at regular intervals transparently on other
		1186	platforms, so it's about as portable as it gets.
		1187
		1188	(I haven't used it myself, but I haven't heard anybody complaining about
		1189	it yet).
		1190
		1191	=item L<AnyEvent::DBI>
		1192
		1193	Executes L<DBI> requests asynchronously in a proxy process for you,
		1194	notifying you in an event-based way when the operation is finished.
790		1195
791	=item L<AnyEvent::HTTPD>	1196	=item L<AnyEvent::HTTPD>
792		1197
793	Provides a simple web application server framework.	1198	A simple embedded webserver.
794		1199
795	=item L<AnyEvent::FastPing>	1200	=item L<AnyEvent::FastPing>
796		1201
797	The fastest ping in the west.	1202	The fastest ping in the west.
798		1203
799	=item L<AnyEvent::DBI>
800
801	Executes L<DBI> requests asynchronously in a proxy process.
802
803	=item L<AnyEvent::AIO>
804
805	Truly asynchronous I/O, should be in the toolbox of every event
806	programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
807	together.
808
809	=item L<AnyEvent::BDB>
810
811	Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
812	L<BDB> and AnyEvent together.
813
814	=item L<AnyEvent::GPSD>
815
816	A non-blocking interface to gpsd, a daemon delivering GPS information.
817
818	=item L<AnyEvent::IGS>
819
820	A non-blocking interface to the Internet Go Server protocol (used by
821	L<App::IGS>).
822
823	=item L<Net::IRC3>
824
825	AnyEvent based IRC client module family.
826
827	=item L<Net::XMPP2>
828
829	AnyEvent based XMPP (Jabber protocol) module family.
830
831	=item L<Net::FCP>
832
833	AnyEvent-based implementation of the Freenet Client Protocol, birthplace
834	of AnyEvent.
835
836	=item L<Event::ExecFlow>
837
838	High level API for event-based execution flow control.
839
840	=item L<Coro>	1204	=item L<Coro>
841		1205
842	Has special support for AnyEvent via L<Coro::AnyEvent>.	1206	Has special support for AnyEvent via L<Coro::AnyEvent>, which allows you
		1207	to simply invert the flow control - don't call us, we will call you:
843		1208
844	=item L<IO::Lambda>	1209	async {
		1210	Coro::AnyEvent::sleep 5; # creates a 5s timer and waits for it
		1211	print "5 seconds later!\n";
845		1212
846	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.	1213	Coro::AnyEvent::readable *STDIN; # uses an I/O watcher
		1214	my $line = <STDIN>; # works for ttys
		1215
		1216	AnyEvent::HTTP::http_get "url", Coro::rouse_cb;
		1217	my ($body, $hdr) = Coro::rouse_wait;
		1218	};
847		1219
848	=back	1220	=back
849		1221
850	=cut	1222	=cut
851		1223
852	package AnyEvent;	1224	package AnyEvent;
853		1225
854	no warnings;	1226	# basically a tuned-down version of common::sense
855	use strict;	1227	sub common_sense {
		1228	# from common:.sense 3.4
		1229	${^WARNING_BITS} ^= ${^WARNING_BITS} ^ "\x3c\x3f\x33\x00\x0f\xf0\x0f\xc0\xf0\xfc\x33\x00";
		1230	# use strict vars subs - NO UTF-8, as Util.pm doesn't like this atm. (uts46data.pl)
		1231	$^H |= 0x00000600;
		1232	}
856		1233
		1234	BEGIN { AnyEvent::common_sense }
		1235
857	use Carp;	1236	use Carp ();
858		1237
859	our $VERSION = 4.231;	1238	our $VERSION = '6.01';
860	our $MODEL;	1239	our $MODEL;
861		1240
862	our $AUTOLOAD;
863	our @ISA;	1241	our @ISA;
864		1242
865	our @REGISTRY;	1243	our @REGISTRY;
866		1244
867	our $WIN32;	1245	our $VERBOSE;
868		1246
869	BEGIN {	1247	BEGIN {
870	my $win32 = ! ! ($^O =~ /mswin32/i);	1248	require "AnyEvent/constants.pl";
871	eval "sub WIN32(){ $win32 }";
872	}
873		1249
		1250	eval "sub TAINT (){" . (${^TAINT}*1) . "}";
		1251
		1252	delete @ENV{grep /^PERL_ANYEVENT_/, keys %ENV}
		1253	if ${^TAINT};
		1254
		1255	$ENV{"PERL_ANYEVENT_$_"} = $ENV{"AE_$_"}
		1256	for grep s/^AE_// && !exists $ENV{"PERL_ANYEVENT_$_"}, keys %ENV;
		1257
		1258	@ENV{grep /^PERL_ANYEVENT_/, keys %ENV} = ()
		1259	if ${^TAINT};
		1260
874	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;	1261	$VERBOSE = $ENV{PERL_ANYEVENT_VERBOSE}*1;
		1262	}
		1263
		1264	our $MAX_SIGNAL_LATENCY = 10;
875		1265
876	our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred	1266	our %PROTOCOL; # (ipv4|ipv6) => (1|2), higher numbers are preferred
877		1267
878	{	1268	{
879	my $idx;	1269	my $idx;
880	$PROTOCOL{$_} = ++$idx	1270	$PROTOCOL{$_} = ++$idx
881	for reverse split /\s*,\s*/,	1271	for reverse split /\s*,\s*/,
882	$ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";	1272	$ENV{PERL_ANYEVENT_PROTOCOLS} || "ipv4,ipv6";
883	}	1273	}
884		1274
		1275	our @post_detect;
		1276
		1277	sub post_detect(&) {
		1278	my ($cb) = @_;
		1279
		1280	push @post_detect, $cb;
		1281
		1282	defined wantarray
		1283	? bless \$cb, "AnyEvent::Util::postdetect"
		1284	: ()
		1285	}
		1286
		1287	sub AnyEvent::Util::postdetect::DESTROY {
		1288	@post_detect = grep $_ != ${$_[0]}, @post_detect;
		1289	}
		1290
		1291	our $POSTPONE_W;
		1292	our @POSTPONE;
		1293
		1294	sub _postpone_exec {
		1295	undef $POSTPONE_W;
		1296
		1297	&{ shift @POSTPONE }
		1298	while @POSTPONE;
		1299	}
		1300
		1301	sub postpone(&) {
		1302	push @POSTPONE, shift;
		1303
		1304	$POSTPONE_W ||= AE::timer (0, 0, \&_postpone_exec);
		1305
		1306	()
		1307	}
		1308
		1309	sub log($$;@) {
		1310	# only load the big bloated module when we actually are about to log something
		1311	if ($_[0] <= $VERBOSE) { # also catches non-numeric levels(!)
		1312	require AnyEvent::Log;
		1313	# AnyEvent::Log overwrites this function
		1314	goto &log;
		1315	}
		1316
		1317	0 # not logged
		1318	}
		1319
		1320	if (length $ENV{PERL_ANYEVENT_LOG}) {
		1321	require AnyEvent::Log; # AnyEvent::Log does the thing for us
		1322	}
		1323
885	my @models = (	1324	our @models = (
886	[EV:: => AnyEvent::Impl::EV::],	1325	[EV:: => AnyEvent::Impl::EV:: , 1],
887	[Event:: => AnyEvent::Impl::Event::],	1326	[AnyEvent::Loop:: => AnyEvent::Impl::Perl:: , 1],
888	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
889	# everything below here will not be autoprobed	1327	# everything below here will not (normally) be autoprobed
890	# as the pureperl backend should work everywhere	1328	# as the pure perl backend should work everywhere
891	# and is usually faster	1329	# and is usually faster
		1330	[Event:: => AnyEvent::Impl::Event::, 1],
		1331	[Glib:: => AnyEvent::Impl::Glib:: , 1], # becomes extremely slow with many watchers
		1332	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
		1333	[Irssi:: => AnyEvent::Impl::Irssi::], # Irssi has a bogus "Event" package
892	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles	1334	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
893	[Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers
894	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
895	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program	1335	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program
896	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza	1336	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
897	[Wx:: => AnyEvent::Impl::POE::],	1337	[Wx:: => AnyEvent::Impl::POE::],
898	[Prima:: => AnyEvent::Impl::POE::],	1338	[Prima:: => AnyEvent::Impl::POE::],
		1339	[IO::Async::Loop:: => AnyEvent::Impl::IOAsync::], # a bitch to autodetect
		1340	[Cocoa::EventLoop:: => AnyEvent::Impl::Cocoa::],
		1341	[FLTK:: => AnyEvent::Impl::FLTK::],
899	);	1342	);
900		1343
901	our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY);	1344	our @isa_hook;
902		1345
903	our @post_detect;	1346	sub _isa_set {
		1347	my @pkg = ("AnyEvent", (map $_->[0], grep defined, @isa_hook), $MODEL);
904		1348
		1349	@{"$pkg[$_-1]::ISA"} = $pkg[$_]
		1350	for 1 .. $#pkg;
		1351
		1352	grep $_ && $_->[1], @isa_hook
		1353	and AE::_reset ();
		1354	}
		1355
		1356	# used for hooking AnyEvent::Strict and AnyEvent::Debug::Wrap into the class hierarchy
		1357	sub _isa_hook($$;$) {
		1358	my ($i, $pkg, $reset_ae) = @_;
		1359
		1360	$isa_hook[$i] = $pkg ? [$pkg, $reset_ae] : undef;
		1361
		1362	_isa_set;
		1363	}
		1364
		1365	# all autoloaded methods reserve the complete glob, not just the method slot.
		1366	# due to bugs in perls method cache implementation.
		1367	our @methods = qw(io timer time now now_update signal child idle condvar);
		1368
905	sub post_detect(&) {	1369	sub detect() {
906	my ($cb) = @_;	1370	return $MODEL if $MODEL; # some programs keep references to detect
907		1371
908	if ($MODEL) {	1372	local $!; # for good measure
909	$cb->();	1373	local $SIG{__DIE__}; # we use eval
910		1374
911	1	1375	# free some memory
		1376	*detect = sub () { $MODEL };
		1377	# undef &func doesn't correctly update the method cache. grmbl.
		1378	# so we delete the whole glob. grmbl.
		1379	# otoh, perl doesn't let me undef an active usb, but it lets me free
		1380	# a glob with an active sub. hrm. i hope it works, but perl is
		1381	# usually buggy in this department. sigh.
		1382	delete @{"AnyEvent::"}{@methods};
		1383	undef @methods;
		1384
		1385	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z0-9:]+)$/) {
		1386	my $model = $1;
		1387	$model = "AnyEvent::Impl::$model" unless $model =~ s/::$//;
		1388	if (eval "require $model") {
		1389	AnyEvent::log 7 => "loaded model '$model' (forced by \$ENV{PERL_ANYEVENT_MODEL}), using it.";
		1390	$MODEL = $model;
912	} else {	1391	} else {
913	push @post_detect, $cb;	1392	AnyEvent::log 5 => "unable to load model '$model' (from \$ENV{PERL_ANYEVENT_MODEL}):\n$@";
914		1393	}
915	defined wantarray
916	? bless \$cb, "AnyEvent::Util::PostDetect"
917	: ()
918	}	1394	}
919	}
920		1395
921	sub AnyEvent::Util::PostDetect::DESTROY {	1396	# check for already loaded models
922	@post_detect = grep $_ != ${$_[0]}, @post_detect;
923	}
924
925	sub detect() {
926	unless ($MODEL) {	1397	unless ($MODEL) {
927	no strict 'refs';	1398	for (@REGISTRY, @models) {
928	local $SIG{__DIE__};	1399	my ($package, $model) = @$_;
929		1400	if (${"$package\::VERSION"} > 0) {
930	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
931	my $model = "AnyEvent::Impl::$1";
932	if (eval "require $model") {	1401	if (eval "require $model") {
		1402	AnyEvent::log 7 => "autodetected model '$model', using it.";
933	$MODEL = $model;	1403	$MODEL = $model;
934	warn "AnyEvent: loaded model '$model' (forced by \$PERL_ANYEVENT_MODEL), using it.\n" if $verbose > 1;	1404	last;
935	} else {	1405	}
936	warn "AnyEvent: unable to load model '$model' (from \$PERL_ANYEVENT_MODEL):\n$@" if $verbose;
937	}	1406	}
938	}	1407	}
939		1408
940	# check for already loaded models
941	unless ($MODEL) {	1409	unless ($MODEL) {
		1410	# try to autoload a model
942	for (@REGISTRY, @models) {	1411	for (@REGISTRY, @models) {
943	my ($package, $model) = @$_;	1412	my ($package, $model, $autoload) = @$_;
		1413	if (
		1414	$autoload
		1415	and eval "require $package"
944	if (${"$package\::VERSION"} > 0) {	1416	and ${"$package\::VERSION"} > 0
945	if (eval "require $model") {	1417	and eval "require $model"
		1418	) {
		1419	AnyEvent::log 7 => "autoloaded model '$model', using it.";
946	$MODEL = $model;	1420	$MODEL = $model;
947	warn "AnyEvent: autodetected model '$model', using it.\n" if $verbose > 1;
948	last;	1421	last;
949	}
950	}	1422	}
951	}	1423	}
952		1424
953	unless ($MODEL) {
954	# try to load a model
955
956	for (@REGISTRY, @models) {
957	my ($package, $model) = @$_;
958	if (eval "require $package"
959	and ${"$package\::VERSION"} > 0
960	and eval "require $model") {
961	$MODEL = $model;
962	warn "AnyEvent: autoprobed model '$model', using it.\n" if $verbose > 1;
963	last;
964	}
965	}
966
967	$MODEL	1425	$MODEL
968	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";	1426	or die "AnyEvent: backend autodetection failed - did you properly install AnyEvent?";
969	}
970	}	1427	}
971
972	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
973
974	unshift @ISA, $MODEL;
975
976	require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
977
978	(shift @post_detect)->() while @post_detect;
979	}	1428	}
980		1429
		1430	# free memory only needed for probing
		1431	undef @models;
		1432	undef @REGISTRY;
		1433
		1434	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
		1435
		1436	# now nuke some methods that are overridden by the backend.
		1437	# SUPER usage is not allowed in these.
		1438	for (qw(time signal child idle)) {
		1439	undef &{"AnyEvent::Base::$_"}
		1440	if defined &{"$MODEL\::$_"};
		1441	}
		1442
		1443	_isa_set;
		1444
		1445	# we're officially open!
		1446
		1447	if ($ENV{PERL_ANYEVENT_STRICT}) {
		1448	require AnyEvent::Strict;
		1449	}
		1450
		1451	if ($ENV{PERL_ANYEVENT_DEBUG_WRAP}) {
		1452	require AnyEvent::Debug;
		1453	AnyEvent::Debug::wrap ($ENV{PERL_ANYEVENT_DEBUG_WRAP});
		1454	}
		1455
		1456	if (length $ENV{PERL_ANYEVENT_DEBUG_SHELL}) {
		1457	require AnyEvent::Socket;
		1458	require AnyEvent::Debug;
		1459
		1460	my $shell = $ENV{PERL_ANYEVENT_DEBUG_SHELL};
		1461	$shell =~ s/\$\$/$$/g;
		1462
		1463	my ($host, $service) = AnyEvent::Socket::parse_hostport ($shell);
		1464	$AnyEvent::Debug::SHELL = AnyEvent::Debug::shell ($host, $service);
		1465	}
		1466
		1467	# now the anyevent environment is set up as the user told us to, so
		1468	# call the actual user code - post detects
		1469
		1470	(shift @post_detect)->() while @post_detect;
		1471	undef @post_detect;
		1472
		1473	*post_detect = sub(&) {
		1474	shift->();
		1475
		1476	undef
		1477	};
		1478
981	$MODEL	1479	$MODEL
982	}	1480	}
983		1481
984	sub AUTOLOAD {	1482	for my $name (@methods) {
985	(my $func = $AUTOLOAD) =~ s/.*://;	1483	*$name = sub {
986		1484	detect;
987	$method{$func}	1485	# we use goto because
988	or croak "$func: not a valid method for AnyEvent objects";	1486	# a) it makes the thunk more transparent
989		1487	# b) it allows us to delete the thunk later
990	detect unless $MODEL;	1488	goto &{ UNIVERSAL::can AnyEvent => "SUPER::$name" }
991		1489	};
992	my $class = shift;
993	$class->$func (@_);
994	}	1490	}
995		1491
996	# utility function to dup a filehandle. this is used by many backends	1492	# utility function to dup a filehandle. this is used by many backends
997	# to support binding more than one watcher per filehandle (they usually	1493	# to support binding more than one watcher per filehandle (they usually
998	# allow only one watcher per fd, so we dup it to get a different one).	1494	# allow only one watcher per fd, so we dup it to get a different one).
999	sub _dupfh($$$$) {	1495	sub _dupfh($$;$$) {
1000	my ($poll, $fh, $r, $w) = @_;	1496	my ($poll, $fh, $r, $w) = @_;
1001		1497
1002	require Fcntl;
1003
1004	# cygwin requires the fh mode to be matching, unix doesn't	1498	# cygwin requires the fh mode to be matching, unix doesn't
1005	my ($rw, $mode) = $poll eq "r" ? ($r, "<")	1499	my ($rw, $mode) = $poll eq "r" ? ($r, "<&") : ($w, ">&");
1006	: $poll eq "w" ? ($w, ">")
1007	: Carp::croak "AnyEvent->io requires poll set to either 'r' or 'w'";
1008		1500
1009	open my $fh2, "$mode&" . fileno $fh	1501	open my $fh2, $mode, $fh
1010	or die "cannot dup() filehandle: $!";	1502	or die "AnyEvent->io: cannot dup() filehandle in mode '$poll': $!,";
1011		1503
1012	# we assume CLOEXEC is already set by perl in all important cases	1504	# we assume CLOEXEC is already set by perl in all important cases
1013		1505
1014	($fh2, $rw)	1506	($fh2, $rw)
1015	}	1507	}
1016		1508
		1509	=head1 SIMPLIFIED AE API
		1510
		1511	Starting with version 5.0, AnyEvent officially supports a second, much
		1512	simpler, API that is designed to reduce the calling, typing and memory
		1513	overhead by using function call syntax and a fixed number of parameters.
		1514
		1515	See the L<AE> manpage for details.
		1516
		1517	=cut
		1518
		1519	package AE;
		1520
		1521	our $VERSION = $AnyEvent::VERSION;
		1522
		1523	sub _reset() {
		1524	eval q{
		1525	# fall back to the main API by default - backends and AnyEvent::Base
		1526	# implementations can overwrite these.
		1527
		1528	sub io($$$) {
		1529	AnyEvent->io (fh => $_[0], poll => $_[1] ? "w" : "r", cb => $_[2])
		1530	}
		1531
		1532	sub timer($$$) {
		1533	AnyEvent->timer (after => $_[0], interval => $_[1], cb => $_[2])
		1534	}
		1535
		1536	sub signal($$) {
		1537	AnyEvent->signal (signal => $_[0], cb => $_[1])
		1538	}
		1539
		1540	sub child($$) {
		1541	AnyEvent->child (pid => $_[0], cb => $_[1])
		1542	}
		1543
		1544	sub idle($) {
		1545	AnyEvent->idle (cb => $_[0]);
		1546	}
		1547
		1548	sub cv(;&) {
		1549	AnyEvent->condvar (@_ ? (cb => $_[0]) : ())
		1550	}
		1551
		1552	sub now() {
		1553	AnyEvent->now
		1554	}
		1555
		1556	sub now_update() {
		1557	AnyEvent->now_update
		1558	}
		1559
		1560	sub time() {
		1561	AnyEvent->time
		1562	}
		1563
		1564	*postpone = \&AnyEvent::postpone;
		1565	*log = \&AnyEvent::log;
		1566	};
		1567	die if $@;
		1568	}
		1569
		1570	BEGIN { _reset }
		1571
1017	package AnyEvent::Base;	1572	package AnyEvent::Base;
1018		1573
1019	# default implementation for now and time	1574	# default implementations for many methods
1020		1575
1021	use Time::HiRes ();	1576	sub time {
		1577	eval q{ # poor man's autoloading {}
		1578	# probe for availability of Time::HiRes
		1579	if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {
		1580	*time = sub { Time::HiRes::time () };
		1581	*AE::time = \& Time::HiRes::time ;
		1582	*now = \&time;
		1583	AnyEvent::log 8 => "AnyEvent: using Time::HiRes for sub-second timing accuracy.";
		1584	# if (eval "use POSIX (); (POSIX::times())...
		1585	} else {
		1586	*time = sub { CORE::time };
		1587	*AE::time = sub (){ CORE::time };
		1588	*now = \&time;
		1589	AnyEvent::log 3 => "using built-in time(), WARNING, no sub-second resolution!";
		1590	}
		1591	};
		1592	die if $@;
1022		1593
1023	sub time { Time::HiRes::time }	1594	&time
1024	sub now { Time::HiRes::time }	1595	}
		1596
		1597	*now = \&time;
		1598	sub now_update { }
		1599
		1600	sub _poll {
		1601	Carp::croak "$AnyEvent::MODEL does not support blocking waits. Caught";
		1602	}
1025		1603
1026	# default implementation for ->condvar	1604	# default implementation for ->condvar
		1605	# in fact, the default should not be overwritten
1027		1606
1028	sub condvar {	1607	sub condvar {
		1608	eval q{ # poor man's autoloading {}
		1609	*condvar = sub {
1029	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::	1610	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, "AnyEvent::CondVar"
		1611	};
		1612
		1613	*AE::cv = sub (;&) {
		1614	bless { @_ ? (_ae_cb => shift) : () }, "AnyEvent::CondVar"
		1615	};
		1616	};
		1617	die if $@;
		1618
		1619	&condvar
1030	}	1620	}
1031		1621
1032	# default implementation for ->signal	1622	# default implementation for ->signal
1033		1623
1034	our %SIG_CB;	1624	our $HAVE_ASYNC_INTERRUPT;
		1625
		1626	sub _have_async_interrupt() {
		1627	$HAVE_ASYNC_INTERRUPT = 1*(!$ENV{PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT}
		1628	&& eval "use Async::Interrupt 1.02 (); 1")
		1629	unless defined $HAVE_ASYNC_INTERRUPT;
		1630
		1631	$HAVE_ASYNC_INTERRUPT
		1632	}
		1633
		1634	our ($SIGPIPE_R, $SIGPIPE_W, %SIG_CB, %SIG_EV, $SIG_IO);
		1635	our (%SIG_ASY, %SIG_ASY_W);
		1636	our ($SIG_COUNT, $SIG_TW);
		1637
		1638	# install a dummy wakeup watcher to reduce signal catching latency
		1639	# used by Impls
		1640	sub _sig_add() {
		1641	unless ($SIG_COUNT++) {
		1642	# try to align timer on a full-second boundary, if possible
		1643	my $NOW = AE::now;
		1644
		1645	$SIG_TW = AE::timer
		1646	$MAX_SIGNAL_LATENCY - ($NOW - int $NOW),
		1647	$MAX_SIGNAL_LATENCY,
		1648	sub { } # just for the PERL_ASYNC_CHECK
		1649	;
		1650	}
		1651	}
		1652
		1653	sub _sig_del {
		1654	undef $SIG_TW
		1655	unless --$SIG_COUNT;
		1656	}
		1657
		1658	our $_sig_name_init; $_sig_name_init = sub {
		1659	eval q{ # poor man's autoloading {}
		1660	undef $_sig_name_init;
		1661
		1662	if (_have_async_interrupt) {
		1663	*sig2num = \&Async::Interrupt::sig2num;
		1664	*sig2name = \&Async::Interrupt::sig2name;
		1665	} else {
		1666	require Config;
		1667
		1668	my %signame2num;
		1669	@signame2num{ split ' ', $Config::Config{sig_name} }
		1670	= split ' ', $Config::Config{sig_num};
		1671
		1672	my @signum2name;
		1673	@signum2name[values %signame2num] = keys %signame2num;
		1674
		1675	*sig2num = sub($) {
		1676	$_[0] > 0 ? shift : $signame2num{+shift}
		1677	};
		1678	*sig2name = sub ($) {
		1679	$_[0] > 0 ? $signum2name[+shift] : shift
		1680	};
		1681	}
		1682	};
		1683	die if $@;
		1684	};
		1685
		1686	sub sig2num ($) { &$_sig_name_init; &sig2num }
		1687	sub sig2name($) { &$_sig_name_init; &sig2name }
1035		1688
1036	sub signal {	1689	sub signal {
		1690	eval q{ # poor man's autoloading {}
		1691	# probe for availability of Async::Interrupt
		1692	if (_have_async_interrupt) {
		1693	AnyEvent::log 8 => "using Async::Interrupt for race-free signal handling.";
		1694
		1695	$SIGPIPE_R = new Async::Interrupt::EventPipe;
		1696	$SIG_IO = AE::io $SIGPIPE_R->fileno, 0, \&_signal_exec;
		1697
		1698	} else {
		1699	AnyEvent::log 8 => "using emulated perl signal handling with latency timer.";
		1700
		1701	if (AnyEvent::WIN32) {
		1702	require AnyEvent::Util;
		1703
		1704	($SIGPIPE_R, $SIGPIPE_W) = AnyEvent::Util::portable_pipe ();
		1705	AnyEvent::Util::fh_nonblocking ($SIGPIPE_R, 1) if $SIGPIPE_R;
		1706	AnyEvent::Util::fh_nonblocking ($SIGPIPE_W, 1) if $SIGPIPE_W; # just in case
		1707	} else {
		1708	pipe $SIGPIPE_R, $SIGPIPE_W;
		1709	fcntl $SIGPIPE_R, AnyEvent::F_SETFL, AnyEvent::O_NONBLOCK if $SIGPIPE_R;
		1710	fcntl $SIGPIPE_W, AnyEvent::F_SETFL, AnyEvent::O_NONBLOCK if $SIGPIPE_W; # just in case
		1711
		1712	# not strictly required, as $^F is normally 2, but let's make sure...
		1713	fcntl $SIGPIPE_R, AnyEvent::F_SETFD, AnyEvent::FD_CLOEXEC;
		1714	fcntl $SIGPIPE_W, AnyEvent::F_SETFD, AnyEvent::FD_CLOEXEC;
		1715	}
		1716
		1717	$SIGPIPE_R
		1718	or Carp::croak "AnyEvent: unable to create a signal reporting pipe: $!\n";
		1719
		1720	$SIG_IO = AE::io $SIGPIPE_R, 0, \&_signal_exec;
		1721	}
		1722
		1723	*signal = $HAVE_ASYNC_INTERRUPT
		1724	? sub {
1037	my (undef, %arg) = @_;	1725	my (undef, %arg) = @_;
1038		1726
		1727	# async::interrupt
1039	my $signal = uc $arg{signal}	1728	my $signal = sig2num $arg{signal};
1040	or Carp::croak "required option 'signal' is missing";
1041
1042	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};	1729	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};
		1730
		1731	$SIG_ASY{$signal} ||= new Async::Interrupt
		1732	cb => sub { undef $SIG_EV{$signal} },
		1733	signal => $signal,
		1734	pipe => [$SIGPIPE_R->filenos],
		1735	pipe_autodrain => 0,
		1736	;
		1737
		1738	bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
		1739	}
		1740	: sub {
		1741	my (undef, %arg) = @_;
		1742
		1743	# pure perl
		1744	my $signal = sig2name $arg{signal};
		1745	$SIG_CB{$signal}{$arg{cb}} = $arg{cb};
		1746
1043	$SIG{$signal} ||= sub {	1747	$SIG{$signal} ||= sub {
		1748	local $!;
		1749	syswrite $SIGPIPE_W, "\x00", 1 unless %SIG_EV;
		1750	undef $SIG_EV{$signal};
		1751	};
		1752
		1753	# can't do signal processing without introducing races in pure perl,
		1754	# so limit the signal latency.
		1755	_sig_add;
		1756
		1757	bless [$signal, $arg{cb}], "AnyEvent::Base::signal"
		1758	}
		1759	;
		1760
		1761	*AnyEvent::Base::signal::DESTROY = sub {
		1762	my ($signal, $cb) = @{$_[0]};
		1763
		1764	_sig_del;
		1765
		1766	delete $SIG_CB{$signal}{$cb};
		1767
		1768	$HAVE_ASYNC_INTERRUPT
		1769	? delete $SIG_ASY{$signal}
		1770	: # delete doesn't work with older perls - they then
		1771	# print weird messages, or just unconditionally exit
		1772	# instead of getting the default action.
		1773	undef $SIG{$signal}
		1774	unless keys %{ $SIG_CB{$signal} };
		1775	};
		1776
		1777	*_signal_exec = sub {
		1778	$HAVE_ASYNC_INTERRUPT
		1779	? $SIGPIPE_R->drain
		1780	: sysread $SIGPIPE_R, (my $dummy), 9;
		1781
		1782	while (%SIG_EV) {
		1783	for (keys %SIG_EV) {
		1784	delete $SIG_EV{$_};
1044	$_->() for values %{ $SIG_CB{$signal} || {} };	1785	&$_ for values %{ $SIG_CB{$_} || {} };
		1786	}
		1787	}
		1788	};
1045	};	1789	};
		1790	die if $@;
1046		1791
1047	bless [$signal, $arg{cb}], "AnyEvent::Base::Signal"	1792	&signal
1048	}
1049
1050	sub AnyEvent::Base::Signal::DESTROY {
1051	my ($signal, $cb) = @{$_[0]};
1052
1053	delete $SIG_CB{$signal}{$cb};
1054
1055	delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
1056	}	1793	}
1057		1794
1058	# default implementation for ->child	1795	# default implementation for ->child
1059		1796
1060	our %PID_CB;	1797	our %PID_CB;
1061	our $CHLD_W;	1798	our $CHLD_W;
1062	our $CHLD_DELAY_W;	1799	our $CHLD_DELAY_W;
1063	our $PID_IDLE;
1064	our $WNOHANG;
1065		1800
1066	sub _child_wait {	1801	# used by many Impl's
1067	while (0 < (my $pid = waitpid -1, $WNOHANG)) {	1802	sub _emit_childstatus($$) {
		1803	my (undef, $rpid, $rstatus) = @_;
		1804
		1805	$_->($rpid, $rstatus)
1068	$_->($pid, $?) for (values %{ $PID_CB{$pid} || {} }),	1806	for values %{ $PID_CB{$rpid} || {} },
1069	(values %{ $PID_CB{0} || {} });	1807	values %{ $PID_CB{0} || {} };
1070	}
1071
1072	undef $PID_IDLE;
1073	}
1074
1075	sub _sigchld {
1076	# make sure we deliver these changes "synchronous" with the event loop.
1077	$CHLD_DELAY_W ||= AnyEvent->timer (after => 0, cb => sub {
1078	undef $CHLD_DELAY_W;
1079	&_child_wait;
1080	});
1081	}	1808	}
1082		1809
1083	sub child {	1810	sub child {
		1811	eval q{ # poor man's autoloading {}
		1812	*_sigchld = sub {
		1813	my $pid;
		1814
		1815	AnyEvent->_emit_childstatus ($pid, $?)
		1816	while ($pid = waitpid -1, WNOHANG) > 0;
		1817	};
		1818
		1819	*child = sub {
1084	my (undef, %arg) = @_;	1820	my (undef, %arg) = @_;
1085		1821
1086	defined (my $pid = $arg{pid} + 0)	1822	my $pid = $arg{pid};
1087	or Carp::croak "required option 'pid' is missing";	1823	my $cb = $arg{cb};
1088		1824
1089	$PID_CB{$pid}{$arg{cb}} = $arg{cb};	1825	$PID_CB{$pid}{$cb+0} = $cb;
1090		1826
1091	unless ($WNOHANG) {
1092	$WNOHANG = eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } || 1;
1093	}
1094
1095	unless ($CHLD_W) {	1827	unless ($CHLD_W) {
1096	$CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);	1828	$CHLD_W = AE::signal CHLD => \&_sigchld;
1097	# child could be a zombie already, so make at least one round	1829	# child could be a zombie already, so make at least one round
1098	&_sigchld;	1830	&_sigchld;
1099	}	1831	}
1100		1832
1101	bless [$pid, $arg{cb}], "AnyEvent::Base::Child"	1833	bless [$pid, $cb+0], "AnyEvent::Base::child"
1102	}	1834	};
1103		1835
1104	sub AnyEvent::Base::Child::DESTROY {	1836	*AnyEvent::Base::child::DESTROY = sub {
1105	my ($pid, $cb) = @{$_[0]};	1837	my ($pid, $icb) = @{$_[0]};
1106		1838
1107	delete $PID_CB{$pid}{$cb};	1839	delete $PID_CB{$pid}{$icb};
1108	delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };	1840	delete $PID_CB{$pid} unless keys %{ $PID_CB{$pid} };
1109		1841
1110	undef $CHLD_W unless keys %PID_CB;	1842	undef $CHLD_W unless keys %PID_CB;
		1843	};
		1844	};
		1845	die if $@;
		1846
		1847	&child
		1848	}
		1849
		1850	# idle emulation is done by simply using a timer, regardless
		1851	# of whether the process is idle or not, and not letting
		1852	# the callback use more than 50% of the time.
		1853	sub idle {
		1854	eval q{ # poor man's autoloading {}
		1855	*idle = sub {
		1856	my (undef, %arg) = @_;
		1857
		1858	my ($cb, $w, $rcb) = $arg{cb};
		1859
		1860	$rcb = sub {
		1861	if ($cb) {
		1862	$w = AE::time;
		1863	&$cb;
		1864	$w = AE::time - $w;
		1865
		1866	# never use more then 50% of the time for the idle watcher,
		1867	# within some limits
		1868	$w = 0.0001 if $w < 0.0001;
		1869	$w = 5 if $w > 5;
		1870
		1871	$w = AE::timer $w, 0, $rcb;
		1872	} else {
		1873	# clean up...
		1874	undef $w;
		1875	undef $rcb;
		1876	}
		1877	};
		1878
		1879	$w = AE::timer 0.05, 0, $rcb;
		1880
		1881	bless \\$cb, "AnyEvent::Base::idle"
		1882	};
		1883
		1884	*AnyEvent::Base::idle::DESTROY = sub {
		1885	undef $${$_[0]};
		1886	};
		1887	};
		1888	die if $@;
		1889
		1890	&idle
1111	}	1891	}
1112		1892
1113	package AnyEvent::CondVar;	1893	package AnyEvent::CondVar;
1114		1894
1115	our @ISA = AnyEvent::CondVar::Base::;	1895	our @ISA = AnyEvent::CondVar::Base::;
1116		1896
		1897	# only to be used for subclassing
		1898	sub new {
		1899	my $class = shift;
		1900	bless AnyEvent->condvar (@_), $class
		1901	}
		1902
1117	package AnyEvent::CondVar::Base;	1903	package AnyEvent::CondVar::Base;
1118		1904
1119	use overload	1905	#use overload
1120	'&{}' => sub { my $self = shift; sub { $self->send (@_) } },	1906	# '&{}' => sub { my $self = shift; sub { $self->send (@_) } },
1121	fallback => 1;	1907	# fallback => 1;
		1908
		1909	# save 300+ kilobytes by dirtily hardcoding overloading
		1910	${"AnyEvent::CondVar::Base::OVERLOAD"}{dummy}++; # Register with magic by touching.
		1911	*{'AnyEvent::CondVar::Base::()'} = sub { }; # "Make it findable via fetchmethod."
		1912	*{'AnyEvent::CondVar::Base::(&{}'} = sub { my $self = shift; sub { $self->send (@_) } }; # &{}
		1913	${'AnyEvent::CondVar::Base::()'} = 1; # fallback
		1914
		1915	our $WAITING;
1122		1916
1123	sub _send {	1917	sub _send {
1124	# nop	1918	# nop
		1919	}
		1920
		1921	sub _wait {
		1922	AnyEvent->_poll until $_[0]{_ae_sent};
1125	}	1923	}
1126		1924
1127	sub send {	1925	sub send {
1128	my $cv = shift;	1926	my $cv = shift;
1129	$cv->{_ae_sent} = [@_];	1927	$cv->{_ae_sent} = [@_];
…		…
1138		1936
1139	sub ready {	1937	sub ready {
1140	$_[0]{_ae_sent}	1938	$_[0]{_ae_sent}
1141	}	1939	}
1142		1940
1143	sub _wait {
1144	AnyEvent->one_event while !$_[0]{_ae_sent};
1145	}
1146
1147	sub recv {	1941	sub recv {
		1942	unless ($_[0]{_ae_sent}) {
		1943	$WAITING
		1944	and Carp::croak "AnyEvent::CondVar: recursive blocking wait attempted";
		1945
		1946	local $WAITING = 1;
1148	$_[0]->_wait;	1947	$_[0]->_wait;
		1948	}
1149		1949
1150	Carp::croak $_[0]{_ae_croak} if $_[0]{_ae_croak};	1950	$_[0]{_ae_croak}
1151	wantarray ? @{ $_[0]{_ae_sent} } : $_[0]{_ae_sent}[0]	1951	and Carp::croak $_[0]{_ae_croak};
		1952
		1953	wantarray
		1954	? @{ $_[0]{_ae_sent} }
		1955	: $_[0]{_ae_sent}[0]
1152	}	1956	}
1153		1957
1154	sub cb {	1958	sub cb {
1155	$_[0]{_ae_cb} = $_[1] if @_ > 1;	1959	my $cv = shift;
		1960
		1961	@_
		1962	and $cv->{_ae_cb} = shift
		1963	and $cv->{_ae_sent}
		1964	and (delete $cv->{_ae_cb})->($cv);
		1965
1156	$_[0]{_ae_cb}	1966	$cv->{_ae_cb}
1157	}	1967	}
1158		1968
1159	sub begin {	1969	sub begin {
1160	++$_[0]{_ae_counter};	1970	++$_[0]{_ae_counter};
1161	$_[0]{_ae_end_cb} = $_[1] if @_ > 1;	1971	$_[0]{_ae_end_cb} = $_[1] if @_ > 1;
…		…
1166	&{ $_[0]{_ae_end_cb} || sub { $_[0]->send } };	1976	&{ $_[0]{_ae_end_cb} || sub { $_[0]->send } };
1167	}	1977	}
1168		1978
1169	# undocumented/compatibility with pre-3.4	1979	# undocumented/compatibility with pre-3.4
1170	*broadcast = \&send;	1980	*broadcast = \&send;
1171	*wait = \&_wait;	1981	*wait = \&recv;
		1982
		1983	=head1 ERROR AND EXCEPTION HANDLING
		1984
		1985	In general, AnyEvent does not do any error handling - it relies on the
		1986	caller to do that if required. The L<AnyEvent::Strict> module (see also
		1987	the C<PERL_ANYEVENT_STRICT> environment variable, below) provides strict
		1988	checking of all AnyEvent methods, however, which is highly useful during
		1989	development.
		1990
		1991	As for exception handling (i.e. runtime errors and exceptions thrown while
		1992	executing a callback), this is not only highly event-loop specific, but
		1993	also not in any way wrapped by this module, as this is the job of the main
		1994	program.
		1995
		1996	The pure perl event loop simply re-throws the exception (usually
		1997	within C<< condvar->recv >>), the L<Event> and L<EV> modules call C<<
		1998	$Event/EV::DIED->() >>, L<Glib> uses C<< install_exception_handler >> and
		1999	so on.
		2000
		2001	=head1 ENVIRONMENT VARIABLES
		2002
		2003	AnyEvent supports a number of environment variables that tune the
		2004	runtime behaviour. They are usually evaluated when AnyEvent is
		2005	loaded, initialised, or a submodule that uses them is loaded. Many of
		2006	them also cause AnyEvent to load additional modules - for example,
		2007	C<PERL_ANYEVENT_DEBUG_WRAP> causes the L<AnyEvent::Debug> module to be
		2008	loaded.
		2009
		2010	All the environment variables documented here start with
		2011	C<PERL_ANYEVENT_>, which is what AnyEvent considers its own
		2012	namespace. Other modules are encouraged (but by no means required) to use
		2013	C<PERL_ANYEVENT_SUBMODULE> if they have registered the AnyEvent::Submodule
		2014	namespace on CPAN, for any submodule. For example, L<AnyEvent::HTTP> could
		2015	be expected to use C<PERL_ANYEVENT_HTTP_PROXY> (it should not access env
		2016	variables starting with C<AE_>, see below).
		2017
		2018	All variables can also be set via the C<AE_> prefix, that is, instead
		2019	of setting C<PERL_ANYEVENT_VERBOSE> you can also set C<AE_VERBOSE>. In
		2020	case there is a clash btween anyevent and another program that uses
		2021	C<AE_something> you can set the corresponding C<PERL_ANYEVENT_something>
		2022	variable to the empty string, as those variables take precedence.
		2023
		2024	When AnyEvent is first loaded, it copies all C<AE_xxx> env variables
		2025	to their C<PERL_ANYEVENT_xxx> counterpart unless that variable already
		2026	exists. If taint mode is on, then AnyEvent will remove I<all> environment
		2027	variables starting with C<PERL_ANYEVENT_> from C<%ENV> (or replace them
		2028	with C<undef> or the empty string, if the corresaponding C<AE_> variable
		2029	is set).
		2030
		2031	The exact algorithm is currently:
		2032
		2033	1. if taint mode enabled, delete all PERL_ANYEVENT_xyz variables from %ENV
		2034	2. copy over AE_xyz to PERL_ANYEVENT_xyz unless the latter alraedy exists
		2035	3. if taint mode enabled, set all PERL_ANYEVENT_xyz variables to undef.
		2036
		2037	This ensures that child processes will not see the C<AE_> variables.
		2038
		2039	The following environment variables are currently known to AnyEvent:
		2040
		2041	=over 4
		2042
		2043	=item C<PERL_ANYEVENT_VERBOSE>
		2044
		2045	By default, AnyEvent will be completely silent except in fatal
		2046	conditions. You can set this environment variable to make AnyEvent more
		2047	talkative. If you want to do more than just set the global logging level
		2048	you should have a look at C<PERL_ANYEVENT_LOG>, which allows much more
		2049	complex specifications.
		2050
		2051	When set to C<5> or higher (warn), causes AnyEvent to warn about unexpected
		2052	conditions, such as not being able to load the event model specified by
		2053	C<PERL_ANYEVENT_MODEL>, or a guard callback throwing an exception - this
		2054	is the minimum recommended level.
		2055
		2056	When set to C<7> or higher (info), cause AnyEvent to report which event model it
		2057	chooses.
		2058
		2059	When set to C<8> or higher (debug), then AnyEvent will report extra information on
		2060	which optional modules it loads and how it implements certain features.
		2061
		2062	=item C<PERL_ANYEVENT_LOG>
		2063
		2064	Accepts rather complex logging specifications. For example, you could log
		2065	all C<debug> messages of some module to stderr, warnings and above to
		2066	stderr, and errors and above to syslog, with:
		2067
		2068	PERL_ANYEVENT_LOG=Some::Module=debug,+log:filter=warn,+%syslog:%syslog=error,syslog
		2069
		2070	For the rather extensive details, see L<AnyEvent::Log>.
		2071
		2072	This variable is evaluated when AnyEvent (or L<AnyEvent::Log>) is loaded,
		2073	so will take effect even before AnyEvent has initialised itself.
		2074
		2075	Note that specifying this environment variable causes the L<AnyEvent::Log>
		2076	module to be loaded, while C<PERL_ANYEVENT_VERBOSE> does not, so only
		2077	using the latter saves a few hundred kB of memory until the first message
		2078	is being logged.
		2079
		2080	=item C<PERL_ANYEVENT_STRICT>
		2081
		2082	AnyEvent does not do much argument checking by default, as thorough
		2083	argument checking is very costly. Setting this variable to a true value
		2084	will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
		2085	check the arguments passed to most method calls. If it finds any problems,
		2086	it will croak.
		2087
		2088	In other words, enables "strict" mode.
		2089
		2090	Unlike C<use strict> (or its modern cousin, C<< use L<common::sense>
		2091	>>, it is definitely recommended to keep it off in production. Keeping
		2092	C<PERL_ANYEVENT_STRICT=1> in your environment while developing programs
		2093	can be very useful, however.
		2094
		2095	=item C<PERL_ANYEVENT_DEBUG_SHELL>
		2096
		2097	If this env variable is set, then its contents will be interpreted by
		2098	C<AnyEvent::Socket::parse_hostport> (after replacing every occurance of
		2099	C<$$> by the process pid) and an C<AnyEvent::Debug::shell> is bound on
		2100	that port. The shell object is saved in C<$AnyEvent::Debug::SHELL>.
		2101
		2102	This happens when the first watcher is created.
		2103
		2104	For example, to bind a debug shell on a unix domain socket in
		2105	F<< /tmp/debug<pid>.sock >>, you could use this:
		2106
		2107	PERL_ANYEVENT_DEBUG_SHELL=/tmp/debug\$\$.sock perlprog
		2108
		2109	Note that creating sockets in F</tmp> is very unsafe on multiuser
		2110	systems.
		2111
		2112	=item C<PERL_ANYEVENT_DEBUG_WRAP>
		2113
		2114	Can be set to C<0>, C<1> or C<2> and enables wrapping of all watchers for
		2115	debugging purposes. See C<AnyEvent::Debug::wrap> for details.
		2116
		2117	=item C<PERL_ANYEVENT_MODEL>
		2118
		2119	This can be used to specify the event model to be used by AnyEvent, before
		2120	auto detection and -probing kicks in.
		2121
		2122	It normally is a string consisting entirely of ASCII letters (e.g. C<EV>
		2123	or C<IOAsync>). The string C<AnyEvent::Impl::> gets prepended and the
		2124	resulting module name is loaded and - if the load was successful - used as
		2125	event model backend. If it fails to load then AnyEvent will proceed with
		2126	auto detection and -probing.
		2127
		2128	If the string ends with C<::> instead (e.g. C<AnyEvent::Impl::EV::>) then
		2129	nothing gets prepended and the module name is used as-is (hint: C<::> at
		2130	the end of a string designates a module name and quotes it appropriately).
		2131
		2132	For example, to force the pure perl model (L<AnyEvent::Loop::Perl>) you
		2133	could start your program like this:
		2134
		2135	PERL_ANYEVENT_MODEL=Perl perl ...
		2136
		2137	=item C<PERL_ANYEVENT_PROTOCOLS>
		2138
		2139	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
		2140	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
		2141	of auto probing).
		2142
		2143	Must be set to a comma-separated list of protocols or address families,
		2144	current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
		2145	used, and preference will be given to protocols mentioned earlier in the
		2146	list.
		2147
		2148	This variable can effectively be used for denial-of-service attacks
		2149	against local programs (e.g. when setuid), although the impact is likely
		2150	small, as the program has to handle conenction and other failures anyways.
		2151
		2152	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
		2153	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
		2154	- only support IPv4, never try to resolve or contact IPv6
		2155	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
		2156	IPv6, but prefer IPv6 over IPv4.
		2157
		2158	=item C<PERL_ANYEVENT_HOSTS>
		2159
		2160	This variable, if specified, overrides the F</etc/hosts> file used by
		2161	L<AnyEvent::Socket>C<::resolve_sockaddr>, i.e. hosts aliases will be read
		2162	from that file instead.
		2163
		2164	=item C<PERL_ANYEVENT_EDNS0>
		2165
		2166	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension for
		2167	DNS. This extension is generally useful to reduce DNS traffic, especially
		2168	when DNSSEC is involved, but some (broken) firewalls drop such DNS
		2169	packets, which is why it is off by default.
		2170
		2171	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
		2172	EDNS0 in its DNS requests.
		2173
		2174	=item C<PERL_ANYEVENT_MAX_FORKS>
		2175
		2176	The maximum number of child processes that C<AnyEvent::Util::fork_call>
		2177	will create in parallel.
		2178
		2179	=item C<PERL_ANYEVENT_MAX_OUTSTANDING_DNS>
		2180
		2181	The default value for the C<max_outstanding> parameter for the default DNS
		2182	resolver - this is the maximum number of parallel DNS requests that are
		2183	sent to the DNS server.
		2184
		2185	=item C<PERL_ANYEVENT_RESOLV_CONF>
		2186
		2187	The absolute path to a F<resolv.conf>-style file to use instead of
		2188	F</etc/resolv.conf> (or the OS-specific configuration) in the default
		2189	resolver, or the empty string to select the default configuration.
		2190
		2191	=item C<PERL_ANYEVENT_CA_FILE>, C<PERL_ANYEVENT_CA_PATH>.
		2192
		2193	When neither C<ca_file> nor C<ca_path> was specified during
		2194	L<AnyEvent::TLS> context creation, and either of these environment
		2195	variables are nonempty, they will be used to specify CA certificate
		2196	locations instead of a system-dependent default.
		2197
		2198	=item C<PERL_ANYEVENT_AVOID_GUARD> and C<PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT>
		2199
		2200	When these are set to C<1>, then the respective modules are not
		2201	loaded. Mostly good for testing AnyEvent itself.
		2202
		2203	=back
1172		2204
1173	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE	2205	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
1174		2206
1175	This is an advanced topic that you do not normally need to use AnyEvent in	2207	This is an advanced topic that you do not normally need to use AnyEvent in
1176	a module. This section is only of use to event loop authors who want to	2208	a module. This section is only of use to event loop authors who want to
…		…
1210		2242
1211	I<rxvt-unicode> also cheats a bit by not providing blocking access to	2243	I<rxvt-unicode> also cheats a bit by not providing blocking access to
1212	condition variables: code blocking while waiting for a condition will	2244	condition variables: code blocking while waiting for a condition will
1213	C<die>. This still works with most modules/usages, and blocking calls must	2245	C<die>. This still works with most modules/usages, and blocking calls must
1214	not be done in an interactive application, so it makes sense.	2246	not be done in an interactive application, so it makes sense.
1215
1216	=head1 ENVIRONMENT VARIABLES
1217
1218	The following environment variables are used by this module:
1219
1220	=over 4
1221
1222	=item C<PERL_ANYEVENT_VERBOSE>
1223
1224	By default, AnyEvent will be completely silent except in fatal
1225	conditions. You can set this environment variable to make AnyEvent more
1226	talkative.
1227
1228	When set to C<1> or higher, causes AnyEvent to warn about unexpected
1229	conditions, such as not being able to load the event model specified by
1230	C<PERL_ANYEVENT_MODEL>.
1231
1232	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1233	model it chooses.
1234
1235	=item C<PERL_ANYEVENT_STRICT>
1236
1237	AnyEvent does not do much argument checking by default, as thorough
1238	argument checking is very costly. Setting this variable to a true value
1239	will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
1240	check the arguments passed to most method calls. If it finds any problems
1241	it will croak.
1242
1243	In other words, enables "strict" mode.
1244
1245	Unlike C<use strict> it is definitely recommended ot keep it off in
1246	production.
1247
1248	=item C<PERL_ANYEVENT_MODEL>
1249
1250	This can be used to specify the event model to be used by AnyEvent, before
1251	auto detection and -probing kicks in. It must be a string consisting
1252	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
1253	and the resulting module name is loaded and if the load was successful,
1254	used as event model. If it fails to load AnyEvent will proceed with
1255	auto detection and -probing.
1256
1257	This functionality might change in future versions.
1258
1259	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1260	could start your program like this:
1261
1262	PERL_ANYEVENT_MODEL=Perl perl ...
1263
1264	=item C<PERL_ANYEVENT_PROTOCOLS>
1265
1266	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1267	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
1268	of auto probing).
1269
1270	Must be set to a comma-separated list of protocols or address families,
1271	current supported: C<ipv4> and C<ipv6>. Only protocols mentioned will be
1272	used, and preference will be given to protocols mentioned earlier in the
1273	list.
1274
1275	This variable can effectively be used for denial-of-service attacks
1276	against local programs (e.g. when setuid), although the impact is likely
1277	small, as the program has to handle connection errors already-
1278
1279	Examples: C<PERL_ANYEVENT_PROTOCOLS=ipv4,ipv6> - prefer IPv4 over IPv6,
1280	but support both and try to use both. C<PERL_ANYEVENT_PROTOCOLS=ipv4>
1281	- only support IPv4, never try to resolve or contact IPv6
1282	addresses. C<PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4> support either IPv4 or
1283	IPv6, but prefer IPv6 over IPv4.
1284
1285	=item C<PERL_ANYEVENT_EDNS0>
1286
1287	Used by L<AnyEvent::DNS> to decide whether to use the EDNS0 extension
1288	for DNS. This extension is generally useful to reduce DNS traffic, but
1289	some (broken) firewalls drop such DNS packets, which is why it is off by
1290	default.
1291
1292	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1293	EDNS0 in its DNS requests.
1294
1295	=item C<PERL_ANYEVENT_MAX_FORKS>
1296
1297	The maximum number of child processes that C<AnyEvent::Util::fork_call>
1298	will create in parallel.
1299
1300	=back
1301		2247
1302	=head1 EXAMPLE PROGRAM	2248	=head1 EXAMPLE PROGRAM
1303		2249
1304	The following program uses an I/O watcher to read data from STDIN, a timer	2250	The following program uses an I/O watcher to read data from STDIN, a timer
1305	to display a message once per second, and a condition variable to quit the	2251	to display a message once per second, and a condition variable to quit the
…		…
1318	warn "read: $input\n"; # output what has been read	2264	warn "read: $input\n"; # output what has been read
1319	$cv->send if $input =~ /^q/i; # quit program if /^q/i	2265	$cv->send if $input =~ /^q/i; # quit program if /^q/i
1320	},	2266	},
1321	);	2267	);
1322		2268
1323	my $time_watcher; # can only be used once
1324
1325	sub new_timer {
1326	$timer = AnyEvent->timer (after => 1, cb => sub {	2269	my $time_watcher = AnyEvent->timer (after => 1, interval => 1, cb => sub {
1327	warn "timeout\n"; # print 'timeout' about every second	2270	warn "timeout\n"; # print 'timeout' at most every second
1328	&new_timer; # and restart the time
1329	});	2271	});
1330	}
1331
1332	new_timer; # create first timer
1333		2272
1334	$cv->recv; # wait until user enters /^q/i	2273	$cv->recv; # wait until user enters /^q/i
1335		2274
1336	=head1 REAL-WORLD EXAMPLE	2275	=head1 REAL-WORLD EXAMPLE
1337		2276
…		…
1410		2349
1411	The actual code goes further and collects all errors (C<die>s, exceptions)	2350	The actual code goes further and collects all errors (C<die>s, exceptions)
1412	that occurred during request processing. The C<result> method detects	2351	that occurred during request processing. The C<result> method detects
1413	whether an exception as thrown (it is stored inside the $txn object)	2352	whether an exception as thrown (it is stored inside the $txn object)
1414	and just throws the exception, which means connection errors and other	2353	and just throws the exception, which means connection errors and other
1415	problems get reported tot he code that tries to use the result, not in a	2354	problems get reported to the code that tries to use the result, not in a
1416	random callback.	2355	random callback.
1417		2356
1418	All of this enables the following usage styles:	2357	All of this enables the following usage styles:
1419		2358
1420	1. Blocking:	2359	1. Blocking:
…		…
1468	through AnyEvent. The benchmark creates a lot of timers (with a zero	2407	through AnyEvent. The benchmark creates a lot of timers (with a zero
1469	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,	2408	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,
1470	which it is), lets them fire exactly once and destroys them again.	2409	which it is), lets them fire exactly once and destroys them again.
1471		2410
1472	Source code for this benchmark is found as F<eg/bench> in the AnyEvent	2411	Source code for this benchmark is found as F<eg/bench> in the AnyEvent
1473	distribution.	2412	distribution. It uses the L<AE> interface, which makes a real difference
		2413	for the EV and Perl backends only.
1474		2414
1475	=head3 Explanation of the columns	2415	=head3 Explanation of the columns
1476		2416
1477	I<watcher> is the number of event watchers created/destroyed. Since	2417	I<watcher> is the number of event watchers created/destroyed. Since
1478	different event models feature vastly different performances, each event	2418	different event models feature vastly different performances, each event
…		…
1499	watcher.	2439	watcher.
1500		2440
1501	=head3 Results	2441	=head3 Results
1502		2442
1503	name watchers bytes create invoke destroy comment	2443	name watchers bytes create invoke destroy comment
1504	EV/EV 400000 244 0.56 0.46 0.31 EV native interface	2444	EV/EV 100000 223 0.47 0.43 0.27 EV native interface
1505	EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers	2445	EV/Any 100000 223 0.48 0.42 0.26 EV + AnyEvent watchers
1506	CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal	2446	Coro::EV/Any 100000 223 0.47 0.42 0.26 coroutines + Coro::Signal
1507	Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation	2447	Perl/Any 100000 431 2.70 0.74 0.92 pure perl implementation
1508	Event/Event 16000 516 31.88 31.30 0.85 Event native interface	2448	Event/Event 16000 516 31.16 31.84 0.82 Event native interface
1509	Event/Any 16000 590 35.75 31.42 1.08 Event + AnyEvent watchers	2449	Event/Any 16000 1203 42.61 34.79 1.80 Event + AnyEvent watchers
		2450	IOAsync/Any 16000 1911 41.92 27.45 16.81 via IO::Async::Loop::IO_Poll
		2451	IOAsync/Any 16000 1726 40.69 26.37 15.25 via IO::Async::Loop::Epoll
1510	Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour	2452	Glib/Any 16000 1118 89.00 12.57 51.17 quadratic behaviour
1511	Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers	2453	Tk/Any 2000 1346 20.96 10.75 8.00 SEGV with >> 2000 watchers
1512	POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event	2454	POE/Any 2000 6951 108.97 795.32 14.24 via POE::Loop::Event
1513	POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select	2455	POE/Any 2000 6648 94.79 774.40 575.51 via POE::Loop::Select
1514		2456
1515	=head3 Discussion	2457	=head3 Discussion
1516		2458
1517	The benchmark does I<not> measure scalability of the event loop very	2459	The benchmark does I<not> measure scalability of the event loop very
1518	well. For example, a select-based event loop (such as the pure perl one)	2460	well. For example, a select-based event loop (such as the pure perl one)
…		…
1530	benchmark machine, handling an event takes roughly 1600 CPU cycles with	2472	benchmark machine, handling an event takes roughly 1600 CPU cycles with
1531	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU	2473	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU
1532	cycles with POE.	2474	cycles with POE.
1533		2475
1534	C<EV> is the sole leader regarding speed and memory use, which are both	2476	C<EV> is the sole leader regarding speed and memory use, which are both
1535	maximal/minimal, respectively. Even when going through AnyEvent, it uses	2477	maximal/minimal, respectively. When using the L<AE> API there is zero
		2478	overhead (when going through the AnyEvent API create is about 5-6 times
		2479	slower, with other times being equal, so still uses far less memory than
1536	far less memory than any other event loop and is still faster than Event	2480	any other event loop and is still faster than Event natively).
1537	natively.
1538		2481
1539	The pure perl implementation is hit in a few sweet spots (both the	2482	The pure perl implementation is hit in a few sweet spots (both the
1540	constant timeout and the use of a single fd hit optimisations in the perl	2483	constant timeout and the use of a single fd hit optimisations in the perl
1541	interpreter and the backend itself). Nevertheless this shows that it	2484	interpreter and the backend itself). Nevertheless this shows that it
1542	adds very little overhead in itself. Like any select-based backend its	2485	adds very little overhead in itself. Like any select-based backend its
1543	performance becomes really bad with lots of file descriptors (and few of	2486	performance becomes really bad with lots of file descriptors (and few of
1544	them active), of course, but this was not subject of this benchmark.	2487	them active), of course, but this was not subject of this benchmark.
1545		2488
1546	The C<Event> module has a relatively high setup and callback invocation	2489	The C<Event> module has a relatively high setup and callback invocation
1547	cost, but overall scores in on the third place.	2490	cost, but overall scores in on the third place.
		2491
		2492	C<IO::Async> performs admirably well, about on par with C<Event>, even
		2493	when using its pure perl backend.
1548		2494
1549	C<Glib>'s memory usage is quite a bit higher, but it features a	2495	C<Glib>'s memory usage is quite a bit higher, but it features a
1550	faster callback invocation and overall ends up in the same class as	2496	faster callback invocation and overall ends up in the same class as
1551	C<Event>. However, Glib scales extremely badly, doubling the number of	2497	C<Event>. However, Glib scales extremely badly, doubling the number of
1552	watchers increases the processing time by more than a factor of four,	2498	watchers increases the processing time by more than a factor of four,
…		…
1587	(even when used without AnyEvent), but most event loops have acceptable	2533	(even when used without AnyEvent), but most event loops have acceptable
1588	performance with or without AnyEvent.	2534	performance with or without AnyEvent.
1589		2535
1590	=item * The overhead AnyEvent adds is usually much smaller than the overhead of	2536	=item * The overhead AnyEvent adds is usually much smaller than the overhead of
1591	the actual event loop, only with extremely fast event loops such as EV	2537	the actual event loop, only with extremely fast event loops such as EV
1592	adds AnyEvent significant overhead.	2538	does AnyEvent add significant overhead.
1593		2539
1594	=item * You should avoid POE like the plague if you want performance or	2540	=item * You should avoid POE like the plague if you want performance or
1595	reasonable memory usage.	2541	reasonable memory usage.
1596		2542
1597	=back	2543	=back
…		…
1613	In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100	2559	In this benchmark, we use 10000 socket pairs (20000 sockets), of which 100
1614	(1%) are active. This mirrors the activity of large servers with many	2560	(1%) are active. This mirrors the activity of large servers with many
1615	connections, most of which are idle at any one point in time.	2561	connections, most of which are idle at any one point in time.
1616		2562
1617	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent	2563	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent
1618	distribution.	2564	distribution. It uses the L<AE> interface, which makes a real difference
		2565	for the EV and Perl backends only.
1619		2566
1620	=head3 Explanation of the columns	2567	=head3 Explanation of the columns
1621		2568
1622	I<sockets> is the number of sockets, and twice the number of "servers" (as	2569	I<sockets> is the number of sockets, and twice the number of "servers" (as
1623	each server has a read and write socket end).	2570	each server has a read and write socket end).
…		…
1630	it to another server. This includes deleting the old timeout and creating	2577	it to another server. This includes deleting the old timeout and creating
1631	a new one that moves the timeout into the future.	2578	a new one that moves the timeout into the future.
1632		2579
1633	=head3 Results	2580	=head3 Results
1634		2581
1635	name sockets create request	2582	name sockets create request
1636	EV 20000 69.01 11.16	2583	EV 20000 62.66 7.99
1637	Perl 20000 73.32 35.87	2584	Perl 20000 68.32 32.64
1638	Event 20000 212.62 257.32	2585	IOAsync 20000 174.06 101.15 epoll
1639	Glib 20000 651.16 1896.30	2586	IOAsync 20000 174.67 610.84 poll
		2587	Event 20000 202.69 242.91
		2588	Glib 20000 557.01 1689.52
1640	POE 20000 349.67 12317.24 uses POE::Loop::Event	2589	POE 20000 341.54 12086.32 uses POE::Loop::Event
1641		2590
1642	=head3 Discussion	2591	=head3 Discussion
1643		2592
1644	This benchmark I<does> measure scalability and overall performance of the	2593	This benchmark I<does> measure scalability and overall performance of the
1645	particular event loop.	2594	particular event loop.
…		…
1647	EV is again fastest. Since it is using epoll on my system, the setup time	2596	EV is again fastest. Since it is using epoll on my system, the setup time
1648	is relatively high, though.	2597	is relatively high, though.
1649		2598
1650	Perl surprisingly comes second. It is much faster than the C-based event	2599	Perl surprisingly comes second. It is much faster than the C-based event
1651	loops Event and Glib.	2600	loops Event and Glib.
		2601
		2602	IO::Async performs very well when using its epoll backend, and still quite
		2603	good compared to Glib when using its pure perl backend.
1652		2604
1653	Event suffers from high setup time as well (look at its code and you will	2605	Event suffers from high setup time as well (look at its code and you will
1654	understand why). Callback invocation also has a high overhead compared to	2606	understand why). Callback invocation also has a high overhead compared to
1655	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event	2607	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event
1656	uses select or poll in basically all documented configurations.	2608	uses select or poll in basically all documented configurations.
…		…
1719	=item * C-based event loops perform very well with small number of	2671	=item * C-based event loops perform very well with small number of
1720	watchers, as the management overhead dominates.	2672	watchers, as the management overhead dominates.
1721		2673
1722	=back	2674	=back
1723		2675
		2676	=head2 THE IO::Lambda BENCHMARK
		2677
		2678	Recently I was told about the benchmark in the IO::Lambda manpage, which
		2679	could be misinterpreted to make AnyEvent look bad. In fact, the benchmark
		2680	simply compares IO::Lambda with POE, and IO::Lambda looks better (which
		2681	shouldn't come as a surprise to anybody). As such, the benchmark is
		2682	fine, and mostly shows that the AnyEvent backend from IO::Lambda isn't
		2683	very optimal. But how would AnyEvent compare when used without the extra
		2684	baggage? To explore this, I wrote the equivalent benchmark for AnyEvent.
		2685
		2686	The benchmark itself creates an echo-server, and then, for 500 times,
		2687	connects to the echo server, sends a line, waits for the reply, and then
		2688	creates the next connection. This is a rather bad benchmark, as it doesn't
		2689	test the efficiency of the framework or much non-blocking I/O, but it is a
		2690	benchmark nevertheless.
		2691
		2692	name runtime
		2693	Lambda/select 0.330 sec
		2694	+ optimized 0.122 sec
		2695	Lambda/AnyEvent 0.327 sec
		2696	+ optimized 0.138 sec
		2697	Raw sockets/select 0.077 sec
		2698	POE/select, components 0.662 sec
		2699	POE/select, raw sockets 0.226 sec
		2700	POE/select, optimized 0.404 sec
		2701
		2702	AnyEvent/select/nb 0.085 sec
		2703	AnyEvent/EV/nb 0.068 sec
		2704	+state machine 0.134 sec
		2705
		2706	The benchmark is also a bit unfair (my fault): the IO::Lambda/POE
		2707	benchmarks actually make blocking connects and use 100% blocking I/O,
		2708	defeating the purpose of an event-based solution. All of the newly
		2709	written AnyEvent benchmarks use 100% non-blocking connects (using
		2710	AnyEvent::Socket::tcp_connect and the asynchronous pure perl DNS
		2711	resolver), so AnyEvent is at a disadvantage here, as non-blocking connects
		2712	generally require a lot more bookkeeping and event handling than blocking
		2713	connects (which involve a single syscall only).
		2714
		2715	The last AnyEvent benchmark additionally uses L<AnyEvent::Handle>, which
		2716	offers similar expressive power as POE and IO::Lambda, using conventional
		2717	Perl syntax. This means that both the echo server and the client are 100%
		2718	non-blocking, further placing it at a disadvantage.
		2719
		2720	As you can see, the AnyEvent + EV combination even beats the
		2721	hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl
		2722	backend easily beats IO::Lambda and POE.
		2723
		2724	And even the 100% non-blocking version written using the high-level (and
		2725	slow :) L<AnyEvent::Handle> abstraction beats both POE and IO::Lambda
		2726	higher level ("unoptimised") abstractions by a large margin, even though
		2727	it does all of DNS, tcp-connect and socket I/O in a non-blocking way.
		2728
		2729	The two AnyEvent benchmarks programs can be found as F<eg/ae0.pl> and
		2730	F<eg/ae2.pl> in the AnyEvent distribution, the remaining benchmarks are
		2731	part of the IO::Lambda distribution and were used without any changes.
		2732
		2733
		2734	=head1 SIGNALS
		2735
		2736	AnyEvent currently installs handlers for these signals:
		2737
		2738	=over 4
		2739
		2740	=item SIGCHLD
		2741
		2742	A handler for C<SIGCHLD> is installed by AnyEvent's child watcher
		2743	emulation for event loops that do not support them natively. Also, some
		2744	event loops install a similar handler.
		2745
		2746	Additionally, when AnyEvent is loaded and SIGCHLD is set to IGNORE, then
		2747	AnyEvent will reset it to default, to avoid losing child exit statuses.
		2748
		2749	=item SIGPIPE
		2750
		2751	A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef>
		2752	when AnyEvent gets loaded.
		2753
		2754	The rationale for this is that AnyEvent users usually do not really depend
		2755	on SIGPIPE delivery (which is purely an optimisation for shell use, or
		2756	badly-written programs), but C<SIGPIPE> can cause spurious and rare
		2757	program exits as a lot of people do not expect C<SIGPIPE> when writing to
		2758	some random socket.
		2759
		2760	The rationale for installing a no-op handler as opposed to ignoring it is
		2761	that this way, the handler will be restored to defaults on exec.
		2762
		2763	Feel free to install your own handler, or reset it to defaults.
		2764
		2765	=back
		2766
		2767	=cut
		2768
		2769	undef $SIG{CHLD}
		2770	if $SIG{CHLD} eq 'IGNORE';
		2771
		2772	$SIG{PIPE} = sub { }
		2773	unless defined $SIG{PIPE};
		2774
		2775	=head1 RECOMMENDED/OPTIONAL MODULES
		2776
		2777	One of AnyEvent's main goals is to be 100% Pure-Perl(tm): only perl (and
		2778	its built-in modules) are required to use it.
		2779
		2780	That does not mean that AnyEvent won't take advantage of some additional
		2781	modules if they are installed.
		2782
		2783	This section explains which additional modules will be used, and how they
		2784	affect AnyEvent's operation.
		2785
		2786	=over 4
		2787
		2788	=item L<Async::Interrupt>
		2789
		2790	This slightly arcane module is used to implement fast signal handling: To
		2791	my knowledge, there is no way to do completely race-free and quick
		2792	signal handling in pure perl. To ensure that signals still get
		2793	delivered, AnyEvent will start an interval timer to wake up perl (and
		2794	catch the signals) with some delay (default is 10 seconds, look for
		2795	C<$AnyEvent::MAX_SIGNAL_LATENCY>).
		2796
		2797	If this module is available, then it will be used to implement signal
		2798	catching, which means that signals will not be delayed, and the event loop
		2799	will not be interrupted regularly, which is more efficient (and good for
		2800	battery life on laptops).
		2801
		2802	This affects not just the pure-perl event loop, but also other event loops
		2803	that have no signal handling on their own (e.g. Glib, Tk, Qt).
		2804
		2805	Some event loops (POE, Event, Event::Lib) offer signal watchers natively,
		2806	and either employ their own workarounds (POE) or use AnyEvent's workaround
		2807	(using C<$AnyEvent::MAX_SIGNAL_LATENCY>). Installing L<Async::Interrupt>
		2808	does nothing for those backends.
		2809
		2810	=item L<EV>
		2811
		2812	This module isn't really "optional", as it is simply one of the backend
		2813	event loops that AnyEvent can use. However, it is simply the best event
		2814	loop available in terms of features, speed and stability: It supports
		2815	the AnyEvent API optimally, implements all the watcher types in XS, does
		2816	automatic timer adjustments even when no monotonic clock is available,
		2817	can take avdantage of advanced kernel interfaces such as C<epoll> and
		2818	C<kqueue>, and is the fastest backend I<by far>. You can even embed
		2819	L<Glib>/L<Gtk2> in it (or vice versa, see L<EV::Glib> and L<Glib::EV>).
		2820
		2821	If you only use backends that rely on another event loop (e.g. C<Tk>),
		2822	then this module will do nothing for you.
		2823
		2824	=item L<Guard>
		2825
		2826	The guard module, when used, will be used to implement
		2827	C<AnyEvent::Util::guard>. This speeds up guards considerably (and uses a
		2828	lot less memory), but otherwise doesn't affect guard operation much. It is
		2829	purely used for performance.
		2830
		2831	=item L<JSON> and L<JSON::XS>
		2832
		2833	One of these modules is required when you want to read or write JSON data
		2834	via L<AnyEvent::Handle>. L<JSON> is also written in pure-perl, but can take
		2835	advantage of the ultra-high-speed L<JSON::XS> module when it is installed.
		2836
		2837	=item L<Net::SSLeay>
		2838
		2839	Implementing TLS/SSL in Perl is certainly interesting, but not very
		2840	worthwhile: If this module is installed, then L<AnyEvent::Handle> (with
		2841	the help of L<AnyEvent::TLS>), gains the ability to do TLS/SSL.
		2842
		2843	=item L<Time::HiRes>
		2844
		2845	This module is part of perl since release 5.008. It will be used when the
		2846	chosen event library does not come with a timing source of its own. The
		2847	pure-perl event loop (L<AnyEvent::Loop>) will additionally load it to
		2848	try to use a monotonic clock for timing stability.
		2849
		2850	=back
		2851
1724		2852
1725	=head1 FORK	2853	=head1 FORK
1726		2854
1727	Most event libraries are not fork-safe. The ones who are usually are	2855	Most event libraries are not fork-safe. The ones who are usually are
1728	because they rely on inefficient but fork-safe C<select> or C<poll>	2856	because they rely on inefficient but fork-safe C<select> or C<poll> calls
1729	calls. Only L<EV> is fully fork-aware.	2857	- higher performance APIs such as BSD's kqueue or the dreaded Linux epoll
		2858	are usually badly thought-out hacks that are incompatible with fork in
		2859	one way or another. Only L<EV> is fully fork-aware and ensures that you
		2860	continue event-processing in both parent and child (or both, if you know
		2861	what you are doing).
		2862
		2863	This means that, in general, you cannot fork and do event processing in
		2864	the child if the event library was initialised before the fork (which
		2865	usually happens when the first AnyEvent watcher is created, or the library
		2866	is loaded).
1730		2867
1731	If you have to fork, you must either do so I<before> creating your first	2868	If you have to fork, you must either do so I<before> creating your first
1732	watcher OR you must not use AnyEvent at all in the child.	2869	watcher OR you must not use AnyEvent at all in the child OR you must do
		2870	something completely out of the scope of AnyEvent.
		2871
		2872	The problem of doing event processing in the parent I<and> the child
		2873	is much more complicated: even for backends that I<are> fork-aware or
		2874	fork-safe, their behaviour is not usually what you want: fork clones all
		2875	watchers, that means all timers, I/O watchers etc. are active in both
		2876	parent and child, which is almost never what you want. USing C<exec>
		2877	to start worker children from some kind of manage rprocess is usually
		2878	preferred, because it is much easier and cleaner, at the expense of having
		2879	to have another binary.
1733		2880
1734		2881
1735	=head1 SECURITY CONSIDERATIONS	2882	=head1 SECURITY CONSIDERATIONS
1736		2883
1737	AnyEvent can be forced to load any event model via	2884	AnyEvent can be forced to load any event model via
…		…
1749	use AnyEvent;	2896	use AnyEvent;
1750		2897
1751	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can	2898	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1752	be used to probe what backend is used and gain other information (which is	2899	be used to probe what backend is used and gain other information (which is
1753	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and	2900	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
1754	$ENV{PERL_ANYEGENT_STRICT}.	2901	$ENV{PERL_ANYEVENT_STRICT}.
		2902
		2903	Note that AnyEvent will remove I<all> environment variables starting with
		2904	C<PERL_ANYEVENT_> from C<%ENV> when it is loaded while taint mode is
		2905	enabled.
1755		2906
1756		2907
1757	=head1 BUGS	2908	=head1 BUGS
1758		2909
1759	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard	2910	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
1760	to work around. If you suffer from memleaks, first upgrade to Perl 5.10	2911	to work around. If you suffer from memleaks, first upgrade to Perl 5.10
1761	and check wether the leaks still show up. (Perl 5.10.0 has other annoying	2912	and check wether the leaks still show up. (Perl 5.10.0 has other annoying
1762	mamleaks, such as leaking on C<map> and C<grep> but it is usually not as	2913	memleaks, such as leaking on C<map> and C<grep> but it is usually not as
1763	pronounced).	2914	pronounced).
1764		2915
1765		2916
1766	=head1 SEE ALSO	2917	=head1 SEE ALSO
1767		2918
1768	Utility functions: L<AnyEvent::Util>.	2919	Tutorial/Introduction: L<AnyEvent::Intro>.
1769		2920
1770	Event modules: L<EV>, L<EV::Glib>, L<Glib::EV>, L<Event>, L<Glib::Event>,	2921	FAQ: L<AnyEvent::FAQ>.
1771	L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>, L<POE>.	2922
		2923	Utility functions: L<AnyEvent::Util> (misc. grab-bag), L<AnyEvent::Log>
		2924	(simply logging).
		2925
		2926	Development/Debugging: L<AnyEvent::Strict> (stricter checking),
		2927	L<AnyEvent::Debug> (interactive shell, watcher tracing).
		2928
		2929	Supported event modules: L<AnyEvent::Loop>, L<EV>, L<EV::Glib>,
		2930	L<Glib::EV>, L<Event>, L<Glib::Event>, L<Glib>, L<Tk>, L<Event::Lib>,
		2931	L<Qt>, L<POE>, L<FLTK>.
1772		2932
1773	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,	2933	Implementations: L<AnyEvent::Impl::EV>, L<AnyEvent::Impl::Event>,
1774	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,	2934	L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>,
1775	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,	2935	L<AnyEvent::Impl::EventLib>, L<AnyEvent::Impl::Qt>,
		2936	L<AnyEvent::Impl::POE>, L<AnyEvent::Impl::IOAsync>, L<Anyevent::Impl::Irssi>,
1776	L<AnyEvent::Impl::POE>.	2937	L<AnyEvent::Impl::FLTK>.
1777		2938
1778	Non-blocking file handles, sockets, TCP clients and	2939	Non-blocking handles, pipes, stream sockets, TCP clients and
1779	servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>.	2940	servers: L<AnyEvent::Handle>, L<AnyEvent::Socket>, L<AnyEvent::TLS>.
1780		2941
1781	Asynchronous DNS: L<AnyEvent::DNS>.	2942	Asynchronous DNS: L<AnyEvent::DNS>.
1782		2943
1783	Coroutine support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>,	2944	Thread support: L<Coro>, L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>.
1784		2945
1785	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.	2946	Nontrivial usage examples: L<AnyEvent::GPSD>, L<AnyEvent::IRC>,
		2947	L<AnyEvent::HTTP>.
1786		2948
1787		2949
1788	=head1 AUTHOR	2950	=head1 AUTHOR
1789		2951
1790	Marc Lehmann <schmorp@schmorp.de>	2952	Marc Lehmann <schmorp@schmorp.de>

Diff Legend

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