[ViewVC] Diff of: cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.44 by root, Mon Apr 7 19:42:18 2008 UTC vs.
Revision 1.100 by elmex, Sun Apr 27 19:15:43 2008 UTC

…		…
1	=head1 NAME	1	=head1 NAME
2		2
3	AnyEvent - provide framework for multiple event loops	3	AnyEvent - provide framework for multiple event loops
4		4
5	Event, Coro, Glib, Tk, Perl - various supported event loops	5	EV, Event, Coro::EV, Coro::Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops
6		6
7	=head1 SYNOPSIS	7	=head1 SYNOPSIS
8		8
9	use AnyEvent;	9	use AnyEvent;
10		10
14		14
15	my $w = AnyEvent->timer (after => $seconds, cb => sub {	15	my $w = AnyEvent->timer (after => $seconds, cb => sub {
16	...	16	...
17	});	17	});
18		18
19	my $w = AnyEvent->condvar; # stores wether a condition was flagged	19	my $w = AnyEvent->condvar; # stores whether a condition was flagged
20	$w->wait; # enters "main loop" till $condvar gets ->broadcast	20	$w->wait; # enters "main loop" till $condvar gets ->broadcast
21	$w->broadcast; # wake up current and all future wait's	21	$w->broadcast; # wake up current and all future wait's
22		22
23	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)	23	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
24		24
…		…
29	policy> and AnyEvent is I<small and efficient>.	29	policy> and AnyEvent is I<small and efficient>.
30		30
31	First and foremost, I<AnyEvent is not an event model> itself, it only	31	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	32	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,	33	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	34	the statement "there can only be one" is a bitter reality: In general,
35	helps hiding the differences.	35	only one event loop can be active at the same time in a process. AnyEvent
		36	helps hiding the differences between those event loops.
36		37
37	The goal of AnyEvent is to offer module authors the ability to do event	38	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	39	programming (waiting for I/O or timer events) without subscribing to a
39	religion, a way of living, and most importantly: without forcing your	40	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	41	module users into the same thing by forcing them to use the same event
41	model you use.	42	model you use.
42		43
43	For modules like POE or IO::Async (which is actually doing all I/O	44	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	45	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	46	like joining a cult: After you joined, you are dependent on them and you
46	anything else, as it is simply incompatible to everything that isn't	47	cannot use anything else, as it is simply incompatible to everything that
47	itself.	48	isn't itself. What's worse, all the potential users of your module are
		49	I<also> forced to use the same event loop you use.
48		50
49	AnyEvent + POE works fine. AnyEvent + Glib works fine. AnyEvent + Tk	51	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	52	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	53	with the rest: POE + IO::Async? no go. Tk + Event? no go. Again: if
52	those, every user of your module has to use it, too. If your module	54	your module uses one of those, every user of your module has to use it,
53	uses AnyEvent, it works transparently with all event models it supports	55	too. But if your module uses AnyEvent, it works transparently with all
54	(including stuff like POE and IO::Async).	56	event models it supports (including stuff like POE and IO::Async, as long
		57	as those use one of the supported event loops. It is trivial to add new
		58	event loops to AnyEvent, too, so it is future-proof).
55		59
56	In addition of being free of having to use I<the one and only true event	60	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	61	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	62	modules, you get an enourmous 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	63	follow. AnyEvent, on the other hand, is lean and up to the point, by only
60	offering the functionality that is useful, in as thin as a wrapper as	64	offering the functionality that is necessary, in as thin as a wrapper as
61	technically possible.	65	technically possible.
62		66
63	Of course, if you want lots of policy (this is arguably somewhat useful	67	Of course, if you want lots of policy (this can arguably be somewhat
64	in many cases) and you want to force your users to the one and only event	68	useful) and you want to force your users to use the one and only event
65	model your module forces on them, you should I<not> use this module.	69	model, you should I<not> use this module.
66		70
		71	#TODO#
		72
		73	Net::IRC3
		74	AnyEvent::HTTPD
		75	AnyEvent::DNS
		76	IO::AnyEvent
		77	Net::FPing
		78	Net::XMPP2
		79	Coro
		80
		81	AnyEvent::IRC
		82	AnyEvent::HTTPD
		83	AnyEvent::DNS
		84	AnyEvent::Handle
		85	AnyEvent::Socket
		86	AnyEvent::FPing
		87	AnyEvent::XMPP
		88	AnyEvent::SNMP
		89	Coro
67		90
68	=head1 DESCRIPTION	91	=head1 DESCRIPTION
69		92
70	L<AnyEvent> provides an identical interface to multiple event loops. This	93	L<AnyEvent> provides an identical interface to multiple event loops. This
71	allows module authors to utilise an event loop without forcing module	94	allows module authors to utilise an event loop without forcing module
72	users to use the same event loop (as only a single event loop can coexist	95	users to use the same event loop (as only a single event loop can coexist
73	peacefully at any one time).	96	peacefully at any one time).
74		97
75	The interface itself is vaguely similar but not identical to the Event	98	The interface itself is vaguely similar, but not identical to the L<Event>
76	module.	99	module.
77		100
78	On the first call of any method, the module tries to detect the currently	101	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	102	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	103	following modules is already loaded: L<Coro::EV>, L<Coro::Event>, L<EV>,
81	used. If none is found, the module tries to load these modules in the	104	L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>,
82	order given. The first one that could be successfully loaded will be	105	L<POE>. The first one found is used. If none are found, the module tries
83	used. If still none could be found, AnyEvent will fall back to a pure-perl	106	to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl
84	event loop, which is also not very efficient.	107	adaptor should always succeed) in the order given. The first one that can
		108	be successfully loaded will be used. If, after this, still none could be
		109	found, AnyEvent will fall back to a pure-perl event loop, which is not
		110	very efficient, but should work everywhere.
85		111
86	Because AnyEvent first checks for modules that are already loaded, loading	112	Because AnyEvent first checks for modules that are already loaded, loading
87	an Event model explicitly before first using AnyEvent will likely make	113	an event model explicitly before first using AnyEvent will likely make
88	that model the default. For example:	114	that model the default. For example:
89		115
90	use Tk;	116	use Tk;
91	use AnyEvent;	117	use AnyEvent;
92		118
93	# .. AnyEvent will likely default to Tk	119	# .. AnyEvent will likely default to Tk
		120
		121	The I<likely> means that, if any module loads another event model and
		122	starts using it, all bets are off. Maybe you should tell their authors to
		123	use AnyEvent so their modules work together with others seamlessly...
