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

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.131 by root, Sat May 24 17:48:38 2008 UTC vs.
Revision 1.173 by root, Mon Jul 21 03:47:22 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, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops	5	EV, 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
11	my $w = AnyEvent->io (fh => $fh, poll => "r\|w", cb => sub {	11	my $w = AnyEvent->io (fh => $fh, poll => "r\|w", cb => sub { ... });
12	...
13	});
14		12
15	my $w = AnyEvent->timer (after => $seconds, cb => sub {	13	my $w = AnyEvent->timer (after => $seconds, cb => sub { ... });
		14	my $w = AnyEvent->timer (after => $seconds, interval => $seconds, cb => ...
		15
		16	print AnyEvent->now; # prints current event loop time
		17	print AnyEvent->time; # think Time::HiRes::time or simply CORE::time.
		18
		19	my $w = AnyEvent->signal (signal => "TERM", cb => sub { ... });
		20
		21	my $w = AnyEvent->child (pid => $pid, cb => sub {
		22	my ($pid, $status) = @_;
16	...	23	...
17	});	24	});
18		25
19	my $w = AnyEvent->condvar; # stores whether a condition was flagged	26	my $w = AnyEvent->condvar; # stores whether a condition was flagged
20	$w->send; # wake up current and all future recv's	27	$w->send; # wake up current and all future recv's
21	$w->recv; # enters "main loop" till $condvar gets ->send	28	$w->recv; # enters "main loop" till $condvar gets ->send
		29	# use a condvar in callback mode:
		30	$w->cb (sub { $_[0]->recv });
		31
		32	=head1 INTRODUCTION/TUTORIAL
		33
		34	This manpage is mainly a reference manual. If you are interested
		35	in a tutorial or some gentle introduction, have a look at the
		36	L<AnyEvent::Intro> manpage.
22		37
23	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)	38	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
24		39
25	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen	40	Glib, POE, IO::Async, Event... CPAN offers event models by the dozen
26	nowadays. So what is different about AnyEvent?	41	nowadays. So what is different about AnyEvent?
27		42
28	Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of	43	Executive Summary: AnyEvent is I<compatible>, AnyEvent is I<free of
29	policy> and AnyEvent is I<small and efficient>.	44	policy> and AnyEvent is I<small and efficient>.
30		45
31	First and foremost, I<AnyEvent is not an event model> itself, it only	46	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	47	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,	48	pragmatic way. For event models and certain classes of immortals alike,
34	the statement "there can only be one" is a bitter reality: In general,	49	the statement "there can only be one" is a bitter reality: In general,
35	only one event loop can be active at the same time in a process. AnyEvent	50	only one event loop can be active at the same time in a process. AnyEvent
36	helps hiding the differences between those event loops.	51	cannot change this, but it can hide the differences between those event
		52	loops.
37		53
38	The goal of AnyEvent is to offer module authors the ability to do event	54	The goal of AnyEvent is to offer module authors the ability to do event
39	programming (waiting for I/O or timer events) without subscribing to a	55	programming (waiting for I/O or timer events) without subscribing to a
40	religion, a way of living, and most importantly: without forcing your	56	religion, a way of living, and most importantly: without forcing your
41	module users into the same thing by forcing them to use the same event	57	module users into the same thing by forcing them to use the same event
42	model you use.	58	model you use.
43		59
44	For modules like POE or IO::Async (which is a total misnomer as it is	60	For modules like POE or IO::Async (which is a total misnomer as it is
45	actually doing all I/O I<synchronously>...), using them in your module is	61	actually doing all I/O I<synchronously>...), using them in your module is
46	like joining a cult: After you joined, you are dependent on them and you	62	like joining a cult: After you joined, you are dependent on them and you
47	cannot use anything else, as it is simply incompatible to everything that	63	cannot use anything else, as they are simply incompatible to everything
48	isn't itself. What's worse, all the potential users of your module are	64	that isn't them. What's worse, all the potential users of your
49	I<also> forced to use the same event loop you use.	65	module are I<also> forced to use the same event loop you use.
50		66
51	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works	67	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
52	fine. AnyEvent + Tk works fine etc. etc. but none of these work together	68	fine. AnyEvent + Tk works fine etc. etc. but none of these work together
53	with the rest: POE + IO::Async? no go. Tk + Event? no go. Again: if	69	with the rest: POE + IO::Async? No go. Tk + Event? No go. Again: if
54	your module uses one of those, every user of your module has to use it,	70	your module uses one of those, every user of your module has to use it,
55	too. But if your module uses AnyEvent, it works transparently with all	71	too. But if your module uses AnyEvent, it works transparently with all
56	event models it supports (including stuff like POE and IO::Async, as long	72	event models it supports (including stuff like IO::Async, as long as those
57	as those use one of the supported event loops. It is trivial to add new	73	use one of the supported event loops. It is trivial to add new event loops
58	event loops to AnyEvent, too, so it is future-proof).	74	to AnyEvent, too, so it is future-proof).
59		75
60	In addition to being free of having to use I<the one and only true event	76	In addition to being free of having to use I<the one and only true event
61	model>, AnyEvent also is free of bloat and policy: with POE or similar	77	model>, AnyEvent also is free of bloat and policy: with POE or similar
62	modules, you get an enormous amount of code and strict rules you have to	78	modules, you get an enormous amount of code and strict rules you have to
63	follow. AnyEvent, on the other hand, is lean and up to the point, by only	79	follow. AnyEvent, on the other hand, is lean and up to the point, by only
64	offering the functionality that is necessary, in as thin as a wrapper as	80	offering the functionality that is necessary, in as thin as a wrapper as
65	technically possible.	81	technically possible.
66		82
		83	Of course, AnyEvent comes with a big (and fully optional!) toolbox
		84	of useful functionality, such as an asynchronous DNS resolver, 100%
		85	non-blocking connects (even with TLS/SSL, IPv6 and on broken platforms
		86	such as Windows) and lots of real-world knowledge and workarounds for
		87	platform bugs and differences.
		88
