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

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.44 by root, Mon Apr 7 19:42:18 2008 UTC vs.
Revision 1.80 by root, Fri Apr 25 09:11:59 2008 UTC

…		…
1	=head1 NAME	1	=head1 NAME
2		2
3	AnyEvent - provide framework for multiple event loops	3	AnyEvent - provide framework for multiple event loops
4		4
5	Event, Coro, Glib, Tk, Perl - various supported event loops	5	EV, Event, Coro::EV, Coro::Event, Glib, Tk, Perl, Event::Lib, Qt, POE - various supported event loops
6		6
7	=head1 SYNOPSIS	7	=head1 SYNOPSIS
8		8
9	use AnyEvent;	9	use AnyEvent;
10		10
14		14
15	my $w = AnyEvent->timer (after => $seconds, cb => sub {	15	my $w = AnyEvent->timer (after => $seconds, cb => sub {
16	...	16	...
17	});	17	});
18		18
19	my $w = AnyEvent->condvar; # stores wether a condition was flagged	19	my $w = AnyEvent->condvar; # stores whether a condition was flagged
20	$w->wait; # enters "main loop" till $condvar gets ->broadcast	20	$w->wait; # enters "main loop" till $condvar gets ->broadcast
21	$w->broadcast; # wake up current and all future wait's	21	$w->broadcast; # wake up current and all future wait's
22		22
23	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)	23	=head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
24		24
…		…
29	policy> and AnyEvent is I<small and efficient>.	29	policy> and AnyEvent is I<small and efficient>.
30		30
31	First and foremost, I<AnyEvent is not an event model> itself, it only	31	First and foremost, I<AnyEvent is not an event model> itself, it only
32	interfaces to whatever event model the main program happens to use in a	32	interfaces to whatever event model the main program happens to use in a
33	pragmatic way. For event models and certain classes of immortals alike,	33	pragmatic way. For event models and certain classes of immortals alike,
34	the statement "there can only be one" is a bitter reality, and AnyEvent	34	the statement "there can only be one" is a bitter reality: In general,
35	helps hiding the differences.	35	only one event loop can be active at the same time in a process. AnyEvent
		36	helps hiding the differences between those event loops.
36		37
37	The goal of AnyEvent is to offer module authors the ability to do event	38	The goal of AnyEvent is to offer module authors the ability to do event
38	programming (waiting for I/O or timer events) without subscribing to a	39	programming (waiting for I/O or timer events) without subscribing to a
39	religion, a way of living, and most importantly: without forcing your	40	religion, a way of living, and most importantly: without forcing your
40	module users into the same thing by forcing them to use the same event	41	module users into the same thing by forcing them to use the same event
41	model you use.	42	model you use.
42		43
43	For modules like POE or IO::Async (which is actually doing all I/O	44	For modules like POE or IO::Async (which is a total misnomer as it is
44	I<synchronously>...), using them in your module is like joining a	45	actually doing all I/O I<synchronously>...), using them in your module is
45	cult: After you joined, you are dependent on them and you cannot use	46	like joining a cult: After you joined, you are dependent on them and you
46	anything else, as it is simply incompatible to everything that isn't	47	cannot use anything else, as it is simply incompatible to everything that
47	itself.	48	isn't itself. What's worse, all the potential users of your module are
		49	I<also> forced to use the same event loop you use.
48		50
49	AnyEvent + POE works fine. AnyEvent + Glib works fine. AnyEvent + Tk	51	AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works
50	works fine etc. etc. but none of these work together with the rest: POE	52	fine. AnyEvent + Tk works fine etc. etc. but none of these work together
51	+ IO::Async? no go. Tk + Event? no go. If your module uses one of	53	with the rest: POE + IO::Async? no go. Tk + Event? no go. Again: if
52	those, every user of your module has to use it, too. If your module	54	your module uses one of those, every user of your module has to use it,
53	uses AnyEvent, it works transparently with all event models it supports	55	too. But if your module uses AnyEvent, it works transparently with all
54	(including stuff like POE and IO::Async).	56	event models it supports (including stuff like POE and IO::Async, as long
		57	as those use one of the supported event loops. It is trivial to add new
		58	event loops to AnyEvent, too, so it is future-proof).
55		59
56	In addition of being free of having to use I<the one and only true event	60	In addition to being free of having to use I<the one and only true event
57	model>, AnyEvent also is free of bloat and policy: with POE or similar	61	model>, AnyEvent also is free of bloat and policy: with POE or similar
58	modules, you get an enourmous amount of code and strict rules you have	62	modules, you get an enourmous amount of code and strict rules you have to
59	to follow. AnyEvent, on the other hand, is lean and to the point by only	63	follow. AnyEvent, on the other hand, is lean and up to the point, by only
60	offering the functionality that is useful, in as thin as a wrapper as	64	offering the functionality that is necessary, in as thin as a wrapper as
61	technically possible.	65	technically possible.
62		66
63	Of course, if you want lots of policy (this is arguably somewhat useful	67	Of course, if you want lots of policy (this can arguably be somewhat
64	in many cases) and you want to force your users to the one and only event	68	useful) and you want to force your users to use the one and only event
65	model your module forces on them, you should I<not> use this module.	69	model, you should I<not> use this module.
66		70
67		71
68	=head1 DESCRIPTION	72	=head1 DESCRIPTION
69		73
70	L<AnyEvent> provides an identical interface to multiple event loops. This	74	L<AnyEvent> provides an identical interface to multiple event loops. This
71	allows module authors to utilise an event loop without forcing module	75	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	76	users to use the same event loop (as only a single event loop can coexist
73	peacefully at any one time).	77	peacefully at any one time).
74		78
75	The interface itself is vaguely similar but not identical to the Event	79	The interface itself is vaguely similar, but not identical to the L<Event>
76	module.	80	module.
77		81
78	On the first call of any method, the module tries to detect the currently	82	During the first call of any watcher-creation method, the module tries
79	loaded event loop by probing wether any of the following modules is	83	to detect the currently loaded event loop by probing whether one of the
80	loaded: L<Coro::Event>, L<Event>, L<Glib>, L<Tk>. The first one found is	84	following modules is already loaded: L<Coro::EV>, L<Coro::Event>, L<EV>,
81	used. If none is found, the module tries to load these modules in the	85	L<Event>, L<Glib>, L<Tk>, L<AnyEvent::Impl::Perl>, L<Event::Lib>, L<Qt>,
82	order given. The first one that could be successfully loaded will be	86	L<POE>. The first one found is used. If none are found, the module tries
83	used. If still none could be found, AnyEvent will fall back to a pure-perl	87	to load these modules (excluding Event::Lib, Qt and POE as the pure perl
84	event loop, which is also not very efficient.	88	adaptor should always succeed) in the order given. The first one that can
		89	be successfully loaded will be used. If, after this, still none could be
		90	found, AnyEvent will fall back to a pure-perl event loop, which is not
		91	very efficient, but should work everywhere.