94		124
95	The pure-perl implementation of AnyEvent is called	125	The pure-perl implementation of AnyEvent is called
96	C<AnyEvent::Impl::Perl>. Like other event modules you can load it	126	C<AnyEvent::Impl::Perl>. Like other event modules you can load it
97	explicitly.	127	explicitly.
98		128
…		…
101	AnyEvent has the central concept of a I<watcher>, which is an object that	131	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	132	stores relevant data for each kind of event you are waiting for, such as
103	the callback to call, the filehandle to watch, etc.	133	the callback to call, the filehandle to watch, etc.
104		134
105	These watchers are normal Perl objects with normal Perl lifetime. After	135	These watchers are normal Perl objects with normal Perl lifetime. After
106	creating a watcher it will immediately "watch" for events and invoke	136	creating a watcher it will immediately "watch" for events and invoke the
		137	callback when the event occurs (of course, only when the event model
		138	is in control).
		139
107	the callback. To disable the watcher you have to destroy it (e.g. by	140	To disable the 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	141	variable you store it in to C<undef> or otherwise deleting all references
109	references to it).	142	to it).
110		143
111	All watchers are created by calling a method on the C<AnyEvent> class.	144	All watchers are created by calling a method on the C<AnyEvent> class.
112		145
		146	Many watchers either are used with "recursion" (repeating timers for
		147	example), or need to refer to their watcher object in other ways.
		148
		149	An any way to achieve that is this pattern:
		150
		151	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
		152	# you can use $w here, for example to undef it
		153	undef $w;
		154	});
		155
		156	Note that C<my $w; $w => combination. This is necessary because in Perl,
		157	my variables are only visible after the statement in which they are
		158	declared.
		159
113	=head2 IO WATCHERS	160	=head2 I/O WATCHERS
114		161
115	You can create I/O watcher by calling the C<< AnyEvent->io >> method with	162	You can create an I/O watcher by calling the C<< AnyEvent->io >> method
116	the following mandatory arguments:	163	with the following mandatory key-value pairs as arguments:
117		164
118	C<fh> the Perl I<filehandle> (not filedescriptor) to watch for	165	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch
119	events. C<poll> must be a string that is either C<r> or C<w>, that creates	166	for events. C<poll> must be a string that is either C<r> or C<w>,
120	a watcher waiting for "r"eadable or "w"ritable events. C<cb> the callback	167	which creates a watcher waiting for "r"eadable or "w"ritable events,
121	to invoke everytime the filehandle becomes ready.	168	respectively. C<cb> is the callback to invoke each time the file handle
		169	becomes ready.