67	Of course, if you want lots of policy (this can arguably be somewhat	89	Now, if you I<do want> lots of policy (this can arguably be somewhat
68	useful) and you want to force your users to use the one and only event	90	useful) and you want to force your users to use the one and only event
69	model, you should I<not> use this module.	91	model, you should I<not> use this module.
70		92
71	=head1 DESCRIPTION	93	=head1 DESCRIPTION
72		94
102	starts using it, all bets are off. Maybe you should tell their authors to	124	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...	125	use AnyEvent so their modules work together with others seamlessly...
104		126
105	The pure-perl implementation of AnyEvent is called	127	The pure-perl implementation of AnyEvent is called
106	C<AnyEvent::Impl::Perl>. Like other event modules you can load it	128	C<AnyEvent::Impl::Perl>. Like other event modules you can load it
107	explicitly.	129	explicitly and enjoy the high availability of that event loop :)
108		130
109	=head1 WATCHERS	131	=head1 WATCHERS
110		132
111	AnyEvent has the central concept of a I<watcher>, which is an object that	133	AnyEvent has the central concept of a I<watcher>, which is an object that
112	stores relevant data for each kind of event you are waiting for, such as	134	stores relevant data for each kind of event you are waiting for, such as
…		…
126	Many watchers either are used with "recursion" (repeating timers for	148	Many watchers either are used with "recursion" (repeating timers for
127	example), or need to refer to their watcher object in other ways.	149	example), or need to refer to their watcher object in other ways.
128		150
129	An any way to achieve that is this pattern:	151	An any way to achieve that is this pattern:
130		152
131	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {	153	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
132	# you can use $w here, for example to undef it	154	# you can use $w here, for example to undef it
133	undef $w;	155	undef $w;
134	});	156	});
135		157
136	Note that C<my $w; $w => combination. This is necessary because in Perl,	158	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	159	my variables are only visible after the statement in which they are
138	declared.	160	declared.
139		161
140	=head2 I/O WATCHERS	162	=head2 I/O WATCHERS
141		163
142	You can create an I/O watcher by calling the C<< AnyEvent->io >> method	164	You can create an I/O watcher by calling the C<< AnyEvent->io >> method
143	with the following mandatory key-value pairs as arguments:	165	with the following mandatory key-value pairs as arguments:
144		166
145	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch	167	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for events
146	for events. C<poll> must be a string that is either C<r> or C<w>,	168	(AnyEvent might or might not keep a reference to this file handle). C<poll>
147	which creates a watcher waiting for "r"eadable or "w"ritable events,	169	must be a string that is either C<r> or C<w>, which creates a watcher
148	respectively. C<cb> is the callback to invoke each time the file handle	170	waiting for "r"eadable or "w"ritable events, respectively. C<cb> is the
149	becomes ready.	171	callback to invoke each time the file handle becomes ready.
150		172
151	Although the callback might get passed parameters, their value and	173	Although the callback might get passed parameters, their value and
152	presence is undefined and you cannot rely on them. Portable AnyEvent	174	presence is undefined and you cannot rely on them. Portable AnyEvent
153	callbacks cannot use arguments passed to I/O watcher callbacks.	175	callbacks cannot use arguments passed to I/O watcher callbacks.
154		176
…		…
158		180
159	Some event loops issue spurious readyness notifications, so you should	181	Some event loops issue spurious readyness notifications, so you should
160	always use non-blocking calls when reading/writing from/to your file	182	always use non-blocking calls when reading/writing from/to your file
161	handles.	183	handles.
162		184
163	Example:
164
165	# wait for readability of STDIN, then read a line and disable the watcher	185	Example: wait for readability of STDIN, then read a line and disable the
		186	watcher.
		187
166	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {	188	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
167	chomp (my $input = <STDIN>);	189	chomp (my $input = <STDIN>);
168	warn "read: $input\n";	190	warn "read: $input\n";
169	undef $w;	191	undef $w;
170	});	192	});
…		…
180		202
181	Although the callback might get passed parameters, their value and	203	Although the callback might get passed parameters, their value and
182	presence is undefined and you cannot rely on them. Portable AnyEvent	204	presence is undefined and you cannot rely on them. Portable AnyEvent
183	callbacks cannot use arguments passed to time watcher callbacks.	205	callbacks cannot use arguments passed to time watcher callbacks.
184		206
185	The timer callback will be invoked at most once: if you want a repeating	207	The callback will normally be invoked once only. If you specify another
186	timer you have to create a new watcher (this is a limitation by both Tk	208	parameter, C<interval>, as a strictly positive number (> 0), then the
187	and Glib).	209	callback will be invoked regularly at that interval (in fractional
		210	seconds) after the first invocation. If C<interval> is specified with a
		211	false value, then it is treated as if it were missing.