85		92
86	Because AnyEvent first checks for modules that are already loaded, loading	93	Because AnyEvent first checks for modules that are already loaded, loading
87	an Event model explicitly before first using AnyEvent will likely make	94	an event model explicitly before first using AnyEvent will likely make
88	that model the default. For example:	95	that model the default. For example:
89		96
90	use Tk;	97	use Tk;
91	use AnyEvent;	98	use AnyEvent;
92		99
93	# .. AnyEvent will likely default to Tk	100	# .. AnyEvent will likely default to Tk
		101
		102	The I<likely> means that, if any module loads another event model and
		103	starts using it, all bets are off. Maybe you should tell their authors to
		104	use AnyEvent so their modules work together with others seamlessly...
94		105
95	The pure-perl implementation of AnyEvent is called	106	The pure-perl implementation of AnyEvent is called
96	C<AnyEvent::Impl::Perl>. Like other event modules you can load it	107	C<AnyEvent::Impl::Perl>. Like other event modules you can load it
97	explicitly.	108	explicitly.
98		109
…		…
101	AnyEvent has the central concept of a I<watcher>, which is an object that	112	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	113	stores relevant data for each kind of event you are waiting for, such as
103	the callback to call, the filehandle to watch, etc.	114	the callback to call, the filehandle to watch, etc.
104		115
105	These watchers are normal Perl objects with normal Perl lifetime. After	116	These watchers are normal Perl objects with normal Perl lifetime. After
106	creating a watcher it will immediately "watch" for events and invoke	117	creating a watcher it will immediately "watch" for events and invoke the
		118	callback when the event occurs (of course, only when the event model
		119	is in control).
		120
107	the callback. To disable the watcher you have to destroy it (e.g. by	121	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	122	variable you store it in to C<undef> or otherwise deleting all references
109	references to it).	123	to it).
110		124
111	All watchers are created by calling a method on the C<AnyEvent> class.	125	All watchers are created by calling a method on the C<AnyEvent> class.
112		126
		127	Many watchers either are used with "recursion" (repeating timers for
		128	example), or need to refer to their watcher object in other ways.
		129
		130	An any way to achieve that is this pattern:
		131
		132	my $w; $w = AnyEvent->type (arg => value ..., cb => sub {
		133	# you can use $w here, for example to undef it
		134	undef $w;
		135	});
		136
		137	Note that C<my $w; $w => combination. This is necessary because in Perl,
		138	my variables are only visible after the statement in which they are
		139	declared.
		140
113	=head2 IO WATCHERS	141	=head2 I/O WATCHERS
114		142
115	You can create I/O watcher by calling the C<< AnyEvent->io >> method with	143	You can create an I/O watcher by calling the C<< AnyEvent->io >> method
116	the following mandatory arguments:	144	with the following mandatory key-value pairs as arguments:
117		145
118	C<fh> the Perl I<filehandle> (not filedescriptor) to watch for	146	C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for
119	events. C<poll> must be a string that is either C<r> or C<w>, that creates	147	events. C<poll> must be a string that is either C<r> or C<w>, which
120	a watcher waiting for "r"eadable or "w"ritable events. C<cb> the callback	148	creates a watcher waiting for "r"eadable or "w"ritable events,
121	to invoke everytime the filehandle becomes ready.	149	respectively. C<cb> is the callback to invoke each time the file handle
		150	becomes ready.