122		170
123	Only one io watcher per C<fh> and C<poll> combination is allowed (i.e. on	171	Although the callback might get passed parameters, their value and
124	a socket you can have one r + one w, not any more (limitation comes from	172	presence is undefined and you cannot rely on them. Portable AnyEvent
125	Tk - if you are sure you are not using Tk this limitation is gone).	173	callbacks cannot use arguments passed to I/O watcher callbacks.
126		174
127	Filehandles will be kept alive, so as long as the watcher exists, the	175	The I/O watcher might use the underlying file descriptor or a copy of it.
128	filehandle exists, too.	176	You must not close a file handle as long as any watcher is active on the
		177	underlying file descriptor.
		178
		179	Some event loops issue spurious readyness notifications, so you should
		180	always use non-blocking calls when reading/writing from/to your file
		181	handles.
129		182
130	Example:	183	Example:
131		184
132	# wait for readability of STDIN, then read a line and disable the watcher	185	# wait for readability of STDIN, then read a line and disable the watcher
133	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {	186	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
…		…
139	=head2 TIME WATCHERS	192	=head2 TIME WATCHERS
140		193
141	You can create a time watcher by calling the C<< AnyEvent->timer >>	194	You can create a time watcher by calling the C<< AnyEvent->timer >>
142	method with the following mandatory arguments:	195	method with the following mandatory arguments:
143		196
144	C<after> after how many seconds (fractions are supported) should the timer	197	C<after> specifies after how many seconds (fractional values are
145	activate. C<cb> the callback to invoke.	198	supported) the callback should be invoked. C<cb> is the callback to invoke
		199	in that case.
		200
		201	Although the callback might get passed parameters, their value and
		202	presence is undefined and you cannot rely on them. Portable AnyEvent
		203	callbacks cannot use arguments passed to time watcher callbacks.
146		204
147	The timer callback will be invoked at most once: if you want a repeating	205	The timer callback will be invoked at most once: if you want a repeating
148	timer you have to create a new watcher (this is a limitation by both Tk	206	timer you have to create a new watcher (this is a limitation by both Tk
149	and Glib).	207	and Glib).
150		208
…		…
156	});	214	});
157		215
158	# to cancel the timer:	216	# to cancel the timer:
159	undef $w;	217	undef $w;
160		218
		219	Example 2:
		220
		221	# fire an event after 0.5 seconds, then roughly every second
		222	my $w;
		223
		224	my $cb = sub {
		225	# cancel the old timer while creating a new one
		226	$w = AnyEvent->timer (after => 1, cb => $cb);
		227	};
		228
		229	# start the "loop" by creating the first watcher
		230	$w = AnyEvent->timer (after => 0.5, cb => $cb);
		231
		232	=head3 TIMING ISSUES
		233
		234	There are two ways to handle timers: based on real time (relative, "fire
		235	in 10 seconds") and based on wallclock time (absolute, "fire at 12
		236	o'clock").
		237
		238	While most event loops expect timers to specified in a relative way, they
		239	use absolute time internally. This makes a difference when your clock
		240	"jumps", for example, when ntp decides to set your clock backwards from
		241	the wrong date of 2014-01-01 to 2008-01-01, a watcher that is supposed to
		242	fire "after" a second might actually take six years to finally fire.
		243
		244	AnyEvent cannot compensate for this. The only event loop that is conscious
		245	about these issues is L<EV>, which offers both relative (ev_timer, based
		246	on true relative time) and absolute (ev_periodic, based on wallclock time)
		247	timers.
		248
		249	AnyEvent always prefers relative timers, if available, matching the
		250	AnyEvent API.
		251
		252	=head2 SIGNAL WATCHERS
		253
		254	You can watch for signals using a signal watcher, C<signal> is the signal
		255	I<name> without any C<SIG> prefix, C<cb> is the Perl callback to
		256	be invoked whenever a signal occurs.
		257
		258	Although the callback might get passed parameters, their value and
		259	presence is undefined and you cannot rely on them. Portable AnyEvent
		260	callbacks cannot use arguments passed to signal watcher callbacks.
		261
		262	Multiple signal occurances can be clumped together into one callback
		263	invocation, and callback invocation will be synchronous. synchronous means
		264	that it might take a while until the signal gets handled by the process,
		265	but it is guarenteed not to interrupt any other callbacks.
		266
		267	The main advantage of using these watchers is that you can share a signal
		268	between multiple watchers.
		269
		270	This watcher might use C<%SIG>, so programs overwriting those signals
		271	directly will likely not work correctly.
		272
		273	Example: exit on SIGINT
		274
		275	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
		276
		277	=head2 CHILD PROCESS WATCHERS
		278
		279	You can also watch on a child process exit and catch its exit status.
		280
		281	The child process is specified by the C<pid> argument (if set to C<0>, it
		282	watches for any child process exit). The watcher will trigger as often
		283	as status change for the child are received. This works by installing a
		284	signal handler for C<SIGCHLD>. The callback will be called with the pid
		285	and exit status (as returned by waitpid), so unlike other watcher types,
		286	you I<can> rely on child watcher callback arguments.
		287
		288	There is a slight catch to child watchers, however: you usually start them
		289	I<after> the child process was created, and this means the process could
		290	have exited already (and no SIGCHLD will be sent anymore).
		291
		292	Not all event models handle this correctly (POE doesn't), but even for
		293	event models that I<do> handle this correctly, they usually need to be
		294	loaded before the process exits (i.e. before you fork in the first place).
		295
		296	This means you cannot create a child watcher as the very first thing in an
		297	AnyEvent program, you I<have> to create at least one watcher before you
		298	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).
		299
		300	Example: fork a process and wait for it
		301
		302	my $done = AnyEvent->condvar;
		303
		304	AnyEvent::detect; # force event module to be initialised
		305
		306	my $pid = fork or exit 5;
		307
		308	my $w = AnyEvent->child (
		309	pid => $pid,
		310	cb => sub {
		311	my ($pid, $status) = @_;
		312	warn "pid $pid exited with status $status";
		313	$done->broadcast;
		314	},
		315	);
		316
		317	# do something else, then wait for process exit
		318	$done->wait;
		319
161	=head2 CONDITION WATCHERS	320	=head2 CONDITION VARIABLES
162		321
163	Condition watchers can be created by calling the C<< AnyEvent->condvar >>	322	Condition variables can be created by calling the C<< AnyEvent->condvar >>
164	method without any arguments.	323	method without any arguments.
165		324
166	A condition watcher watches for a condition - precisely that the C<<	325	A condition variable waits for a condition - precisely that the C<<
167	->broadcast >> method has been called.	326	->broadcast >> method has been called.
168		327
		328	They are very useful to signal that a condition has been fulfilled, for
		329	example, if you write a module that does asynchronous http requests,
		330	then a condition variable would be the ideal candidate to signal the
		331	availability of results.
		332
		333	You can also use condition variables to block your main program until
		334	an event occurs - for example, you could C<< ->wait >> in your main
		335	program until the user clicks the Quit button in your app, which would C<<
		336	->broadcast >> the "quit" event.
		337
169	Note that condition watchers recurse into the event loop - if you have	338	Note that condition variables recurse into the event loop - if you have
170	two watchers that call C<< ->wait >> in a round-robbin fashion, you	339	two pirces of code that call C<< ->wait >> in a round-robbin fashion, you
171	lose. Therefore, condition watchers are good to export to your caller, but	340	lose. Therefore, condition variables are good to export to your caller, but
172	you should avoid making a blocking wait, at least in callbacks, as this	341	you should avoid making a blocking wait yourself, at least in callbacks,
173	usually asks for trouble.	342	as this asks for trouble.
174		343
175	The watcher has only two methods:	344	This object has two methods:
176		345
177	=over 4	346	=over 4
178		347
179	=item $cv->wait	348	=item $cv->wait
180		349
181	Wait (blocking if necessary) until the C<< ->broadcast >> method has been	350	Wait (blocking if necessary) until the C<< ->broadcast >> method has been
182	called on c<$cv>, while servicing other watchers normally.	351	called on c<$cv>, while servicing other watchers normally.
183		352
184	Not all event models support a blocking wait - some die in that case, so
185	if you are using this from a module, never require a blocking wait, but
186	let the caller decide wether the call will block or not (for example,
187	by coupling condition variables with some kind of request results and
188	supporting callbacks so the caller knows that getting the result will not
189	block, while still suppporting blockign waits if the caller so desires).
190
191	You can only wait once on a condition - additional calls will return	353	You can only wait once on a condition - additional calls will return
192	immediately.	354	immediately.
193		355
		356	Not all event models support a blocking wait - some die in that case
		357	(programs might want to do that to stay interactive), so I<if you are
		358	using this from a module, never require a blocking wait>, but let the
		359	caller decide whether the call will block or not (for example, by coupling
		360	condition variables with some kind of request results and supporting
		361	callbacks so the caller knows that getting the result will not block,
		362	while still suppporting blocking waits if the caller so desires).
		363
		364	Another reason I<never> to C<< ->wait >> in a module is that you cannot
		365	sensibly have two C<< ->wait >>'s in parallel, as that would require
		366	multiple interpreters or coroutines/threads, none of which C<AnyEvent>
		367	can supply (the coroutine-aware backends L<AnyEvent::Impl::CoroEV> and
		368	L<AnyEvent::Impl::CoroEvent> explicitly support concurrent C<< ->wait >>'s
		369	from different coroutines, however).
		370
194	=item $cv->broadcast	371	=item $cv->broadcast
195		372
196	Flag the condition as ready - a running C<< ->wait >> and all further	373	Flag the condition as ready - a running C<< ->wait >> and all further
197	calls to C<wait> will return after this method has been called. If nobody	374	calls to C<wait> will (eventually) return after this method has been
198	is waiting the broadcast will be remembered..	375	called. If nobody is waiting the broadcast will be remembered..
		376
		377	=back
199		378
200	Example:	379	Example:
201		380
202	# wait till the result is ready	381	# wait till the result is ready
203	my $result_ready = AnyEvent->condvar;	382	my $result_ready = AnyEvent->condvar;
204		383
205	# do something such as adding a timer	384	# do something such as adding a timer
206	# or socket watcher the calls $result_ready->broadcast	385	# or socket watcher the calls $result_ready->broadcast
207	# when the "result" is ready.	386	# when the "result" is ready.
		387	# in this case, we simply use a timer:
		388	my $w = AnyEvent->timer (
		389	after => 1,
		390	cb => sub { $result_ready->broadcast },
		391	);
208		392
		393	# this "blocks" (while handling events) till the watcher
		394	# calls broadcast
209	$result_ready->wait;	395	$result_ready->wait;
210		396
211	=back	397	=head1 GLOBAL VARIABLES AND FUNCTIONS
212
213	=head2 SIGNAL WATCHERS
214
215	You can listen for signals using a signal watcher, C<signal> is the signal
216	I<name> without any C<SIG> prefix. Multiple signals events can be clumped
217	together into one callback invocation, and callback invocation might or
218	might not be asynchronous.
219
220	These watchers might use C<%SIG>, so programs overwriting those signals
221	directly will likely not work correctly.
222
223	Example: exit on SIGINT
224
225	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
226
227	=head2 CHILD PROCESS WATCHERS
228
229	You can also listen for the status of a child process specified by the
230	C<pid> argument (or any child if the pid argument is 0). The watcher will
231	trigger as often as status change for the child are received. This works
232	by installing a signal handler for C<SIGCHLD>. The callback will be called with
233	the pid and exit status (as returned by waitpid).
234
235	Example: wait for pid 1333
236
237	my $w = AnyEvent->child (pid => 1333, cb => sub { warn "exit status $?" });
238
239	=head1 GLOBALS
240		398
241	=over 4	399	=over 4
242		400
243	=item $AnyEvent::MODEL	401	=item $AnyEvent::MODEL
244		402
…		…
249	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).	407	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).
250		408
251	The known classes so far are:	409	The known classes so far are:
252		410
253	AnyEvent::Impl::CoroEV based on Coro::EV, best choice.	411	AnyEvent::Impl::CoroEV based on Coro::EV, best choice.
254	AnyEvent::Impl::EV based on EV (an interface to libev, also best choice).
255	AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.	412	AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
		413	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
