ViewVC Help

View File | Revision Log | Show Annotations | Download File

/cvs/AnyEvent/lib/AnyEvent.pm

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

Diff Legend

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