122		151
123	Only one io watcher per C<fh> and C<poll> combination is allowed (i.e. on	152	As long as the I/O watcher exists it will keep the file descriptor or a
124	a socket you can have one r + one w, not any more (limitation comes from	153	copy of it alive/open.
125	Tk - if you are sure you are not using Tk this limitation is gone).
126		154
127	Filehandles will be kept alive, so as long as the watcher exists, the	155	It is not allowed to close a file handle as long as any watcher is active
128	filehandle exists, too.	156	on the underlying file descriptor.
		157
		158	Some event loops issue spurious readyness notifications, so you should
		159	always use non-blocking calls when reading/writing from/to your file
		160	handles.
129		161
130	Example:	162	Example:
131		163
132	# wait for readability of STDIN, then read a line and disable the watcher	164	# wait for readability of STDIN, then read a line and disable the watcher
133	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {	165	my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {
…		…
139	=head2 TIME WATCHERS	171	=head2 TIME WATCHERS
140		172
141	You can create a time watcher by calling the C<< AnyEvent->timer >>	173	You can create a time watcher by calling the C<< AnyEvent->timer >>
142	method with the following mandatory arguments:	174	method with the following mandatory arguments:
143		175
144	C<after> after how many seconds (fractions are supported) should the timer	176	C<after> specifies after how many seconds (fractional values are
145	activate. C<cb> the callback to invoke.	177	supported) should the timer activate. C<cb> the callback to invoke in that
		178	case.
146		179
147	The timer callback will be invoked at most once: if you want a repeating	180	The timer callback will be invoked at most once: if you want a repeating
148	timer you have to create a new watcher (this is a limitation by both Tk	181	timer you have to create a new watcher (this is a limitation by both Tk
149	and Glib).	182	and Glib).
150		183
…		…
156	});	189	});
157		190
158	# to cancel the timer:	191	# to cancel the timer:
159	undef $w;	192	undef $w;
160		193
		194	Example 2:
		195
		196	# fire an event after 0.5 seconds, then roughly every second
		197	my $w;
		198
		199	my $cb = sub {
		200	# cancel the old timer while creating a new one
		201	$w = AnyEvent->timer (after => 1, cb => $cb);
		202	};
		203
		204	# start the "loop" by creating the first watcher
		205	$w = AnyEvent->timer (after => 0.5, cb => $cb);
		206
		207	=head3 TIMING ISSUES
		208
		209	There are two ways to handle timers: based on real time (relative, "fire
		210	in 10 seconds") and based on wallclock time (absolute, "fire at 12
		211	o'clock").
		212
		213	While most event loops expect timers to specified in a relative way, they
		214	use absolute time internally. This makes a difference when your clock
		215	"jumps", for example, when ntp decides to set your clock backwards from
		216	the wrong date of 2014-01-01 to 2008-01-01, a watcher that is supposed to
		217	fire "after" a second might actually take six years to finally fire.
		218
		219	AnyEvent cannot compensate for this. The only event loop that is conscious
		220	about these issues is L<EV>, which offers both relative (ev_timer, based
		221	on true relative time) and absolute (ev_periodic, based on wallclock time)
		222	timers.
		223
		224	AnyEvent always prefers relative timers, if available, matching the
		225	AnyEvent API.
		226
		227	=head2 SIGNAL WATCHERS
		228
		229	You can watch for signals using a signal watcher, C<signal> is the signal
		230	I<name> without any C<SIG> prefix, C<cb> is the Perl callback to
		231	be invoked whenever a signal occurs.
		232
		233	Multiple signal occurances can be clumped together into one callback
		234	invocation, and callback invocation will be synchronous. synchronous means
		235	that it might take a while until the signal gets handled by the process,
		236	but it is guarenteed not to interrupt any other callbacks.
		237
		238	The main advantage of using these watchers is that you can share a signal
		239	between multiple watchers.
		240
		241	This watcher might use C<%SIG>, so programs overwriting those signals
		242	directly will likely not work correctly.
		243
		244	Example: exit on SIGINT
		245
		246	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
		247
		248	=head2 CHILD PROCESS WATCHERS
		249
		250	You can also watch on a child process exit and catch its exit status.
		251
		252	The child process is specified by the C<pid> argument (if set to C<0>, it
		253	watches for any child process exit). The watcher will trigger as often
		254	as status change for the child are received. This works by installing a
		255	signal handler for C<SIGCHLD>. The callback will be called with the pid
		256	and exit status (as returned by waitpid).
		257
		258	Example: wait for pid 1333
		259
		260	my $w = AnyEvent->child (
		261	pid => 1333,
		262	cb => sub {
		263	my ($pid, $status) = @_;
		264	warn "pid $pid exited with status $status";
		265	},
		266	);
		267
161	=head2 CONDITION WATCHERS	268	=head2 CONDITION VARIABLES
162		269
163	Condition watchers can be created by calling the C<< AnyEvent->condvar >>	270	Condition variables can be created by calling the C<< AnyEvent->condvar >>
164	method without any arguments.	271	method without any arguments.
165		272
166	A condition watcher watches for a condition - precisely that the C<<	273	A condition variable waits for a condition - precisely that the C<<
167	->broadcast >> method has been called.	274	->broadcast >> method has been called.
168		275
		276	They are very useful to signal that a condition has been fulfilled, for
		277	example, if you write a module that does asynchronous http requests,
		278	then a condition variable would be the ideal candidate to signal the
		279	availability of results.
		280
		281	You can also use condition variables to block your main program until
		282	an event occurs - for example, you could C<< ->wait >> in your main
		283	program until the user clicks the Quit button in your app, which would C<<
		284	->broadcast >> the "quit" event.
		285
169	Note that condition watchers recurse into the event loop - if you have	286	Note that condition variables recurse into the event loop - if you have
170	two watchers that call C<< ->wait >> in a round-robbin fashion, you	287	two pirces of code that call C<< ->wait >> in a round-robbin fashion, you
171	lose. Therefore, condition watchers are good to export to your caller, but	288	lose. Therefore, condition variables are good to export to your caller, but
172	you should avoid making a blocking wait, at least in callbacks, as this	289	you should avoid making a blocking wait yourself, at least in callbacks,
173	usually asks for trouble.	290	as this asks for trouble.
174		291
175	The watcher has only two methods:	292	This object has two methods:
176		293
177	=over 4	294	=over 4
178		295
179	=item $cv->wait	296	=item $cv->wait
180		297
181	Wait (blocking if necessary) until the C<< ->broadcast >> method has been	298	Wait (blocking if necessary) until the C<< ->broadcast >> method has been
182	called on c<$cv>, while servicing other watchers normally.	299	called on c<$cv>, while servicing other watchers normally.
183		300
184	Not all event models support a blocking wait - some die in that case, so
185	if you are using this from a module, never require a blocking wait, but
186	let the caller decide wether the call will block or not (for example,
187	by coupling condition variables with some kind of request results and
188	supporting callbacks so the caller knows that getting the result will not
189	block, while still suppporting blockign waits if the caller so desires).
190
191	You can only wait once on a condition - additional calls will return	301	You can only wait once on a condition - additional calls will return
192	immediately.	302	immediately.
193		303
		304	Not all event models support a blocking wait - some die in that case
		305	(programs might want to do that to stay interactive), so I<if you are
		306	using this from a module, never require a blocking wait>, but let the
		307	caller decide whether the call will block or not (for example, by coupling
		308	condition variables with some kind of request results and supporting
		309	callbacks so the caller knows that getting the result will not block,
		310	while still suppporting blocking waits if the caller so desires).
		311
		312	Another reason I<never> to C<< ->wait >> in a module is that you cannot
		313	sensibly have two C<< ->wait >>'s in parallel, as that would require
		314	multiple interpreters or coroutines/threads, none of which C<AnyEvent>
		315	can supply (the coroutine-aware backends L<AnyEvent::Impl::CoroEV> and
		316	L<AnyEvent::Impl::CoroEvent> explicitly support concurrent C<< ->wait >>'s
		317	from different coroutines, however).
		318
194	=item $cv->broadcast	319	=item $cv->broadcast
195		320
196	Flag the condition as ready - a running C<< ->wait >> and all further	321	Flag the condition as ready - a running C<< ->wait >> and all further
197	calls to C<wait> will return after this method has been called. If nobody	322	calls to C<wait> will (eventually) return after this method has been
198	is waiting the broadcast will be remembered..	323	called. If nobody is waiting the broadcast will be remembered..
		324
		325	=back
199		326
200	Example:	327	Example:
201		328
202	# wait till the result is ready	329	# wait till the result is ready
203	my $result_ready = AnyEvent->condvar;	330	my $result_ready = AnyEvent->condvar;
204		331
205	# do something such as adding a timer	332	# do something such as adding a timer
206	# or socket watcher the calls $result_ready->broadcast	333	# or socket watcher the calls $result_ready->broadcast
207	# when the "result" is ready.	334	# when the "result" is ready.
		335	# in this case, we simply use a timer:
		336	my $w = AnyEvent->timer (
		337	after => 1,
		338	cb => sub { $result_ready->broadcast },
		339	);
208		340
		341	# this "blocks" (while handling events) till the watcher
		342	# calls broadcast
209	$result_ready->wait;	343	$result_ready->wait;
210		344
211	=back	345	=head1 GLOBAL VARIABLES AND FUNCTIONS
212
213	=head2 SIGNAL WATCHERS
214
215	You can listen for signals using a signal watcher, C<signal> is the signal
216	I<name> without any C<SIG> prefix. Multiple signals events can be clumped
217	together into one callback invocation, and callback invocation might or
218	might not be asynchronous.
219
220	These watchers might use C<%SIG>, so programs overwriting those signals
221	directly will likely not work correctly.
222
223	Example: exit on SIGINT
224
225	my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 });
226
227	=head2 CHILD PROCESS WATCHERS
228
229	You can also listen for the status of a child process specified by the
230	C<pid> argument (or any child if the pid argument is 0). The watcher will
231	trigger as often as status change for the child are received. This works
232	by installing a signal handler for C<SIGCHLD>. The callback will be called with
233	the pid and exit status (as returned by waitpid).
234
235	Example: wait for pid 1333
236
237	my $w = AnyEvent->child (pid => 1333, cb => sub { warn "exit status $?" });
238
239	=head1 GLOBALS
240		346
241	=over 4	347	=over 4
242		348
243	=item $AnyEvent::MODEL	349	=item $AnyEvent::MODEL
244		350
…		…
249	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).	355	AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).
250		356
251	The known classes so far are:	357	The known classes so far are:
252		358
253	AnyEvent::Impl::CoroEV based on Coro::EV, best choice.	359	AnyEvent::Impl::CoroEV based on Coro::EV, best choice.
254	AnyEvent::Impl::EV based on EV (an interface to libev, also best choice).
255	AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.	360	AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
		361	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