188		212
189	Example:	213	The callback will be rescheduled before invoking the callback, but no
		214	attempt is done to avoid timer drift in most backends, so the interval is
		215	only approximate.
190		216
191	# fire an event after 7.7 seconds	217	Example: fire an event after 7.7 seconds.
		218
192	my $w = AnyEvent->timer (after => 7.7, cb => sub {	219	my $w = AnyEvent->timer (after => 7.7, cb => sub {
193	warn "timeout\n";	220	warn "timeout\n";
194	});	221	});
195		222
196	# to cancel the timer:	223	# to cancel the timer:
197	undef $w;	224	undef $w;
198		225
199	Example 2:
200
201	# fire an event after 0.5 seconds, then roughly every second	226	Example 2: fire an event after 0.5 seconds, then roughly every second.
202	my $w;
203		227
204	my $cb = sub {
205	# cancel the old timer while creating a new one
206	$w = AnyEvent->timer (after => 1, cb => $cb);	228	my $w = AnyEvent->timer (after => 0.5, interval => 1, cb => sub {
		229	warn "timeout\n";
207	};	230	};
208
209	# start the "loop" by creating the first watcher
210	$w = AnyEvent->timer (after => 0.5, cb => $cb);
211		231
212	=head3 TIMING ISSUES	232	=head3 TIMING ISSUES
213		233
214	There are two ways to handle timers: based on real time (relative, "fire	234	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	235	in 10 seconds") and based on wallclock time (absolute, "fire at 12
…		…
227	timers.	247	timers.
228		248
229	AnyEvent always prefers relative timers, if available, matching the	249	AnyEvent always prefers relative timers, if available, matching the
230	AnyEvent API.	250	AnyEvent API.
231		251
		252	AnyEvent has two additional methods that return the "current time":
		253
		254	=over 4
		255
		256	=item AnyEvent->time
		257
		258	This returns the "current wallclock time" as a fractional number of
		259	seconds since the Epoch (the same thing as C<time> or C<Time::HiRes::time>
		260	return, and the result is guaranteed to be compatible with those).
		261
		262	It progresses independently of any event loop processing, i.e. each call
		263	will check the system clock, which usually gets updated frequently.
		264
		265	=item AnyEvent->now
		266
		267	This also returns the "current wallclock time", but unlike C<time>, above,
		268	this value might change only once per event loop iteration, depending on
		269	the event loop (most return the same time as C<time>, above). This is the
		270	time that AnyEvent's timers get scheduled against.
		271
		272	I<In almost all cases (in all cases if you don't care), this is the
		273	function to call when you want to know the current time.>
		274
		275	This function is also often faster then C<< AnyEvent->time >>, and
		276	thus the preferred method if you want some timestamp (for example,
		277	L<AnyEvent::Handle> uses this to update it's activity timeouts).
		278
		279	The rest of this section is only of relevance if you try to be very exact
		280	with your timing, you can skip it without bad conscience.
		281
		282	For a practical example of when these times differ, consider L<Event::Lib>
		283	and L<EV> and the following set-up:
		284
		285	The event loop is running and has just invoked one of your callback at
		286	time=500 (assume no other callbacks delay processing). In your callback,
		287	you wait a second by executing C<sleep 1> (blocking the process for a
		288	second) and then (at time=501) you create a relative timer that fires
		289	after three seconds.
		290
		291	With L<Event::Lib>, C<< AnyEvent->time >> and C<< AnyEvent->now >> will
		292	both return C<501>, because that is the current time, and the timer will
		293	be scheduled to fire at time=504 (C<501> + C<3>).
		294
		295	With L<EV>, C<< AnyEvent->time >> returns C<501> (as that is the current
		296	time), but C<< AnyEvent->now >> returns C<500>, as that is the time the
		297	last event processing phase started. With L<EV>, your timer gets scheduled
		298	to run at time=503 (C<500> + C<3>).
		299
		300	In one sense, L<Event::Lib> is more exact, as it uses the current time
		301	regardless of any delays introduced by event processing. However, most
		302	callbacks do not expect large delays in processing, so this causes a
		303	higher drift (and a lot more system calls to get the current time).
		304
		305	In another sense, L<EV> is more exact, as your timer will be scheduled at
		306	the same time, regardless of how long event processing actually took.
		307
		308	In either case, if you care (and in most cases, you don't), then you
		309	can get whatever behaviour you want with any event loop, by taking the
		310	difference between C<< AnyEvent->time >> and C<< AnyEvent->now >> into
		311	account.
		312
		313	=back
		314
232	=head2 SIGNAL WATCHERS	315	=head2 SIGNAL WATCHERS
233		316
234	You can watch for signals using a signal watcher, C<signal> is the signal	317	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	318	I<name> in uppercase and without any C<SIG> prefix, C<cb> is the Perl
236	be invoked whenever a signal occurs.	319	callback to be invoked whenever a signal occurs.
237		320
238	Although the callback might get passed parameters, their value and	321	Although the callback might get passed parameters, their value and
239	presence is undefined and you cannot rely on them. Portable AnyEvent	322	presence is undefined and you cannot rely on them. Portable AnyEvent
240	callbacks cannot use arguments passed to signal watcher callbacks.	323	callbacks cannot use arguments passed to signal watcher callbacks.
241		324
…		…
277	AnyEvent program, you I<have> to create at least one watcher before you	360	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>).	361	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).
279		362
280	Example: fork a process and wait for it	363	Example: fork a process and wait for it
281		364
282	my $done = AnyEvent->condvar;	365	my $done = AnyEvent->condvar;
283		366
284	my $pid = fork or exit 5;	367	my $pid = fork or exit 5;
285		368
286	my $w = AnyEvent->child (	369	my $w = AnyEvent->child (
287	pid => $pid,	370	pid => $pid,
288	cb => sub {	371	cb => sub {
289	my ($pid, $status) = @_;	372	my ($pid, $status) = @_;
290	warn "pid $pid exited with status $status";	373	warn "pid $pid exited with status $status";
291	$done->send;	374	$done->send;
292	},	375	},
293	);	376	);
294		377
295	# do something else, then wait for process exit	378	# do something else, then wait for process exit
296	$done->recv;	379	$done->recv;
297		380
298	=head2 CONDITION VARIABLES	381	=head2 CONDITION VARIABLES
299		382
300	If you are familiar with some event loops you will know that all of them	383	If you are familiar with some event loops you will know that all of them
301	require you to run some blocking "loop", "run" or similar function that	384	require you to run some blocking "loop", "run" or similar function that
…		…
306		389
307	The instrument to do that is called a "condition variable", so called	390	The instrument to do that is called a "condition variable", so called
308	because they represent a condition that must become true.	391	because they represent a condition that must become true.
309		392
310	Condition variables can be created by calling the C<< AnyEvent->condvar	393	Condition variables can be created by calling the C<< AnyEvent->condvar
		394
311	>> method, usually without arguments. The only argument pair allowed is	395	>> method, usually without arguments. The only argument pair allowed is
		396
312	C<cb>, which specifies a callback to be called when the condition variable	397	C<cb>, which specifies a callback to be called when the condition variable
313	becomes true.	398	becomes true, with the condition variable as the first argument (but not
		399	the results).
314		400
315	After creation, the condition variable is "false" until it becomes "true"	401	After creation, the condition variable is "false" until it becomes "true"
316	by calling the C<send> method (or calling the condition variable as if it	402	by calling the C<send> method (or calling the condition variable as if it
317	were a callback).	403	were a callback, read about the caveats in the description for the C<<
		404	->send >> method).
318		405
319	Condition variables are similar to callbacks, except that you can	406	Condition variables are similar to callbacks, except that you can
320	optionally wait for them. They can also be called merge points - points	407	optionally wait for them. They can also be called merge points - points
321	in time where multiple outstanding events have been processed. And yet	408	in time where multiple outstanding events have been processed. And yet
322	another way to call them is transactions - each condition variable can be	409	another way to call them is transactions - each condition variable can be
…		…
373		460
374	my $done = AnyEvent->condvar;	461	my $done = AnyEvent->condvar;
375	my $delay = AnyEvent->timer (after => 5, cb => $done);	462	my $delay = AnyEvent->timer (after => 5, cb => $done);
376	$done->recv;	463	$done->recv;
377		464
		465	Example: Imagine an API that returns a condvar and doesn't support
		466	callbacks. This is how you make a synchronous call, for example from
		467	the main program:
		468
		469	use AnyEvent::CouchDB;
		470
		471	...
		472
		473	my @info = $couchdb->info->recv;
		474
		475	And this is how you would just ste a callback to be called whenever the
		476	results are available:
		477
		478	$couchdb->info->cb (sub {
		479	my @info = $_[0]->recv;
		480	});
		481
378	=head3 METHODS FOR PRODUCERS	482	=head3 METHODS FOR PRODUCERS
379		483
380	These methods should only be used by the producing side, i.e. the	484	These methods should only be used by the producing side, i.e. the
381	code/module that eventually sends the signal. Note that it is also	485	code/module that eventually sends the signal. Note that it is also
382	the producer side which creates the condvar in most cases, but it isn't	486	the producer side which creates the condvar in most cases, but it isn't
…		…
394	immediately from within send.	498	immediately from within send.
395		499
396	Any arguments passed to the C<send> call will be returned by all	500	Any arguments passed to the C<send> call will be returned by all
397	future C<< ->recv >> calls.	501	future C<< ->recv >> calls.
398		502
399	Condition variables are overloaded so one can call them directly (as a	503	Condition variables are overloaded so one can call them directly
400	code reference). Calling them directly is the same as calling C<send>.	504	(as a code reference). Calling them directly is the same as calling
		505	C<send>. Note, however, that many C-based event loops do not handle
		506	overloading, so as tempting as it may be, passing a condition variable
		507	instead of a callback does not work. Both the pure perl and EV loops
		508	support overloading, however, as well as all functions that use perl to
		509	invoke a callback (as in L<AnyEvent::Socket> and L<AnyEvent::DNS> for
		510	example).
401		511
402	=item $cv->croak ($error)	512	=item $cv->croak ($error)
403		513
404	Similar to send, but causes all call's to C<< ->recv >> to invoke	514	Similar to send, but causes all call's to C<< ->recv >> to invoke
405	C<Carp::croak> with the given error message/object/scalar.	515	C<Carp::croak> with the given error message/object/scalar.
…		…
509	=item $bool = $cv->ready	619	=item $bool = $cv->ready
510		620
511	Returns true when the condition is "true", i.e. whether C<send> or	621	Returns true when the condition is "true", i.e. whether C<send> or
512	C<croak> have been called.	622	C<croak> have been called.
513		623
514	=item $cb = $cv->cb ([new callback])	624	=item $cb = $cv->cb ($cb->($cv))
515		625
516	This is a mutator function that returns the callback set and optionally	626	This is a mutator function that returns the callback set and optionally
517	replaces it before doing so.	627	replaces it before doing so.
518		628
519	The callback will be called when the condition becomes "true", i.e. when	629	The callback will be called when the condition becomes "true", i.e. when
520	C<send> or C<croak> are called. Calling C<recv> inside the callback	630	C<send> or C<croak> are called, with the only argument being the condition
521	or at any later time is guaranteed not to block.	631	variable itself. Calling C<recv> inside the callback or at any later time
		632	is guaranteed not to block.
522		633
523	=back	634	=back
524		635
525	=head1 GLOBAL VARIABLES AND FUNCTIONS	636	=head1 GLOBAL VARIABLES AND FUNCTIONS
526		637
…		…
612		723
613	If it doesn't care, it can just "use AnyEvent" and use it itself, or not	724	If it doesn't care, it can just "use AnyEvent" and use it itself, or not
614	do anything special (it does not need to be event-based) and let AnyEvent	725	do anything special (it does not need to be event-based) and let AnyEvent
615	decide which implementation to chose if some module relies on it.	726	decide which implementation to chose if some module relies on it.
616		727
617	If the main program relies on a specific event model. For example, in	728	If the main program relies on a specific event model - for example, in
618	Gtk2 programs you have to rely on the Glib module. You should load the	729	Gtk2 programs you have to rely on the Glib module - you should load the
619	event module before loading AnyEvent or any module that uses it: generally	730	event module before loading AnyEvent or any module that uses it: generally
620	speaking, you should load it as early as possible. The reason is that	731	speaking, you should load it as early as possible. The reason is that
621	modules might create watchers when they are loaded, and AnyEvent will	732	modules might create watchers when they are loaded, and AnyEvent will
622	decide on the event model to use as soon as it creates watchers, and it	733	decide on the event model to use as soon as it creates watchers, and it
623	might chose the wrong one unless you load the correct one yourself.	734	might chose the wrong one unless you load the correct one yourself.
624		735
625	You can chose to use a rather inefficient pure-perl implementation by	736	You can chose to use a pure-perl implementation by loading the
626	loading the C<AnyEvent::Impl::Perl> module, which gives you similar	737	C<AnyEvent::Impl::Perl> module, which gives you similar behaviour
627	behaviour everywhere, but letting AnyEvent chose is generally better.	738	everywhere, but letting AnyEvent chose the model is generally better.
		739
		740	=head2 MAINLOOP EMULATION
		741
		742	Sometimes (often for short test scripts, or even standalone programs who
		743	only want to use AnyEvent), you do not want to run a specific event loop.
		744
		745	In that case, you can use a condition variable like this:
		746
		747	AnyEvent->condvar->recv;
		748
		749	This has the effect of entering the event loop and looping forever.
		750
		751	Note that usually your program has some exit condition, in which case
		752	it is better to use the "traditional" approach of storing a condition
		753	variable somewhere, waiting for it, and sending it when the program should
		754	exit cleanly.
		755
628		756
629	=head1 OTHER MODULES	757	=head1 OTHER MODULES
630		758
631	The following is a non-exhaustive list of additional modules that use	759	The following is a non-exhaustive list of additional modules that use
632	AnyEvent and can therefore be mixed easily with other AnyEvent modules	760	AnyEvent and can therefore be mixed easily with other AnyEvent modules
…		…
638	=item L<AnyEvent::Util>	766	=item L<AnyEvent::Util>
639		767
640	Contains various utility functions that replace often-used but blocking	768	Contains various utility functions that replace often-used but blocking
641	functions such as C<inet_aton> by event-/callback-based versions.	769	functions such as C<inet_aton> by event-/callback-based versions.
642		770
643	=item L<AnyEvent::Handle>
644
645	Provide read and write buffers and manages watchers for reads and writes.
646
647	=item L<AnyEvent::Socket>	771	=item L<AnyEvent::Socket>
648		772
649	Provides various utility functions for (internet protocol) sockets,	773	Provides various utility functions for (internet protocol) sockets,
650	addresses and name resolution. Also functions to create non-blocking tcp	774	addresses and name resolution. Also functions to create non-blocking tcp
651	connections or tcp servers, with IPv6 and SRV record support and more.	775	connections or tcp servers, with IPv6 and SRV record support and more.
652		776
		777	=item L<AnyEvent::Handle>
		778
		779	Provide read and write buffers, manages watchers for reads and writes,
		780	supports raw and formatted I/O, I/O queued and fully transparent and
		781	non-blocking SSL/TLS.
		782
		783	=item L<AnyEvent::DNS>
		784
		785	Provides rich asynchronous DNS resolver capabilities.
		786
		787	=item L<AnyEvent::HTTP>
		788
		789	A simple-to-use HTTP library that is capable of making a lot of concurrent
		790	HTTP requests.
		791
653	=item L<AnyEvent::HTTPD>	792	=item L<AnyEvent::HTTPD>
654		793
655	Provides a simple web application server framework.	794	Provides a simple web application server framework.
656		795
657	=item L<AnyEvent::DNS>
658
659	Provides rich asynchronous DNS resolver capabilities.
660
661	=item L<AnyEvent::FastPing>	796	=item L<AnyEvent::FastPing>
662		797
663	The fastest ping in the west.	798	The fastest ping in the west.
		799
		800	=item L<AnyEvent::DBI>
		801
		802	Executes L<DBI> requests asynchronously in a proxy process.
		803
		804	=item L<AnyEvent::AIO>
		805
		806	Truly asynchronous I/O, should be in the toolbox of every event
		807	programmer. AnyEvent::AIO transparently fuses L<IO::AIO> and AnyEvent
		808	together.
		809
		810	=item L<AnyEvent::BDB>
		811
		812	Truly asynchronous Berkeley DB access. AnyEvent::BDB transparently fuses
		813	L<BDB> and AnyEvent together.
		814
		815	=item L<AnyEvent::GPSD>
		816
		817	A non-blocking interface to gpsd, a daemon delivering GPS information.
		818
		819	=item L<AnyEvent::IGS>
		820
		821	A non-blocking interface to the Internet Go Server protocol (used by
		822	L<App::IGS>).
664		823
665	=item L<Net::IRC3>	824	=item L<Net::IRC3>
666		825
667	AnyEvent based IRC client module family.	826	AnyEvent based IRC client module family.
668		827
…		…
681		840
682	=item L<Coro>	841	=item L<Coro>
683		842
684	Has special support for AnyEvent via L<Coro::AnyEvent>.	843	Has special support for AnyEvent via L<Coro::AnyEvent>.
685		844
686	=item L<AnyEvent::AIO>, L<IO::AIO>
687
688	Truly asynchronous I/O, should be in the toolbox of every event
689	programmer. AnyEvent::AIO transparently fuses IO::AIO and AnyEvent
690	together.
691
692	=item L<AnyEvent::BDB>, L<BDB>
693
694	Truly asynchronous Berkeley DB access. AnyEvent::AIO transparently fuses
695	IO::AIO and AnyEvent together.
696
697	=item L<IO::Lambda>	845	=item L<IO::Lambda>
698		846
699	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.	847	The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
700		848
701	=back	849	=back
…		…
707	no warnings;	855	no warnings;
708	use strict;	856	use strict;
709		857
710	use Carp;	858	use Carp;
711		859
712	our $VERSION = '4.0';	860	our $VERSION = 4.22;
713	our $MODEL;	861	our $MODEL;
714		862
715	our $AUTOLOAD;	863	our $AUTOLOAD;
716	our @ISA;	864	our @ISA;
717		865
		866	our @REGISTRY;
		867
		868	our $WIN32;
		869
		870	BEGIN {
		871	my $win32 = ! ! ($^O =~ /mswin32/i);
		872	eval "sub WIN32(){ $win32 }";
		873	}
		874
718	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;	875	our $verbose = $ENV{PERL_ANYEVENT_VERBOSE}*1;
719		876
720	our @REGISTRY;	877	our %PROTOCOL; # (ipv4\|ipv6) => (1\|2), higher numbers are preferred
721
722	our %PROTOCOL; # (ipv4\|ipv6) => (1\|2)
723		878
724	{	879	{
725	my $idx;	880	my $idx;
726	$PROTOCOL{$_} = ++$idx	881	$PROTOCOL{$_} = ++$idx
		882	for reverse split /\s,\s/,
727	for split /\s,\s/, $ENV{PERL_ANYEVENT_PROTOCOLS} \|\| "ipv4,ipv6";	883	$ENV{PERL_ANYEVENT_PROTOCOLS} \|\| "ipv4,ipv6";
728	}	884	}
729		885
730	my @models = (	886	my @models = (
731	[EV:: => AnyEvent::Impl::EV::],	887	[EV:: => AnyEvent::Impl::EV::],
732	[Event:: => AnyEvent::Impl::Event::],	888	[Event:: => AnyEvent::Impl::Event::],
733	[Tk:: => AnyEvent::Impl::Tk::],
734	[Wx:: => AnyEvent::Impl::POE::],
735	[Prima:: => AnyEvent::Impl::POE::],
736	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],	889	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
737	# everything below here will not be autoprobed as the pureperl backend should work everywhere	890	# everything below here will not be autoprobed
738	[Glib:: => AnyEvent::Impl::Glib::],	891	# as the pureperl backend should work everywhere
		892	# and is usually faster
		893	[Tk:: => AnyEvent::Impl::Tk::], # crashes with many handles
		894	[Glib:: => AnyEvent::Impl::Glib::], # becomes extremely slow with many watchers
739	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy	895	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
740	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program	896	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program
741	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza	897	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
		898	[Wx:: => AnyEvent::Impl::POE::],
		899	[Prima:: => AnyEvent::Impl::POE::],
742	);	900	);
743		901
744	our %method = map +($_ => 1), qw(io timer signal child condvar one_event DESTROY);	902	our %method = map +($_ => 1), qw(io timer time now signal child condvar one_event DESTROY);
745		903
746	our @post_detect;	904	our @post_detect;
747		905
748	sub post_detect(&) {	906	sub post_detect(&) {
749	my ($cb) = @_;	907	my ($cb) = @_;
…		…
766	}	924	}
767		925
768	sub detect() {	926	sub detect() {
769	unless ($MODEL) {	927	unless ($MODEL) {
770	no strict 'refs';	928	no strict 'refs';
		929	local $SIG{__DIE__};
771		930
772	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {	931	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
773	my $model = "AnyEvent::Impl::$1";	932	my $model = "AnyEvent::Impl::$1";
774	if (eval "require $model") {	933	if (eval "require $model") {
775	$MODEL = $model;	934	$MODEL = $model;
…		…
809	$MODEL	968	$MODEL
810	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";	969	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV, Event or Glib.";
811	}	970	}
812	}	971	}
813		972
		973	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
		974
814	unshift @ISA, $MODEL;	975	unshift @ISA, $MODEL;
815	push @{"$MODEL\::ISA"}, "AnyEvent::Base";	976
		977	require AnyEvent::Strict if $ENV{PERL_ANYEVENT_STRICT};
816		978
817	(shift @post_detect)->() while @post_detect;	979	(shift @post_detect)->() while @post_detect;
818	}	980	}
819		981
820	$MODEL	982	$MODEL
…		…
830		992
831	my $class = shift;	993	my $class = shift;
832	$class->$func (@_);	994	$class->$func (@_);
833	}	995	}
834		996
		997	# utility function to dup a filehandle. this is used by many backends
		998	# to support binding more than one watcher per filehandle (they usually
		999	# allow only one watcher per fd, so we dup it to get a different one).
		1000	sub _dupfh($$$$) {
		1001	my ($poll, $fh, $r, $w) = @_;
		1002
		1003	require Fcntl;
		1004
		1005	# cygwin requires the fh mode to be matching, unix doesn't
		1006	my ($rw, $mode) = $poll eq "r" ? ($r, "<")
		1007	: $poll eq "w" ? ($w, ">")
		1008	: Carp::croak "AnyEvent->io requires poll set to either 'r' or 'w'";
		1009
		1010	open my $fh2, "$mode&" . fileno $fh
		1011	or die "cannot dup() filehandle: $!";
		1012
		1013	# we assume CLOEXEC is already set by perl in all important cases
		1014
		1015	($fh2, $rw)
		1016	}
		1017
835	package AnyEvent::Base;	1018	package AnyEvent::Base;
		1019
		1020	# default implementation for now and time
		1021
		1022	use Time::HiRes ();
		1023
		1024	sub time { Time::HiRes::time }
		1025	sub now { Time::HiRes::time }
836		1026
837	# default implementation for ->condvar	1027	# default implementation for ->condvar
838		1028
839	sub condvar {	1029	sub condvar {
840	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::	1030	bless { @_ == 3 ? (_ae_cb => $_[2]) : () }, AnyEvent::CondVar::
…		…
861	sub AnyEvent::Base::Signal::DESTROY {	1051	sub AnyEvent::Base::Signal::DESTROY {
862	my ($signal, $cb) = @{$_[0]};	1052	my ($signal, $cb) = @{$_[0]};
863		1053
864	delete $SIG_CB{$signal}{$cb};	1054	delete $SIG_CB{$signal}{$cb};
865		1055
866	$SIG{$signal} = 'DEFAULT' unless keys %{ $SIG_CB{$signal} };	1056	delete $SIG{$signal} unless keys %{ $SIG_CB{$signal} };
867	}	1057	}
868		1058
869	# default implementation for ->child	1059	# default implementation for ->child
870		1060
871	our %PID_CB;	1061	our %PID_CB;
…		…
898	or Carp::croak "required option 'pid' is missing";	1088	or Carp::croak "required option 'pid' is missing";
899		1089
900	$PID_CB{$pid}{$arg{cb}} = $arg{cb};	1090	$PID_CB{$pid}{$arg{cb}} = $arg{cb};
901		1091
902	unless ($WNOHANG) {	1092	unless ($WNOHANG) {
903	$WNOHANG = eval { require POSIX; &POSIX::WNOHANG } \|\| 1;	1093	$WNOHANG = eval { local $SIG{__DIE__}; require POSIX; &POSIX::WNOHANG } \|\| 1;
904	}	1094	}
905		1095
906	unless ($CHLD_W) {	1096	unless ($CHLD_W) {
907	$CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);	1097	$CHLD_W = AnyEvent->signal (signal => 'CHLD', cb => \&_sigchld);
908	# child could be a zombie already, so make at least one round	1098	# child could be a zombie already, so make at least one round
…		…
1041	C<PERL_ANYEVENT_MODEL>.	1231	C<PERL_ANYEVENT_MODEL>.
1042		1232
1043	When set to C<2> or higher, cause AnyEvent to report to STDERR which event	1233	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
1044	model it chooses.	1234	model it chooses.
1045		1235
		1236	=item C<PERL_ANYEVENT_STRICT>
		1237
		1238	AnyEvent does not do much argument checking by default, as thorough
		1239	argument checking is very costly. Setting this variable to a true value
		1240	will cause AnyEvent to load C<AnyEvent::Strict> and then to thoroughly
		1241	check the arguments passed to most method calls. If it finds any problems
		1242	it will croak.
		1243
		1244	In other words, enables "strict" mode.
		1245
		1246	Unlike C<use strict> it is definitely recommended ot keep it off in
		1247	production.
		1248
1046	=item C<PERL_ANYEVENT_MODEL>	1249	=item C<PERL_ANYEVENT_MODEL>
1047		1250
1048	This can be used to specify the event model to be used by AnyEvent, before	1251	This can be used to specify the event model to be used by AnyEvent, before
1049	auto detection and -probing kicks in. It must be a string consisting	1252	auto detection and -probing kicks in. It must be a string consisting
1050	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended	1253	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
…		…
1055	This functionality might change in future versions.	1258	This functionality might change in future versions.
1056		1259
1057	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you	1260	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
1058	could start your program like this:	1261	could start your program like this:
1059		1262
1060	PERL_ANYEVENT_MODEL=Perl perl ...	1263	PERL_ANYEVENT_MODEL=Perl perl ...
1061		1264
1062	=item C<PERL_ANYEVENT_PROTOCOLS>	1265	=item C<PERL_ANYEVENT_PROTOCOLS>
1063		1266
1064	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences	1267	Used by both L<AnyEvent::DNS> and L<AnyEvent::Socket> to determine preferences
1065	for IPv4 or IPv6. The default is unspecified (and might change, or be the result	1268	for IPv4 or IPv6. The default is unspecified (and might change, or be the result
…		…
1087	some (broken) firewalls drop such DNS packets, which is why it is off by	1290	some (broken) firewalls drop such DNS packets, which is why it is off by
1088	default.	1291	default.
1089		1292
1090	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce	1293	Setting this variable to C<1> will cause L<AnyEvent::DNS> to announce
1091	EDNS0 in its DNS requests.	1294	EDNS0 in its DNS requests.
		1295
		1296	=item C<PERL_ANYEVENT_MAX_FORKS>
		1297
		1298	The maximum number of child processes that C<AnyEvent::Util::fork_call>
		1299	will create in parallel.
1092		1300
1093	=back	1301	=back
1094		1302
1095	=head1 EXAMPLE PROGRAM	1303	=head1 EXAMPLE PROGRAM
1096		1304
…		…
1535	specified in the variable.	1743	specified in the variable.
1536		1744
1537	You can make AnyEvent completely ignore this variable by deleting it	1745	You can make AnyEvent completely ignore this variable by deleting it
1538	before the first watcher gets created, e.g. with a C<BEGIN> block:	1746	before the first watcher gets created, e.g. with a C<BEGIN> block:
1539		1747
1540	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }	1748	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }
1541		1749
1542	use AnyEvent;	1750	use AnyEvent;
1543		1751
1544	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can	1752	Similar considerations apply to $ENV{PERL_ANYEVENT_VERBOSE}, as that can
1545	be used to probe what backend is used and gain other information (which is	1753	be used to probe what backend is used and gain other information (which is
1546	probably even less useful to an attacker than PERL_ANYEVENT_MODEL).	1754	probably even less useful to an attacker than PERL_ANYEVENT_MODEL), and
		1755	$ENV{PERL_ANYEGENT_STRICT}.
		1756
		1757
		1758	=head1 BUGS
		1759
		1760	Perl 5.8 has numerous memleaks that sometimes hit this module and are hard
		1761	to work around. If you suffer from memleaks, first upgrade to Perl 5.10
		1762	and check wether the leaks still show up. (Perl 5.10.0 has other annoying
		1763	mamleaks, such as leaking on C<map> and C<grep> but it is usually not as
		1764	pronounced).
1547		1765
1548		1766
1549	=head1 SEE ALSO	1767	=head1 SEE ALSO
1550		1768
1551	Utility functions: L<AnyEvent::Util>.	1769	Utility functions: L<AnyEvent::Util>.
…		…
1568	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.	1786	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>, L<AnyEvent::DNS>.
1569		1787
1570		1788
1571	=head1 AUTHOR	1789	=head1 AUTHOR
1572		1790
1573	Marc Lehmann <schmorp@schmorp.de>	1791	Marc Lehmann <schmorp@schmorp.de>
1574	http://home.schmorp.de/	1792	http://home.schmorp.de/
1575		1793
1576	=cut	1794	=cut
1577		1795
1578	1	1796	1
1579		1797

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.131 by root, Sat May 24 17:48:38 2008 UTC vs. Revision 1.173 by root, Mon Jul 21 03:47:22 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.131 by root, Sat May 24 17:48:38 2008 UTC vs.
Revision 1.173 by root, Mon Jul 21 03:47:22 2008 UTC