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

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

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.52 by root, Sat Apr 19 03:47:24 2008 UTC vs. Revision 1.101 by root, Sun Apr 27 19:36:55 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.52 by root, Sat Apr 19 03:47:24 2008 UTC vs.
Revision 1.101 by root, Sun Apr 27 19:36:55 2008 UTC