256	AnyEvent::Impl::Event based on Event, also second best choice :)	362	AnyEvent::Impl::Event based on Event, second best choice.
257	AnyEvent::Impl::Glib based on Glib, second-best choice.	363	AnyEvent::Impl::Glib based on Glib, third-best choice.
258	AnyEvent::Impl::Tk based on Tk, very bad choice.	364	AnyEvent::Impl::Tk based on Tk, very bad choice.
259	AnyEvent::Impl::Perl pure-perl implementation, inefficient.	365	AnyEvent::Impl::Perl pure-perl implementation, inefficient but portable.
		366	AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
		367	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
		368	AnyEvent::Impl::POE based on POE, not generic enough for full support.
		369
		370	There is no support for WxWidgets, as WxWidgets has no support for
		371	watching file handles. However, you can use WxWidgets through the
		372	POE Adaptor, as POE has a Wx backend that simply polls 20 times per
		373	second, which was considered to be too horrible to even consider for
		374	AnyEvent. Likewise, other POE backends can be used by AnyEvent by using
		375	it's adaptor.
		376
		377	AnyEvent knows about L<Prima> and L<Wx> and will try to use L<POE> when
		378	autodetecting them.
260		379
261	=item AnyEvent::detect	380	=item AnyEvent::detect
262		381
263	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model if	382	Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model
264	necessary. You should only call this function right before you would have	383	if necessary. You should only call this function right before you would
265	created an AnyEvent watcher anyway, that is, very late at runtime.	384	have created an AnyEvent watcher anyway, that is, as late as possible at
		385	runtime.
266		386
267	=back	387	=back
268		388
269	=head1 WHAT TO DO IN A MODULE	389	=head1 WHAT TO DO IN A MODULE
270		390
271	As a module author, you should "use AnyEvent" and call AnyEvent methods	391	As a module author, you should C<use AnyEvent> and call AnyEvent methods
272	freely, but you should not load a specific event module or rely on it.	392	freely, but you should not load a specific event module or rely on it.
273		393
274	Be careful when you create watchers in the module body - Anyevent will	394	Be careful when you create watchers in the module body - AnyEvent will
275	decide which event module to use as soon as the first method is called, so	395	decide which event module to use as soon as the first method is called, so
276	by calling AnyEvent in your module body you force the user of your module	396	by calling AnyEvent in your module body you force the user of your module
277	to load the event module first.	397	to load the event module first.
278		398
		399	Never call C<< ->wait >> on a condition variable unless you I<know> that
		400	the C<< ->broadcast >> method has been called on it already. This is
		401	because it will stall the whole program, and the whole point of using
		402	events is to stay interactive.
		403
		404	It is fine, however, to call C<< ->wait >> when the user of your module
		405	requests it (i.e. if you create a http request object ad have a method
		406	called C<results> that returns the results, it should call C<< ->wait >>
		407	freely, as the user of your module knows what she is doing. always).
		408