256	AnyEvent::Impl::Event based on Event, also second best choice :)	414	AnyEvent::Impl::Event based on Event, second best choice.
257	AnyEvent::Impl::Glib based on Glib, second-best choice.	415	AnyEvent::Impl::Glib based on Glib, third-best choice.
		416	AnyEvent::Impl::Perl pure-perl implementation, inefficient but portable.
258	AnyEvent::Impl::Tk based on Tk, very bad choice.	417	AnyEvent::Impl::Tk based on Tk, very bad choice.
259	AnyEvent::Impl::Perl pure-perl implementation, inefficient.	418	AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
		419	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
		420	AnyEvent::Impl::POE based on POE, not generic enough for full support.
		421
		422	There is no support for WxWidgets, as WxWidgets has no support for
		423	watching file handles. However, you can use WxWidgets through the
		424	POE Adaptor, as POE has a Wx backend that simply polls 20 times per
		425	second, which was considered to be too horrible to even consider for
		426	AnyEvent. Likewise, other POE backends can be used by AnyEvent by using
		427	it's adaptor.
		428
		429	AnyEvent knows about L<Prima> and L<Wx> and will try to use L<POE> when
		430	autodetecting them.
260		431
261	=item AnyEvent::detect	432	=item AnyEvent::detect
262		433
263	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model if	434	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
264	necessary. You should only call this function right before you would have	435	if necessary. You should only call this function right before you would
265	created an AnyEvent watcher anyway, that is, very late at runtime.	436	have created an AnyEvent watcher anyway, that is, as late as possible at
		437	runtime.
266		438
267	=back	439	=back
268		440
269	=head1 WHAT TO DO IN A MODULE	441	=head1 WHAT TO DO IN A MODULE
270		442
271	As a module author, you should "use AnyEvent" and call AnyEvent methods	443	As a module author, you should C<use AnyEvent> and call AnyEvent methods
272	freely, but you should not load a specific event module or rely on it.	444	freely, but you should not load a specific event module or rely on it.
273		445
274	Be careful when you create watchers in the module body - Anyevent will	446	Be careful when you create watchers in the module body - AnyEvent will
275	decide which event module to use as soon as the first method is called, so	447	decide which event module to use as soon as the first method is called, so
276	by calling AnyEvent in your module body you force the user of your module	448	by calling AnyEvent in your module body you force the user of your module
277	to load the event module first.	449	to load the event module first.
278		450
		451	Never call C<< ->wait >> on a condition variable unless you I<know> that
		452	the C<< ->broadcast >> method has been called on it already. This is
		453	because it will stall the whole program, and the whole point of using
		454	events is to stay interactive.
		455
		456	It is fine, however, to call C<< ->wait >> when the user of your module
		457	requests it (i.e. if you create a http request object ad have a method
		458	called C<results> that returns the results, it should call C<< ->wait >>
		459	freely, as the user of your module knows what she is doing. always).
		460
279	=head1 WHAT TO DO IN THE MAIN PROGRAM	461	=head1 WHAT TO DO IN THE MAIN PROGRAM
280		462
281	There will always be a single main program - the only place that should	463	There will always be a single main program - the only place that should
282	dictate which event model to use.	464	dictate which event model to use.
283		465
284	If it doesn't care, it can just "use AnyEvent" and use it itself, or not	466	If it doesn't care, it can just "use AnyEvent" and use it itself, or not
285	do anything special and let AnyEvent decide which implementation to chose.	467	do anything special (it does not need to be event-based) and let AnyEvent
		468	decide which implementation to chose if some module relies on it.
286		469
287	If the main program relies on a specific event model (for example, in Gtk2	470	If the main program relies on a specific event model. For example, in
288	programs you have to rely on either Glib or Glib::Event), you should load	471	Gtk2 programs you have to rely on the Glib module. You should load the
289	it before loading AnyEvent or any module that uses it, generally, as early	472	event module before loading AnyEvent or any module that uses it: generally
290	as possible. The reason is that modules might create watchers when they	473	speaking, you should load it as early as possible. The reason is that
291	are loaded, and AnyEvent will decide on the event model to use as soon as	474	modules might create watchers when they are loaded, and AnyEvent will
292	it creates watchers, and it might chose the wrong one unless you load the	475	decide on the event model to use as soon as it creates watchers, and it
293	correct one yourself.	476	might chose the wrong one unless you load the correct one yourself.
294		477
295	You can chose to use a rather inefficient pure-perl implementation by	478	You can chose to use a rather inefficient pure-perl implementation by
296	loading the C<AnyEvent::Impl::Perl> module, but letting AnyEvent chose is	479	loading the C<AnyEvent::Impl::Perl> module, which gives you similar
297	generally better.	480	behaviour everywhere, but letting AnyEvent chose is generally better.
		481
		482	=head1 OTHER MODULES
		483
		484	L<AnyEvent> itself comes with useful utility modules:
		485
		486	To make it easier to do non-blocking IO the modules L<AnyEvent::Handle>
		487	and L<AnyEvent::Socket> are provided. L<AnyEvent::Handle> provides
		488	read and write buffers and manages watchers for reads and writes.
		489	L<AnyEvent::Socket> provides means to do non-blocking connects.
		490
		491	Aside from those there are these modules that support AnyEvent (and use it
		492	for non-blocking IO):
		493
		494	=over 4
		495
		496	=item L<AnyEvent::FastPing>
		497
		498	=item L<Net::IRC3>
		499
		500	=item L<Net::XMPP2>
		501
		502	=back