279	=head1 WHAT TO DO IN THE MAIN PROGRAM	409	=head1 WHAT TO DO IN THE MAIN PROGRAM
280		410
281	There will always be a single main program - the only place that should	411	There will always be a single main program - the only place that should
282	dictate which event model to use.	412	dictate which event model to use.
283		413
284	If it doesn't care, it can just "use AnyEvent" and use it itself, or not	414	If it doesn't care, it can just "use AnyEvent" and use it itself, or not
285	do anything special and let AnyEvent decide which implementation to chose.	415	do anything special (it does not need to be event-based) and let AnyEvent
		416	decide which implementation to chose if some module relies on it.
286		417
287	If the main program relies on a specific event model (for example, in Gtk2	418	If the main program relies on a specific event model. For example, in
288	programs you have to rely on either Glib or Glib::Event), you should load	419	Gtk2 programs you have to rely on the Glib module. You should load the
289	it before loading AnyEvent or any module that uses it, generally, as early	420	event module before loading AnyEvent or any module that uses it: generally
290	as possible. The reason is that modules might create watchers when they	421	speaking, you should load it as early as possible. The reason is that
291	are loaded, and AnyEvent will decide on the event model to use as soon as	422	modules might create watchers when they are loaded, and AnyEvent will
292	it creates watchers, and it might chose the wrong one unless you load the	423	decide on the event model to use as soon as it creates watchers, and it
293	correct one yourself.	424	might chose the wrong one unless you load the correct one yourself.
294		425
295	You can chose to use a rather inefficient pure-perl implementation by	426	You can chose to use a rather inefficient pure-perl implementation by
296	loading the C<AnyEvent::Impl::Perl> module, but letting AnyEvent chose is	427	loading the C<AnyEvent::Impl::Perl> module, which gives you similar
297	generally better.	428	behaviour everywhere, but letting AnyEvent chose is generally better.
298		429
299	=cut	430	=cut
300		431
301	package AnyEvent;	432	package AnyEvent;
302		433
303	no warnings;	434	no warnings;
304	use strict;	435	use strict;
305		436
306	use Carp;	437	use Carp;
307		438
308	our $VERSION = '3.0';	439	our $VERSION = '3.3';
309	our $MODEL;	440	our $MODEL;
310		441
311	our $AUTOLOAD;	442	our $AUTOLOAD;
312	our @ISA;	443	our @ISA;
313		444
…		…
315		446
316	our @REGISTRY;	447	our @REGISTRY;
317		448
318	my @models = (	449	my @models = (
319	[Coro::EV:: => AnyEvent::Impl::CoroEV::],	450	[Coro::EV:: => AnyEvent::Impl::CoroEV::],
		451	[Coro::Event:: => AnyEvent::Impl::CoroEvent::],
320	[EV:: => AnyEvent::Impl::EV::],	452	[EV:: => AnyEvent::Impl::EV::],
321	[Coro::Event:: => AnyEvent::Impl::CoroEvent::],
322	[Event:: => AnyEvent::Impl::Event::],	453	[Event:: => AnyEvent::Impl::Event::],
323	[Glib:: => AnyEvent::Impl::Glib::],	454	[Glib:: => AnyEvent::Impl::Glib::],
324	[Tk:: => AnyEvent::Impl::Tk::],	455	[Tk:: => AnyEvent::Impl::Tk::],
		456	[Wx:: => AnyEvent::Impl::POE::],
		457	[Prima:: => AnyEvent::Impl::POE::],
325	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],	458	[AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
		459	# everything below here will not be autoprobed as the pureperl backend should work everywhere
		460	[Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy
		461	[Qt:: => AnyEvent::Impl::Qt::], # requires special main program
		462	[POE::Kernel:: => AnyEvent::Impl::POE::], # lasciate ogni speranza
326	);	463	);
327		464
328	our %method = map +($_ => 1), qw(io timer condvar broadcast wait signal one_event DESTROY);	465	our %method = map +($_ => 1), qw(io timer signal child condvar broadcast wait one_event DESTROY);
329		466
330	sub detect() {	467	sub detect() {
331	unless ($MODEL) {	468	unless ($MODEL) {
332	no strict 'refs';	469	no strict 'refs';
333		470
		471	if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) {
		472	my $model = "AnyEvent::Impl::$1";
		473	if (eval "require $model") {
		474	$MODEL = $model;
		475	warn "AnyEvent: loaded model '$model' (forced by \$PERL_ANYEVENT_MODEL), using it.\n" if $verbose > 1;
		476	} else {
		477	warn "AnyEvent: unable to load model '$model' (from \$PERL_ANYEVENT_MODEL):\n$@" if $verbose;
		478	}
		479	}
		480
334	# check for already loaded models	481	# check for already loaded models
		482	unless ($MODEL) {
335	for (@REGISTRY, @models) {	483	for (@REGISTRY, @models) {
336	my ($package, $model) = @$_;	484	my ($package, $model) = @$_;
337	if (${"$package\::VERSION"} > 0) {	485	if (${"$package\::VERSION"} > 0) {
338	if (eval "require $model") {	486	if (eval "require $model") {
339	$MODEL = $model;	487	$MODEL = $model;
340	warn "AnyEvent: found model '$model', using it.\n" if $verbose > 1;	488	warn "AnyEvent: autodetected model '$model', using it.\n" if $verbose > 1;
341	last;	489	last;
		490	}
342	}	491	}
343	}	492	}
344	}
345		493
346	unless ($MODEL) {	494	unless ($MODEL) {
347	# try to load a model	495	# try to load a model
348		496
349	for (@REGISTRY, @models) {	497	for (@REGISTRY, @models) {
350	my ($package, $model) = @$_;	498	my ($package, $model) = @$_;
351	if (eval "require $package"	499	if (eval "require $package"
352	and ${"$package\::VERSION"} > 0	500	and ${"$package\::VERSION"} > 0
353	and eval "require $model") {	501	and eval "require $model") {
354	$MODEL = $model;	502	$MODEL = $model;
355	warn "AnyEvent: autoprobed and loaded model '$model', using it.\n" if $verbose > 1;	503	warn "AnyEvent: autoprobed model '$model', using it.\n" if $verbose > 1;
356	last;	504	last;
		505	}
357	}	506	}
		507
		508	$MODEL
		509	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV (or Coro+EV), Event (or Coro+Event) or Glib.";
358	}	510	}
359
360	$MODEL
361	or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV (or Coro+EV), Event (or Coro+Event), Glib or Tk.";
362	}	511	}
363		512
364	unshift @ISA, $MODEL;	513	unshift @ISA, $MODEL;
365	push @{"$MODEL\::ISA"}, "AnyEvent::Base";	514	push @{"$MODEL\::ISA"}, "AnyEvent::Base";
366	}	515	}
…		…
477	undef $CHLD_W unless keys %PID_CB;	626	undef $CHLD_W unless keys %PID_CB;
478	}	627	}
479		628
480	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE	629	=head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE
481		630
		631	This is an advanced topic that you do not normally need to use AnyEvent in
		632	a module. This section is only of use to event loop authors who want to
		633	provide AnyEvent compatibility.
		634