298		503
299	=cut	504	=cut
300		505
301	package AnyEvent;	506	package AnyEvent;
302		507
303	no warnings;	508	no warnings;
304	use strict;	509	use strict;
305		510
306	use Carp;	511	use Carp;
307		512
308	our $VERSION = '3.0';	513	our $VERSION = '3.3';
309	our $MODEL;	514	our $MODEL;
310		515
311	our $AUTOLOAD;	516	our $AUTOLOAD;
312	our @ISA;	517	our @ISA;
313		518
…		…
315		520
316	our @REGISTRY;	521	our @REGISTRY;
317		522
318	my @models = (	523	my @models = (
319	[Coro::EV:: => AnyEvent::Impl::CoroEV::],	524	[Coro::EV:: => AnyEvent::Impl::CoroEV::],
		525	[Coro::Event:: => AnyEvent::Impl::CoroEvent::],
320	[EV:: => AnyEvent::Impl::EV::],	526	[EV:: => AnyEvent::Impl::EV::],
321	[Coro::Event:: => AnyEvent::Impl::CoroEvent::],
322	[Event:: => AnyEvent::Impl::Event::],	527	[Event:: => AnyEvent::Impl::Event::],
323	[Glib:: => AnyEvent::Impl::Glib::],	528	[Glib:: => AnyEvent::Impl::Glib::],
324	[Tk:: => AnyEvent::Impl::Tk::],	529	[Tk:: => AnyEvent::Impl::Tk::],
		530	[Wx:: => AnyEvent::Impl::POE::],
		531	[Prima:: => AnyEvent::Impl::POE::],
325	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],	532	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
		533	# everything below here will not be autoprobed as the pureperl backend should work everywhere
		534	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
		535	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program
		536	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
326	);	537	);
327		538
328	our %method = map +($_ => 1), qw(io timer condvar broadcast wait signal one_event DESTROY);	539	our %method = map +($_ => 1), qw(io timer signal child condvar broadcast wait one_event DESTROY);
329		540
330	sub detect() {	541	sub detect() {
331	unless ($MODEL) {	542	unless ($MODEL) {
332	no strict 'refs';	543	no strict 'refs';
333		544
		545	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
		546	my $model = "AnyEvent::Impl::$1";
		547	if (eval "require $model") {
		548	$MODEL = $model;
		549	warn "AnyEvent: loaded model '$model' (forced by \$PERL_ANYEVENT_MODEL), using it.\n" if $verbose > 1;
		550	} else {
		551	warn "AnyEvent: unable to load model '$model' (from \$PERL_ANYEVENT_MODEL):\n$@" if $verbose;
		552	}
		553	}
		554
334	# check for already loaded models	555	# check for already loaded models
		556	unless ($MODEL) {
335	for (@REGISTRY, @models) {	557	for (@REGISTRY, @models) {
336	my ($package, $model) = @$_;	558	my ($package, $model) = @$_;
337	if (${"$package\::VERSION"} > 0) {	559	if (${"$package\::VERSION"} > 0) {
338	if (eval "require $model") {	560	if (eval "require $model") {
339	$MODEL = $model;	561	$MODEL = $model;
340	warn "AnyEvent: found model '$model', using it.\n" if $verbose > 1;	562	warn "AnyEvent: autodetected model '$model', using it.\n" if $verbose > 1;
341	last;	563	last;
		564	}
342	}	565	}
343	}	566	}
344	}
345		567
346	unless ($MODEL) {	568	unless ($MODEL) {
347	# try to load a model	569	# try to load a model
348		570
349	for (@REGISTRY, @models) {	571	for (@REGISTRY, @models) {
350	my ($package, $model) = @$_;	572	my ($package, $model) = @$_;
351	if (eval "require $package"	573	if (eval "require $package"
352	and ${"$package\::VERSION"} > 0	574	and ${"$package\::VERSION"} > 0
353	and eval "require $model") {	575	and eval "require $model") {
354	$MODEL = $model;	576	$MODEL = $model;
355	warn "AnyEvent: autoprobed and loaded model '$model', using it.\n" if $verbose > 1;	577	warn "AnyEvent: autoprobed model '$model', using it.\n" if $verbose > 1;
356	last;	578	last;
		579	}
357	}	580	}
		581
		582	$MODEL
		583	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) or Glib.";
358	}	584	}
359
360	$MODEL
361	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.";
362	}	585	}
363		586
364	unshift @ISA, $MODEL;	587	unshift @ISA, $MODEL;
365	push @{"$MODEL\::ISA"}, "AnyEvent::Base";	588	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
366	}	589	}
…		…
477	undef $CHLD_W unless keys %PID_CB;	700	undef $CHLD_W unless keys %PID_CB;
478	}	701	}
479		702
480	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE	703	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
481		704
		705	This is an advanced topic that you do not normally need to use AnyEvent in
		706	a module. This section is only of use to event loop authors who want to
		707	provide AnyEvent compatibility.
		708
482	If you need to support another event library which isn't directly	709	If you need to support another event library which isn't directly
483	supported by AnyEvent, you can supply your own interface to it by	710	supported by AnyEvent, you can supply your own interface to it by
484	pushing, before the first watcher gets created, the package name of	711	pushing, before the first watcher gets created, the package name of
485	the event module and the package name of the interface to use onto	712	the event module and the package name of the interface to use onto
486	C<@AnyEvent::REGISTRY>. You can do that before and even without loading	713	C<@AnyEvent::REGISTRY>. You can do that before and even without loading
487	AnyEvent.	714	AnyEvent, so it is reasonably cheap.
488		715
489	Example:	716	Example:
490		717
491	push @AnyEvent::REGISTRY, [urxvt => urxvt::anyevent::];	718	push @AnyEvent::REGISTRY, [urxvt => urxvt::anyevent::];
492		719
493	This tells AnyEvent to (literally) use the C<urxvt::anyevent::>	720	This tells AnyEvent to (literally) use the C<urxvt::anyevent::>
494	package/class when it finds the C<urxvt> package/module is loaded. When	721	package/class when it finds the C<urxvt> package/module is already loaded.
		722
495	AnyEvent is loaded and asked to find a suitable event model, it will	723	When AnyEvent is loaded and asked to find a suitable event model, it
496	first check for the presence of urxvt.	724	will first check for the presence of urxvt by trying to C<use> the
		725	C<urxvt::anyevent> module.
497		726
498	The class should provide implementations for all watcher types (see	727	The class should provide implementations for all watcher types. See
499	L<AnyEvent::Impl::Event> (source code), L<AnyEvent::Impl::Glib>	728	L<AnyEvent::Impl::EV> (source code), L<AnyEvent::Impl::Glib> (Source code)
500	(Source code) and so on for actual examples, use C<perldoc -m	729	and so on for actual examples. Use C<perldoc -m AnyEvent::Impl::Glib> to
501	AnyEvent::Impl::Glib> to see the sources).	730	see the sources.
502		731
		732	If you don't provide C<signal> and C<child> watchers than AnyEvent will
		733	provide suitable (hopefully) replacements.
		734
503	The above isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt)	735	The above example isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt)
504	uses the above line as-is. An interface isn't included in AnyEvent	736	terminal emulator uses the above line as-is. An interface isn't included
505	because it doesn't make sense outside the embedded interpreter inside	737	in AnyEvent because it doesn't make sense outside the embedded interpreter
506	I<rxvt-unicode>, and it is updated and maintained as part of the	738	inside I<rxvt-unicode>, and it is updated and maintained as part of the
507	I<rxvt-unicode> distribution.	739	I<rxvt-unicode> distribution.
508		740
509	I<rxvt-unicode> also cheats a bit by not providing blocking access to	741	I<rxvt-unicode> also cheats a bit by not providing blocking access to
510	condition variables: code blocking while waiting for a condition will	742	condition variables: code blocking while waiting for a condition will
511	C<die>. This still works with most modules/usages, and blocking calls must	743	C<die>. This still works with most modules/usages, and blocking calls must
512	not be in an interactive application, so it makes sense.	744	not be done in an interactive application, so it makes sense.
513		745
514	=head1 ENVIRONMENT VARIABLES	746	=head1 ENVIRONMENT VARIABLES
515		747
516	The following environment variables are used by this module:	748	The following environment variables are used by this module:
517		749
518	C<PERL_ANYEVENT_VERBOSE> when set to C<2> or higher, reports which event	750	=over 4
519	model gets used.
520		751
		752	=item C<PERL_ANYEVENT_VERBOSE>
		753
		754	By default, AnyEvent will be completely silent except in fatal
		755	conditions. You can set this environment variable to make AnyEvent more
		756	talkative.
		757
		758	When set to C<1> or higher, causes AnyEvent to warn about unexpected
		759	conditions, such as not being able to load the event model specified by
		760	C<PERL_ANYEVENT_MODEL>.
		761
		762	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
		763	model it chooses.
		764
		765	=item C<PERL_ANYEVENT_MODEL>
		766
		767	This can be used to specify the event model to be used by AnyEvent, before
		768	autodetection and -probing kicks in. It must be a string consisting
		769	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
		770	and the resulting module name is loaded and if the load was successful,
		771	used as event model. If it fails to load AnyEvent will proceed with
		772	autodetection and -probing.
		773
		774	This functionality might change in future versions.
		775
		776	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
		777	could start your program like this:
		778
		779	PERL_ANYEVENT_MODEL=Perl perl ...
		780
		781	=back
		782