482	If you need to support another event library which isn't directly	635	If you need to support another event library which isn't directly
483	supported by AnyEvent, you can supply your own interface to it by	636	supported by AnyEvent, you can supply your own interface to it by
484	pushing, before the first watcher gets created, the package name of	637	pushing, before the first watcher gets created, the package name of
485	the event module and the package name of the interface to use onto	638	the event module and the package name of the interface to use onto
486	C<@AnyEvent::REGISTRY>. You can do that before and even without loading	639	C<@AnyEvent::REGISTRY>. You can do that before and even without loading
487	AnyEvent.	640	AnyEvent, so it is reasonably cheap.
488		641
489	Example:	642	Example:
490		643
491	push @AnyEvent::REGISTRY, [urxvt => urxvt::anyevent::];	644	push @AnyEvent::REGISTRY, [urxvt => urxvt::anyevent::];
492		645
493	This tells AnyEvent to (literally) use the C<urxvt::anyevent::>	646	This tells AnyEvent to (literally) use the C<urxvt::anyevent::>
494	package/class when it finds the C<urxvt> package/module is loaded. When	647	package/class when it finds the C<urxvt> package/module is already loaded.
		648
495	AnyEvent is loaded and asked to find a suitable event model, it will	649	When AnyEvent is loaded and asked to find a suitable event model, it
496	first check for the presence of urxvt.	650	will first check for the presence of urxvt by trying to C<use> the
		651	C<urxvt::anyevent> module.
497		652
498	The class should provide implementations for all watcher types (see	653	The class should provide implementations for all watcher types. See
499	L<AnyEvent::Impl::Event> (source code), L<AnyEvent::Impl::Glib>	654	L<AnyEvent::Impl::EV> (source code), L<AnyEvent::Impl::Glib> (Source code)
500	(Source code) and so on for actual examples, use C<perldoc -m	655	and so on for actual examples. Use C<perldoc -m AnyEvent::Impl::Glib> to
501	AnyEvent::Impl::Glib> to see the sources).	656	see the sources.
502		657
		658	If you don't provide C<signal> and C<child> watchers than AnyEvent will
		659	provide suitable (hopefully) replacements.
		660
503	The above isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt)	661	The above example isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt)
504	uses the above line as-is. An interface isn't included in AnyEvent	662	terminal emulator uses the above line as-is. An interface isn't included
505	because it doesn't make sense outside the embedded interpreter inside	663	in AnyEvent because it doesn't make sense outside the embedded interpreter
506	I<rxvt-unicode>, and it is updated and maintained as part of the	664	inside I<rxvt-unicode>, and it is updated and maintained as part of the
507	I<rxvt-unicode> distribution.	665	I<rxvt-unicode> distribution.
508		666
509	I<rxvt-unicode> also cheats a bit by not providing blocking access to	667	I<rxvt-unicode> also cheats a bit by not providing blocking access to
510	condition variables: code blocking while waiting for a condition will	668	condition variables: code blocking while waiting for a condition will
511	C<die>. This still works with most modules/usages, and blocking calls must	669	C<die>. This still works with most modules/usages, and blocking calls must
512	not be in an interactive application, so it makes sense.	670	not be done in an interactive application, so it makes sense.
513		671
514	=head1 ENVIRONMENT VARIABLES	672	=head1 ENVIRONMENT VARIABLES
515		673
516	The following environment variables are used by this module:	674	The following environment variables are used by this module:
517		675
518	C<PERL_ANYEVENT_VERBOSE> when set to C<2> or higher, reports which event	676	=over 4
519	model gets used.
520		677
		678	=item C<PERL_ANYEVENT_VERBOSE>
		679
		680	By default, AnyEvent will be completely silent except in fatal
		681	conditions. You can set this environment variable to make AnyEvent more
		682	talkative.
		683
		684	When set to C<1> or higher, causes AnyEvent to warn about unexpected
		685	conditions, such as not being able to load the event model specified by
		686	C<PERL_ANYEVENT_MODEL>.
		687
		688	When set to C<2> or higher, cause AnyEvent to report to STDERR which event
		689	model it chooses.
		690
		691	=item C<PERL_ANYEVENT_MODEL>
		692
		693	This can be used to specify the event model to be used by AnyEvent, before
		694	autodetection and -probing kicks in. It must be a string consisting
		695	entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended
		696	and the resulting module name is loaded and if the load was successful,
		697	used as event model. If it fails to load AnyEvent will proceed with
		698	autodetection and -probing.
		699
		700	This functionality might change in future versions.
		701
		702	For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you
		703	could start your program like this:
		704
		705	PERL_ANYEVENT_MODEL=Perl perl ...
		706
		707	=back
		708
521	=head1 EXAMPLE	709	=head1 EXAMPLE PROGRAM
522		710
523	The following program uses an io watcher to read data from stdin, a timer	711	The following program uses an I/O watcher to read data from STDIN, a timer
524	to display a message once per second, and a condvar to exit the program	712	to display a message once per second, and a condition variable to quit the
525	when the user enters quit:	713	program when the user enters quit:
526		714
527	use AnyEvent;	715	use AnyEvent;
528		716
529	my $cv = AnyEvent->condvar;	717	my $cv = AnyEvent->condvar;
530		718
531	my $io_watcher = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub {	719	my $io_watcher = AnyEvent->io (
		720	fh => \*STDIN,
		721	poll => 'r',
		722	cb => sub {
532	warn "io event <$_[0]>\n"; # will always output <r>	723	warn "io event <$_[0]>\n"; # will always output <r>
533	chomp (my $input = <STDIN>); # read a line	724	chomp (my $input = <STDIN>); # read a line
534	warn "read: $input\n"; # output what has been read	725	warn "read: $input\n"; # output what has been read
535	$cv->broadcast if $input =~ /^q/i; # quit program if /^q/i	726	$cv->broadcast if $input =~ /^q/i; # quit program if /^q/i
		727	},
536	});	728	);
537		729
538	my $time_watcher; # can only be used once	730	my $time_watcher; # can only be used once
539		731
540	sub new_timer {	732	sub new_timer {
541	$timer = AnyEvent->timer (after => 1, cb => sub {	733	$timer = AnyEvent->timer (after => 1, cb => sub {
…		…
623	$txn->{finished}->wait;	815	$txn->{finished}->wait;
624	return $txn->{result};	816	return $txn->{result};
625		817
626	The actual code goes further and collects all errors (C<die>s, exceptions)	818	The actual code goes further and collects all errors (C<die>s, exceptions)
627	that occured during request processing. The C<result> method detects	819	that occured during request processing. The C<result> method detects
628	wether an exception as thrown (it is stored inside the $txn object)	820	whether an exception as thrown (it is stored inside the $txn object)
629	and just throws the exception, which means connection errors and other	821	and just throws the exception, which means connection errors and other
630	problems get reported tot he code that tries to use the result, not in a	822	problems get reported tot he code that tries to use the result, not in a
631	random callback.	823	random callback.
632		824
633	All of this enables the following usage styles:	825	All of this enables the following usage styles:
634		826
635	1. Blocking:	827	1. Blocking:
636		828
637	my $data = $fcp->client_get ($url);	829	my $data = $fcp->client_get ($url);
638		830
639	2. Blocking, but parallelizing:	831	2. Blocking, but running in parallel:
640		832
641	my @datas = map $_->result,	833	my @datas = map $_->result,
642	map $fcp->txn_client_get ($_),	834	map $fcp->txn_client_get ($_),
643	@urls;	835	@urls;
644		836
645	Both blocking examples work without the module user having to know	837	Both blocking examples work without the module user having to know
646	anything about events.	838	anything about events.
647		839
648	3a. Event-based in a main program, using any support Event module:	840	3a. Event-based in a main program, using any supported event module:
649		841
650	use Event;	842	use EV;
651		843
652	$fcp->txn_client_get ($url)->cb (sub {	844	$fcp->txn_client_get ($url)->cb (sub {
653	my $txn = shift;	845	my $txn = shift;
654	my $data = $txn->result;	846	my $data = $txn->result;
655	...	847	...
656	});	848	});
657		849
658	Event::loop;	850	EV::loop;
659		851
660	3b. The module user could use AnyEvent, too:	852	3b. The module user could use AnyEvent, too:
661		853
662	use AnyEvent;	854	use AnyEvent;
663		855
…		…
668	$quit->broadcast;	860	$quit->broadcast;
669	});	861	});
670		862
671	$quit->wait;	863	$quit->wait;
672		864
		865
		866	=head1 BENCHMARK
		867
		868	To give you an idea of the performance and overheads that AnyEvent adds
		869	over the event loops themselves (and to give you an impression of the
		870	speed of various event loops), here is a benchmark of various supported
		871	event models natively and with anyevent. The benchmark creates a lot of
		872	timers (with a zero timeout) and I/O watchers (watching STDOUT, a pty, to
		873	become writable, which it is), lets them fire exactly once and destroys
		874	them again.
		875
		876	Rewriting the benchmark to use many different sockets instead of using
		877	the same filehandle for all I/O watchers results in a much longer runtime
		878	(socket creation is expensive), but qualitatively the same figures, so it
		879	was not used.
		880
		881	=head2 Explanation of the columns
		882
		883	I<watcher> is the number of event watchers created/destroyed. Since
		884	different event models feature vastly different performances, each event
		885	loop was given a number of watchers so that overall runtime is acceptable
		886	and similar between tested event loop (and keep them from crashing): Glib
		887	would probably take thousands of years if asked to process the same number
		888	of watchers as EV in this benchmark.
		889
		890	I<bytes> is the number of bytes (as measured by the resident set size,
		891	RSS) consumed by each watcher. This method of measuring captures both C
		892	and Perl-based overheads.
		893
		894	I<create> is the time, in microseconds (millionths of seconds), that it
		895	takes to create a single watcher. The callback is a closure shared between
		896	all watchers, to avoid adding memory overhead. That means closure creation
		897	and memory usage is not included in the figures.
		898
		899	I<invoke> is the time, in microseconds, used to invoke a simple
		900	callback. The callback simply counts down a Perl variable and after it was
		901	invoked "watcher" times, it would C<< ->broadcast >> a condvar once to
		902	signal the end of this phase.
		903
		904	I<destroy> is the time, in microseconds, that it takes to destroy a single
		905	watcher.
		906
		907	=head2 Results
		908
		909	name watchers bytes create invoke destroy comment
		910	EV/EV 400000 244 0.56 0.46 0.31 EV native interface
		911	EV/Any 100000 610 3.52 0.91 0.75 EV + AnyEvent watchers
		912	CoroEV/Any 100000 610 3.49 0.92 0.75 coroutines + Coro::Signal
		913	Perl/Any 100000 513 4.91 0.92 1.15 pure perl implementation
		914	Event/Event 16000 523 28.05 21.38 0.86 Event native interface
		915	Event/Any 16000 943 34.43 20.48 1.39 Event + AnyEvent watchers
		916	Glib/Any 16000 1357 96.99 12.55 55.51 quadratic behaviour
		917	Tk/Any 2000 1855 27.01 66.61 14.03 SEGV with >> 2000 watchers
		918	POE/Event 2000 6644 108.15 768.19 14.33 via POE::Loop::Event
		919	POE/Select 2000 6343 94.69 807.65 562.69 via POE::Loop::Select
		920
		921	=head2 Discussion
		922
		923	The benchmark does I<not> measure scalability of the event loop very
		924	well. For example, a select-based event loop (such as the pure perl one)
		925	can never compete with an event loop that uses epoll when the number of
		926	file descriptors grows high. In this benchmark, all events become ready at
		927	the same time, so select/poll-based implementations get an unnatural speed
		928	boost.
		929
		930	C<EV> is the sole leader regarding speed and memory use, which are both
		931	maximal/minimal, respectively. Even when going through AnyEvent, there are
		932	only two event loops that use slightly less memory (the C<Event> module
		933	natively and the pure perl backend), and no faster event models, not even
		934	C<Event> natively.
		935
		936	The pure perl implementation is hit in a few sweet spots (both the
		937	zero timeout and the use of a single fd hit optimisations in the perl
		938	interpreter and the backend itself, and all watchers become ready at the
		939	same time). Nevertheless this shows that it adds very little overhead in
		940	itself. Like any select-based backend its performance becomes really bad
		941	with lots of file descriptors (and few of them active), of course, but
		942	this was not subject of this benchmark.
		943
		944	The C<Event> module has a relatively high setup and callback invocation cost,
		945	but overall scores on the third place.
		946
		947	C<Glib>'s memory usage is quite a bit bit higher, but it features a
		948	faster callback invocation and overall ends up in the same class as
		949	C<Event>. However, Glib scales extremely badly, doubling the number of
		950	watchers increases the processing time by more than a factor of four,
		951	making it completely unusable when using larger numbers of watchers
		952	(note that only a single file descriptor was used in the benchmark, so
		953	inefficiencies of C<poll> do not account for this).
		954
		955	The C<Tk> adaptor works relatively well. The fact that it crashes with
		956	more than 2000 watchers is a big setback, however, as correctness takes
		957	precedence over speed. Nevertheless, its performance is surprising, as the
		958	file descriptor is dup()ed for each watcher. This shows that the dup()
		959	employed by some adaptors is not a big performance issue (it does incur a
		960	hidden memory cost inside the kernel, though, that is not reflected in the
		961	figures above).
		962
		963	C<POE>, regardless of underlying event loop (wether using its pure perl
		964	select-based backend or the Event module) shows abysmal performance and
		965	memory usage: Watchers use almost 30 times as much memory as EV watchers,
		966	and 10 times as much memory as both Event or EV via AnyEvent. Watcher
		967	invocation is almost 900 times slower than with AnyEvent's pure perl
		968	implementation. The design of the POE adaptor class in AnyEvent can not
		969	really account for this, as session creation overhead is small compared
		970	to execution of the state machine, which is coded pretty optimally within
		971	L<AnyEvent::Impl::POE>. POE simply seems to be abysmally slow.
		972
		973	=head2 Summary
		974
		975	Using EV through AnyEvent is faster than any other event loop, but most
		976	event loops have acceptable performance with or without AnyEvent.
		977
		978	The overhead AnyEvent adds is usually much smaller than the overhead of
		979	the actual event loop, only with extremely fast event loops such as the EV
		980	adds AnyEvent significant overhead.
		981
		982	And you should simply avoid POE like the plague if you want performance or
		983	reasonable memory usage.
		984
		985
		986	=head1 FORK
		987
		988	Most event libraries are not fork-safe. The ones who are usually are
		989	because they are so inefficient. Only L<EV> is fully fork-aware.
		990
		991	If you have to fork, you must either do so I<before> creating your first
		992	watcher OR you must not use AnyEvent at all in the child.
		993
		994
		995	=head1 SECURITY CONSIDERATIONS
		996
		997	AnyEvent can be forced to load any event model via
		998	$ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used to
		999	execute arbitrary code or directly gain access, it can easily be used to
		1000	make the program hang or malfunction in subtle ways, as AnyEvent watchers
		1001	will not be active when the program uses a different event model than
		1002	specified in the variable.
		1003
		1004	You can make AnyEvent completely ignore this variable by deleting it
		1005	before the first watcher gets created, e.g. with a C<BEGIN> block:
		1006
		1007	BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} }
		1008
		1009	use AnyEvent;
		1010
		1011