521	=head1 EXAMPLE	783	=head1 EXAMPLE PROGRAM
522		784
523	The following program uses an io watcher to read data from stdin, a timer	785	The following program uses an I/O watcher to read data from STDIN, a timer
524	to display a message once per second, and a condvar to exit the program	786	to display a message once per second, and a condition variable to quit the
525	when the user enters quit:	787	program when the user enters quit:
526		788
527	use AnyEvent;	789	use AnyEvent;
528		790
529	my $cv = AnyEvent->condvar;	791	my $cv = AnyEvent->condvar;
530		792
531	my $io_watcher = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {	793	my $io_watcher = AnyEvent->io (
		794	fh => \*STDIN,
		795	poll => 'r',
		796	cb => sub {
532	warn "io event <$_[0]>\n"; # will always output <r>	797	warn "io event <$_[0]>\n"; # will always output <r>
533	chomp (my $input = <STDIN>); # read a line	798	chomp (my $input = <STDIN>); # read a line
534	warn "read: $input\n"; # output what has been read	799	warn "read: $input\n"; # output what has been read
535	$cv->broadcast if $input =~ /^q/i; # quit program if /^q/i	800	$cv->broadcast if $input =~ /^q/i; # quit program if /^q/i
		801	},
536	});	802	);
537		803
538	my $time_watcher; # can only be used once	804	my $time_watcher; # can only be used once
539		805
540	sub new_timer {	806	sub new_timer {
541	$timer = AnyEvent->timer (after => 1, cb => sub {	807	$timer = AnyEvent->timer (after => 1, cb => sub {
…		…
623	$txn->{finished}->wait;	889	$txn->{finished}->wait;
624	return $txn->{result};	890	return $txn->{result};
625		891
626	The actual code goes further and collects all errors (C<die>s, exceptions)	892	The actual code goes further and collects all errors (C<die>s, exceptions)
627	that occured during request processing. The C<result> method detects	893	that occured during request processing. The C<result> method detects
628	wether an exception as thrown (it is stored inside the $txn object)	894	whether an exception as thrown (it is stored inside the $txn object)
629	and just throws the exception, which means connection errors and other	895	and just throws the exception, which means connection errors and other
630	problems get reported tot he code that tries to use the result, not in a	896	problems get reported tot he code that tries to use the result, not in a
631	random callback.	897	random callback.
632		898
633	All of this enables the following usage styles:	899	All of this enables the following usage styles:
634		900
635	1. Blocking:	901	1. Blocking:
636		902
637	my $data = $fcp->client_get ($url);	903	my $data = $fcp->client_get ($url);
638		904
639	2. Blocking, but parallelizing:	905	2. Blocking, but running in parallel:
640		906
641	my @datas = map $_->result,	907	my @datas = map $_->result,
642	map $fcp->txn_client_get ($_),	908	map $fcp->txn_client_get ($_),
643	@urls;	909	@urls;
644		910
645	Both blocking examples work without the module user having to know	911	Both blocking examples work without the module user having to know
646	anything about events.	912	anything about events.
647		913
648	3a. Event-based in a main program, using any support Event module:	914	3a. Event-based in a main program, using any supported event module:
649		915
650	use Event;	916	use EV;
651		917
652	$fcp->txn_client_get ($url)->cb (sub {	918	$fcp->txn_client_get ($url)->cb (sub {
653	my $txn = shift;	919	my $txn = shift;
654	my $data = $txn->result;	920	my $data = $txn->result;
655	...	921	...
656	});	922	});
657		923
658	Event::loop;	924	EV::loop;
659		925
660	3b. The module user could use AnyEvent, too:	926	3b. The module user could use AnyEvent, too:
661		927
662	use AnyEvent;	928	use AnyEvent;
663		929
…		…
668	$quit->broadcast;	934	$quit->broadcast;
669	});	935	});
670		936
671	$quit->wait;	937	$quit->wait;
672		938
		939
		940	=head1 BENCHMARKS
		941
		942	To give you an idea of the performance and overheads that AnyEvent adds
		943	over the event loops themselves and to give you an impression of the speed
		944	of various event loops I prepared some benchmarks.
		945
		946	=head2 BENCHMARKING ANYEVENT OVERHEAD
		947
		948	Here is a benchmark of various supported event models used natively and
		949	through anyevent. The benchmark creates a lot of timers (with a zero
		950	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,
		951	which it is), lets them fire exactly once and destroys them again.
		952
		953	Source code for this benchmark is found as F<eg/bench> in the AnyEvent
		954	distribution.
		955
		956	=head3 Explanation of the columns
		957
		958	I<watcher> is the number of event watchers created/destroyed. Since
		959	different event models feature vastly different performances, each event
		960	loop was given a number of watchers so that overall runtime is acceptable
		961	and similar between tested event loop (and keep them from crashing): Glib
		962	would probably take thousands of years if asked to process the same number
		963	of watchers as EV in this benchmark.
		964
		965	I<bytes> is the number of bytes (as measured by the resident set size,
		966	RSS) consumed by each watcher. This method of measuring captures both C
		967	and Perl-based overheads.
		968
		969	I<create> is the time, in microseconds (millionths of seconds), that it
		970	takes to create a single watcher. The callback is a closure shared between
		971	all watchers, to avoid adding memory overhead. That means closure creation
		972	and memory usage is not included in the figures.
		973
		974	I<invoke> is the time, in microseconds, used to invoke a simple
		975	callback. The callback simply counts down a Perl variable and after it was
		976	invoked "watcher" times, it would C<< ->broadcast >> a condvar once to
		977	signal the end of this phase.
		978
		979	I<destroy> is the time, in microseconds, that it takes to destroy a single
		980	watcher.
		981
		982	=head3 Results
		983
		984	name watchers bytes create invoke destroy comment
		985	EV/EV 400000 244 0.56 0.46 0.31 EV native interface
		986	EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers
		987	CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal
		988	Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation
		989	Event/Event 16000 516 31.88 31.30 0.85 Event native interface
		990	Event/Any 16000 590 35.75 31.42 1.08 Event + AnyEvent watchers
		991	Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour
		992	Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers
		993	POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event
		994	POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select
		995
		996	=head3 Discussion
		997
		998	The benchmark does I<not> measure scalability of the event loop very
		999	well. For example, a select-based event loop (such as the pure perl one)
		1000	can never compete with an event loop that uses epoll when the number of
		1001	file descriptors grows high. In this benchmark, all events become ready at
		1002	the same time, so select/poll-based implementations get an unnatural speed
		1003	boost.
		1004
		1005	Also, note that the number of watchers usually has a nonlinear effect on
		1006	overall speed, that is, creating twice as many watchers doesn't take twice
		1007	the time - usually it takes longer. This puts event loops tested with a
		1008	higher number of watchers at a disadvantage.
		1009
		1010	To put the range of results into perspective, consider that on the
		1011	benchmark machine, handling an event takes roughly 1600 CPU cycles with
		1012	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU
		1013	cycles with POE.
		1014
		1015	C<EV> is the sole leader regarding speed and memory use, which are both
		1016	maximal/minimal, respectively. Even when going through AnyEvent, it uses
		1017	far less memory than any other event loop and is still faster than Event
		1018	natively.
		1019
		1020	The pure perl implementation is hit in a few sweet spots (both the
		1021	constant timeout and the use of a single fd hit optimisations in the perl
		1022	interpreter and the backend itself). Nevertheless this shows that it
		1023	adds very little overhead in itself. Like any select-based backend its
		1024	performance becomes really bad with lots of file descriptors (and few of
		1025	them active), of course, but this was not subject of this benchmark.
		1026
		1027	The C<Event> module has a relatively high setup and callback invocation
		1028	cost, but overall scores in on the third place.
		1029
		1030	C<Glib>'s memory usage is quite a bit higher, but it features a
		1031	faster callback invocation and overall ends up in the same class as
		1032	C<Event>. However, Glib scales extremely badly, doubling the number of
		1033	watchers increases the processing time by more than a factor of four,
		1034	making it completely unusable when using larger numbers of watchers
		1035	(note that only a single file descriptor was used in the benchmark, so
		1036	inefficiencies of C<poll> do not account for this).
		1037
		1038	The C<Tk> adaptor works relatively well. The fact that it crashes with
		1039	more than 2000 watchers is a big setback, however, as correctness takes
		1040	precedence over speed. Nevertheless, its performance is surprising, as the
		1041	file descriptor is dup()ed for each watcher. This shows that the dup()
		1042	employed by some adaptors is not a big performance issue (it does incur a
		1043	hidden memory cost inside the kernel which is not reflected in the figures
		1044	above).
		1045
		1046	C<POE>, regardless of underlying event loop (whether using its pure
		1047	perl select-based backend or the Event module, the POE-EV backend
		1048	couldn't be tested because it wasn't working) shows abysmal performance
		1049	and memory usage: Watchers use almost 30 times as much memory as
		1050	EV watchers, and 10 times as much memory as Event (the high memory
		1051	requirements are caused by requiring a session for each watcher). Watcher
		1052	invocation speed is almost 900 times slower than with AnyEvent's pure perl
		1053	implementation. The design of the POE adaptor class in AnyEvent can not
		1054	really account for this, as session creation overhead is small compared
		1055	to execution of the state machine, which is coded pretty optimally within
		1056	L<AnyEvent::Impl::POE>. POE simply seems to be abysmally slow.
		1057
		1058	=head3 Summary
		1059
		1060	=over 4
		1061
		1062	=item * Using EV through AnyEvent is faster than any other event loop
		1063	(even when used without AnyEvent), but most event loops have acceptable
		1064	performance with or without AnyEvent.
		1065
		1066	=item * The overhead AnyEvent adds is usually much smaller than the overhead of
		1067	the actual event loop, only with extremely fast event loops such as EV
		1068	adds AnyEvent significant overhead.
		1069
		1070	=item * You should avoid POE like the plague if you want performance or
		1071	reasonable memory usage.
		1072
		1073	=back
		1074
		1075	=head2 BENCHMARKING THE LARGE SERVER CASE
		1076
		1077	This benchmark atcually benchmarks the event loop itself. It works by
		1078	creating a number of "servers": each server consists of a socketpair, a
		1079	timeout watcher that gets reset on activity (but never fires), and an I/O
		1080	watcher waiting for input on one side of the socket. Each time the socket
		1081	watcher reads a byte it will write that byte to a random other "server".
		1082
		1083	The effect is that there will be a lot of I/O watchers, only part of which
		1084	are active at any one point (so there is a constant number of active
		1085	fds for each loop iterstaion, but which fds these are is random). The
		1086	timeout is reset each time something is read because that reflects how
		1087	most timeouts work (and puts extra pressure on the event loops).
		1088
		1089	In this benchmark, we use 10000 socketpairs (20000 sockets), of which 100
		1090	(1%) are active. This mirrors the activity of large servers with many
		1091	connections, most of which are idle at any one point in time.
		1092
		1093	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent
		1094	distribution.
		1095
		1096	=head3 Explanation of the columns
		1097
		1098	I<sockets> is the number of sockets, and twice the number of "servers" (as
		1099	each server has a read and write socket end).
		1100
		1101	I<create> is the time it takes to create a socketpair (which is
		1102	nontrivial) and two watchers: an I/O watcher and a timeout watcher.
		1103
		1104	I<request>, the most important value, is the time it takes to handle a
		1105	single "request", that is, reading the token from the pipe and forwarding
		1106	it to another server. This includes deleting the old timeout and creating
		1107	a new one that moves the timeout into the future.
		1108
		1109	=head3 Results
		1110
		1111	name sockets create request
		1112	EV 20000 69.01 11.16
		1113	Perl 20000 73.32 35.87
		1114	Event 20000 212.62 257.32
		1115	Glib 20000 651.16 1896.30
		1116	POE 20000 349.67 12317.24 uses POE::Loop::Event
		1117
		1118	=head3 Discussion
		1119
		1120	This benchmark I<does> measure scalability and overall performance of the
		1121	particular event loop.
		1122
		1123	EV is again fastest. Since it is using epoll on my system, the setup time
		1124	is relatively high, though.
		1125
		1126	Perl surprisingly comes second. It is much faster than the C-based event
		1127	loops Event and Glib.
		1128
		1129	Event suffers from high setup time as well (look at its code and you will
		1130	understand why). Callback invocation also has a high overhead compared to
		1131	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event
		1132	uses select or poll in basically all documented configurations.
		1133
		1134	Glib is hit hard by its quadratic behaviour w.r.t. many watchers. It
		1135	clearly fails to perform with many filehandles or in busy servers.
		1136
		1137	POE is still completely out of the picture, taking over 1000 times as long
		1138	as EV, and over 100 times as long as the Perl implementation, even though
		1139	it uses a C-based event loop in this case.
		1140
		1141	=head3 Summary
		1142
		1143	=over 4
		1144
		1145	=item * The pure perl implementation performs extremely well, considering
		1146	that it uses select.
		1147
		1148	=item * Avoid Glib or POE in large projects where performance matters.
		1149
		1150	=back
		1151
		1152	=head2 BENCHMARKING SMALL SERVERS
		1153
		1154	While event loops should scale (and select-based ones do not...) even to
		1155	large servers, most programs we (or I :) actually write have only a few
		1156	I/O watchers.
		1157
		1158	In this benchmark, I use the same benchmark program as in the large server
		1159	case, but it uses only eight "servers", of which three are active at any
		1160	one time. This should reflect performance for a small server relatively
		1161	well.
		1162
		1163	The columns are identical to the previous table.
		1164
		1165	=head3 Results
		1166
		1167	name sockets create request
		1168	EV 16 20.00 6.54
		1169	Perl 16 25.75 12.62
		1170	Event 16 81.27 35.86
		1171	Glib 16 32.63 15.48
		1172	POE 16 261.87 276.28 uses POE::Loop::Event
		1173
		1174	=head3 Discussion
		1175
		1176	The benchmark tries to test the performance of a typical small
		1177	server. While knowing how various event loops perform is interesting, keep
		1178	in mind that their overhead in this case is usually not as important, due
		1179	to the small absolute number of watchers (that is, you need efficiency and
		1180	speed most when you have lots of watchers, not when you only have a few of
		1181	them).
		1182
		1183	EV is again fastest.
		1184
		1185	The C-based event loops Event and Glib come in second this time, as the
		1186	overhead of running an iteration is much smaller in C than in Perl (little
		1187	code to execute in the inner loop, and perl's function calling overhead is
		1188	high, and updating all the data structures is costly).
		1189
		1190	The pure perl event loop is much slower, but still competitive.
		1191
		1192	POE also performs much better in this case, but is is still far behind the
		1193	others.
		1194
		1195	=head3 Summary
		1196
		1197	=over 4
		1198
		1199	=item * C-based event loops perform very well with small number of
		1200	watchers, as the management overhead dominates.
		1201
		1202	=back
		1203
		1204
		1205	=head1 FORK
		1206
		1207	Most event libraries are not fork-safe. The ones who are usually are
		1208	because they are so inefficient. Only L<EV> is fully fork-aware.
		1209
		1210	If you have to fork, you must either do so I<before> creating your first
		1211	watcher OR you must not use AnyEvent at all in the child.
		1212
		1213
		1214	=head1 SECURITY CONSIDERATIONS
		1215
		1216	AnyEvent can be forced to load any event model via
		1217	$ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used to
		1218	execute arbitrary code or directly gain access, it can easily be used to
		1219	make the program hang or malfunction in subtle ways, as AnyEvent watchers
		1220	will not be active when the program uses a different event model than
		1221	specified in the variable.
		1222
		1223	You can make AnyEvent completely ignore this variable by deleting it
		1224	before the first watcher gets created, e.g. with a C<BEGIN> block:
		1225
		1226	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }
		1227
		1228	use AnyEvent;
		1229
		1230
673	=head1 SEE ALSO	1231	=head1 SEE ALSO
674		1232
675	Event modules: L<Coro::Event>, L<Coro>, L<Event>, L<Glib::Event>, L<Glib>.	1233	Event modules: L<Coro::EV>, L<EV>, L<EV::Glib>, L<Glib::EV>,
		1234	L<Coro::Event>, L<Event>, L<Glib::Event>, L<Glib>, L<Coro>, L<Tk>,
		1235	L<Event::Lib>, L<Qt>, L<POE>.
676		1236
		1237	Implementations: L<AnyEvent::Impl::CoroEV>, L<AnyEvent::Impl::EV>,
677	Implementations: L<AnyEvent::Impl::Coro>, L<AnyEvent::Impl::Event>, L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>.	1238	L<AnyEvent::Impl::CoroEvent>, L<AnyEvent::Impl::Event>, L<AnyEvent::Impl::Glib>,
		1239	L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, L<AnyEvent::Impl::EventLib>,
		1240	L<AnyEvent::Impl::Qt>, L<AnyEvent::Impl::POE>.
678		1241
679	Nontrivial usage example: L<Net::FCP>.	1242	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>.
680		1243
681	=head1	1244
		1245	=head1 AUTHOR
		1246
		1247	Marc Lehmann <schmorp@schmorp.de>
		1248	http://home.schmorp.de/
682		1249
683	=cut	1250	=cut
684		1251
685	1	1252	1
686		1253

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.44 by root, Mon Apr 7 19:42:18 2008 UTC vs. Revision 1.100 by elmex, Sun Apr 27 19:15:43 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.44 by root, Mon Apr 7 19:42:18 2008 UTC vs.
Revision 1.100 by elmex, Sun Apr 27 19:15:43 2008 UTC