673	=head1 SEE ALSO	1012	=head1 SEE ALSO
674		1013
675	Event modules: L<Coro::Event>, L<Coro>, L<Event>, L<Glib::Event>, L<Glib>.	1014	Event modules: L<Coro::EV>, L<EV>, L<EV::Glib>, L<Glib::EV>,
		1015	L<Coro::Event>, L<Event>, L<Glib::Event>, L<Glib>, L<Coro>, L<Tk>,
		1016	L<Event::Lib>, L<Qt>, L<POE>.
676		1017
		1018	Implementations: L<AnyEvent::Impl::CoroEV>, L<AnyEvent::Impl::EV>,
677	Implementations: L<AnyEvent::Impl::Coro>, L<AnyEvent::Impl::Event>, L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>.	1019	L<AnyEvent::Impl::CoroEvent>, L<AnyEvent::Impl::Event>, L<AnyEvent::Impl::Glib>,
		1020	L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, L<AnyEvent::Impl::EventLib>,
		1021	L<AnyEvent::Impl::Qt>, L<AnyEvent::Impl::POE>.
678		1022
679	Nontrivial usage example: L<Net::FCP>.	1023	Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>.
680		1024
681	=head1	1025
		1026	=head1 AUTHOR
		1027
		1028	Marc Lehmann <schmorp@schmorp.de>
		1029	http://home.schmorp.de/
682		1030
683	=cut	1031	=cut
684		1032
685	1	1033	1
686		1034

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.44 by root, Mon Apr 7 19:42:18 2008 UTC vs. Revision 1.80 by root, Fri Apr 25 09:11:59 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.44 by root, Mon Apr 7 19:42:18 2008 UTC vs.
Revision 1.80 by root, Fri Apr 25 09:11:59 2008 UTC