[ViewVC] Diff of: cvs/EV/EV.pm

Comparing EV/EV.pm (file contents):
Revision 1.31 by root, Thu Nov 8 02:21:02 2007 UTC vs.
Revision 1.92 by root, Sun May 18 10:45:36 2008 UTC

…		…
10		10
11	my $w = EV::timer 2, 0, sub {	11	my $w = EV::timer 2, 0, sub {
12	warn "is called after 2s";	12	warn "is called after 2s";
13	};	13	};
14		14
15	my $w = EV::timer 2, 1, sub {	15	my $w = EV::timer 2, 2, sub {
16	warn "is called roughly every 2s (repeat = 1)";	16	warn "is called roughly every 2s (repeat = 2)";
17	};	17	};
18		18
19	undef $w; # destroy event watcher again	19	undef $w; # destroy event watcher again
20		20
21	my $w = EV::periodic 0, 60, 0, sub {	21	my $w = EV::periodic 0, 60, 0, sub {
…		…
23	};	23	};
24		24
25	# IO	25	# IO
26		26
27	my $w = EV::io *STDIN, EV::READ, sub {	27	my $w = EV::io *STDIN, EV::READ, sub {
28	my ($w, $revents) = @_; # all callbacks get the watcher object and event mask	28	my ($w, $revents) = @_; # all callbacks receive the watcher and event mask
29	warn "stdin is readable, you entered: ", <STDIN>;	29	warn "stdin is readable, you entered: ", <STDIN>;
30	};	30	};
31		31
32	# SIGNALS	32	# SIGNALS
33		33
34	my $w = EV::signal 'QUIT', sub {	34	my $w = EV::signal 'QUIT', sub {
35	warn "sigquit received\n";	35	warn "sigquit received\n";
36	};	36	};
37		37
38	my $w = EV::signal 3, sub {	38	# CHILD/PID STATUS CHANGES
39	warn "sigquit received (this is GNU/Linux, right?)\n";	39
		40	my $w = EV::child 666, 0, sub {
		41	my ($w, $revents) = @_;
		42	my $status = $w->rstatus;
40	};	43	};
41		44
42	# CHILD/PID STATUS CHANGES	45	# STAT CHANGES
43		46	my $w = EV::stat "/etc/passwd", 10, sub {
44	my $w = EV::child 666, sub {
45	my ($w, $revents) = @_;	47	my ($w, $revents) = @_;
46	# my $pid = $w->rpid;	48	warn $w->path, " has changed somehow.\n";
47	my $status = $w->rstatus;
48	};	49	};
49		50
50	# MAINLOOP	51	# MAINLOOP
51	EV::loop; # loop until EV::loop_done is called	52	EV::loop; # loop until EV::unloop is called or all watchers stop
52	EV::loop EV::LOOP_ONESHOT; # block until at least one event could be handled	53	EV::loop EV::LOOP_ONESHOT; # block until at least one event could be handled
53	EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block	54	EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block
54		55
55	=head1 DESCRIPTION	56	=head1 DESCRIPTION
56		57
57	This module provides an interface to libev	58	This module provides an interface to libev
58	(L<http://software.schmorp.de/pkg/libev.html>).	59	(L<http://software.schmorp.de/pkg/libev.html>). While the documentation
		60	below is comprehensive, one might also consult the documentation of libev
		61	itself (L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>) for more
		62	subtle details on watcher semantics or some discussion on the available
		63	backends, or how to force a specific backend with C<LIBEV_FLAGS>, or just
		64	about in any case because it has much more detailed information.
		65
		66	This module is very fast and scalable. It is actually so fast that you
		67	can use it through the L<AnyEvent> module, stay portable to other event
		68	loops (if you don't rely on any watcher types not available through it)
		69	and still be faster than with any other event loop currently supported in
		70	Perl.
59		71
60	=cut	72	=cut
61		73
62	package EV;	74	package EV;
63		75
64	use strict;	76	use strict;
65		77
66	BEGIN {	78	BEGIN {
67	our $VERSION = '0.51';	79	our $VERSION = '3.33';
68	use XSLoader;	80	use XSLoader;
69	XSLoader::load "EV", $VERSION;	81	XSLoader::load "EV", $VERSION;
70	}	82	}
71		83
72	@EV::Io::ISA =	84	@EV::IO::ISA =
73	@EV::Timer::ISA =	85	@EV::Timer::ISA =
74	@EV::Periodic::ISA =	86	@EV::Periodic::ISA =
75	@EV::Signal::ISA =	87	@EV::Signal::ISA =
		88	@EV::Child::ISA =
		89	@EV::Stat::ISA =
76	@EV::Idle::ISA =	90	@EV::Idle::ISA =
77	@EV::Prepare::ISA =	91	@EV::Prepare::ISA =
78	@EV::Check::ISA =	92	@EV::Check::ISA =
79	@EV::Child::ISA = "EV::Watcher";	93	@EV::Embed::ISA =
		94	@EV::Fork::ISA =
		95	@EV::Async::ISA =
		96	"EV::Watcher";
		97
		98	@EV::Loop::Default::ISA = "EV::Loop";
		99
		100	=head1 EVENT LOOPS
		101
		102	EV supports multiple event loops: There is a single "default event loop"
		103	that can handle everything including signals and child watchers, and any
		104	number of "dynamic event loops" that can use different backends (with
		105	various limitations), but no child and signal watchers.
		106
		107	You do not have to do anything to create the default event loop: When
		108	the module is loaded a suitable backend is selected on the premise of
		109	selecting a working backend (which for example rules out kqueue on most
		110	BSDs). Modules should, unless they have "special needs" always use the
		111	default loop as this is fastest (perl-wise), best supported by other
		112	modules (e.g. AnyEvent or Coro) and most portable event loop.
		113
		114	For specific programs you can create additional event loops dynamically.
		115
		116	=over 4
		117
		118	=item $loop = new EV::loop [$flags]
		119
		120	Create a new event loop as per the specified flags. Please refer to the
		121	C<ev_loop_new ()> function description in the libev documentation
		122	(L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#GLOBAL_FUNCTIONS>)
		123	for more info.
		124
		125	The loop will automatically be destroyed when it is no longer referenced
		126	by any watcher and the loop object goes out of scope.
		127
		128	Using C<EV::FLAG_FORKCHECK> is recommended, as only the default event loop
		129	is protected by this module.
		130
		131	=item $loop->loop_fork
		132
		133	Must be called after a fork in the child, before entering or continuing
		134	the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls
		135	this fucntion automatically, at some performance loss (refer to the libev
		136	documentation).
		137
		138	=item $loop = EV::default_loop [$flags]
		139
		140	Return the default loop (which is a singleton object).
		141
		142	=back
		143
80		144
81	=head1 BASIC INTERFACE	145	=head1 BASIC INTERFACE
82		146
83	=over 4	147	=over 4
84		148
85	=item $EV::DIED	149	=item $EV::DIED
86		150
87	Must contain a reference to a function that is called when a callback	151	Must contain a reference to a function that is called when a callback
88	throws an exception (with $@ containing thr error). The default prints an	152	throws an exception (with $@ containing the error). The default prints an
89	informative message and continues.	153	informative message and continues.
90		154
91	If this callback throws an exception it will be silently ignored.	155	If this callback throws an exception it will be silently ignored.
92		156
		157	=item $flags = EV::supported_backends
		158
		159	=item $flags = EV::recommended_backends
		160
		161	=item $flags = EV::embeddable_backends
		162
		163	Returns the set (see C<EV::BACKEND_*> flags) of backends supported by this
		164	instance of EV, the set of recommended backends (supposed to be good) for
		165	this platform and the set of embeddable backends (see EMBED WATCHERS).
		166
		167	=item EV::sleep $seconds
		168
		169	Block the process for the given number of (fractional) seconds.
		170
93	=item $time = EV::time	171	=item $time = EV::time
94		172
95	Returns the current time in (fractional) seconds since the epoch.	173	Returns the current time in (fractional) seconds since the epoch.
96		174
97	=item $time = EV::now	175	=item $time = EV::now
		176
		177	=item $time = $loop->now
98		178
99	Returns the time the last event loop iteration has been started. This	179	Returns the time the last event loop iteration has been started. This
100	is the time that (relative) timers are based on, and refering to it is	180	is the time that (relative) timers are based on, and refering to it is
101	usually faster then calling EV::time.	181	usually faster then calling EV::time.
102		182
103	=item $method = EV::ev_method	183	=item $backend = EV::backend
		184
		185	=item $backend = $loop->backend
104		186
105	Returns an integer describing the backend used by libev (EV::METHOD_SELECT	187	Returns an integer describing the backend used by libev (EV::METHOD_SELECT
106	or EV::METHOD_EPOLL).	188	or EV::METHOD_EPOLL).
107		189
108	=item EV::loop [$flags]	190	=item EV::loop [$flags]
109		191
		192	=item $loop->loop ([$flags])
		193
110	Begin checking for events and calling callbacks. It returns when a	194	Begin checking for events and calling callbacks. It returns when a
111	callback calls EV::loop_done.	195	callback calls EV::unloop.
112		196
113	The $flags argument can be one of the following:	197	The $flags argument can be one of the following:
114		198
115	0 as above	199	0 as above
116	EV::LOOP_ONESHOT block at most once (wait, but do not loop)	200	EV::LOOP_ONESHOT block at most once (wait, but do not loop)
117	EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait)	201	EV::LOOP_NONBLOCK do not block at all (fetch/handle events but do not wait)
118		202
119	=item EV::loop_done [$how]	203	=item EV::unloop [$how]
120		204
		205	=item $loop->unloop ([$how])
		206
121	When called with no arguments or an argument of 1, makes the innermost	207	When called with no arguments or an argument of EV::UNLOOP_ONE, makes the
122	call to EV::loop return.	208	innermost call to EV::loop return.
123		209
124	When called with an agrument of 2, all calls to EV::loop will return as	210	When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as
125	fast as possible.	211	fast as possible.
126		212
127	=back	213	=item $count = EV::loop_count
128		214
129	=head2 WATCHER	215	=item $count = $loop->loop_count
		216
		217	Return the number of times the event loop has polled for new
		218	events. Sometiems useful as a generation counter.
		219
		220	=item EV::once $fh_or_undef, $events, $timeout, $cb->($revents)
		221
		222	=item $loop->once ($fh_or_undef, $events, $timeout, $cb->($revents))
		223
		224	This function rolls together an I/O and a timer watcher for a single
		225	one-shot event without the need for managing a watcher object.
		226
		227	If C<$fh_or_undef> is a filehandle or file descriptor, then C<$events>
		228	must be a bitset containing either C<EV::READ>, C<EV::WRITE> or C<EV::READ
		229	\| EV::WRITE>, indicating the type of I/O event you want to wait for. If
		230	you do not want to wait for some I/O event, specify C<undef> for
		231	C<$fh_or_undef> and C<0> for C<$events>).
		232
		233	If timeout is C<undef> or negative, then there will be no
		234	timeout. Otherwise a EV::timer with this value will be started.
		235
		236	When an error occurs or either the timeout or I/O watcher triggers, then
		237	the callback will be called with the received event set (in general
		238	you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>,
		239	C<EV::WRITE> and C<EV::TIMEOUT>).
		240
		241	EV::once doesn't return anything: the watchers stay active till either
		242	of them triggers, then they will be stopped and freed, and the callback
		243	invoked.
		244
		245	=item EV::feed_fd_event ($fd, $revents)
		246
		247	=item $loop->feed_fd_event ($fd, $revents)
		248
		249	Feed an event on a file descriptor into EV. EV will react to this call as
		250	if the readyness notifications specified by C<$revents> (a combination of
		251	C<EV::READ> and C<EV::WRITE>) happened on the file descriptor C<$fd>.
		252
		253	=item EV::feed_signal_event ($signal)
		254
		255	Feed a signal event into EV. EV will react to this call as if the signal
		256	specified by C<$signal> had occured.
		257
		258	=item EV::set_io_collect_interval $time
		259
		260	=item $loop->set_io_collect_interval ($time)
		261
		262	=item EV::set_timeout_collect_interval $time
		263
		264	=item $loop->set_timeout_collect_interval ($time)
		265
		266	These advanced functions set the minimum block interval when polling for I/O events and the minimum
		267	wait interval for timer events. See the libev documentation at
		268	L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP> for
		269	a more detailed discussion.
		270
		271	=back
		272
		273
		274	=head1 WATCHER OBJECTS
130		275
131	A watcher is an object that gets created to record your interest in some	276	A watcher is an object that gets created to record your interest in some
132	event. For instance, if you want to wait for STDIN to become readable, you	277	event. For instance, if you want to wait for STDIN to become readable, you
133	would create an EV::io watcher for that:	278	would create an EV::io watcher for that:
134		279
135	my $watcher = EV::io *STDIN, EV::READ, sub {	280	my $watcher = EV::io *STDIN, EV::READ, sub {
136	my ($watcher, $revents) = @_;	281	my ($watcher, $revents) = @_;
137	warn "yeah, STDIN should not be readable without blocking!\n"	282	warn "yeah, STDIN should now be readable without blocking!\n"
138	};	283	};
139		284
140	All watchers can be active (waiting for events) or inactive (paused). Only	285	All watchers can be active (waiting for events) or inactive (paused). Only
141	active watchers will have their callbacks invoked. All callbacks will be	286	active watchers will have their callbacks invoked. All callbacks will be
142	called with at least two arguments: the watcher and a bitmask of received	287	called with at least two arguments: the watcher and a bitmask of received
143	events.	288	events.
144		289
145	Each watcher type has its associated bit in revents, so you can use the	290	Each watcher type has its associated bit in revents, so you can use the
146	same callback for multiple watchers. The event mask is named after the	291	same callback for multiple watchers. The event mask is named after the
147	type, i..e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE,	292	type, i..e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE,
148	EV::periodic sets EV::PERIODIC and so on, with the exception of IO events	293	EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events
149	(which can set both EV::READ and EV::WRITE bits), and EV::timer (which	294	(which can set both EV::READ and EV::WRITE bits), and EV::timer (which
150	uses EV::TIMEOUT).	295	uses EV::TIMEOUT).
151		296
152	In the rare case where one wants to create a watcher but not start it at	297	In the rare case where one wants to create a watcher but not start it at
153	the same time, each constructor has a variant with a trailing C<_ns> in	298	the same time, each constructor has a variant with a trailing C<_ns> in
…		…
159		304
160	Also, all methods changing some aspect of a watcher (->set, ->priority,	305	Also, all methods changing some aspect of a watcher (->set, ->priority,
161	->fh and so on) automatically stop and start it again if it is active,	306	->fh and so on) automatically stop and start it again if it is active,
162	which means pending events get lost.	307	which means pending events get lost.
163		308
164	=head2 WATCHER TYPES	309	=head2 COMMON WATCHER METHODS
165		310
166	Now lets move to the existing watcher types and asociated methods.	311	This section lists methods common to all watchers.
167
168	The following methods are available for all watchers. Then followes a
169	description of each watcher constructor (EV::io, EV::timer, EV::periodic,
170	EV::signal, EV::child, EV::idle, EV::prepare and EV::check), followed by
171	any type-specific methods (if any).
172		312
173	=over 4	313	=over 4
174		314
175	=item $w->start	315	=item $w->start
176		316
…		…
180		320
181	=item $w->stop	321	=item $w->stop
182		322
183	Stop a watcher if it is active. Also clear any pending events (events that	323	Stop a watcher if it is active. Also clear any pending events (events that
184	have been received but that didn't yet result in a callback invocation),	324	have been received but that didn't yet result in a callback invocation),
185	regardless of wether the watcher was active or not.	325	regardless of whether the watcher was active or not.
186		326
187	=item $bool = $w->is_active	327	=item $bool = $w->is_active
188		328
189	Returns true if the watcher is active, false otherwise.	329	Returns true if the watcher is active, false otherwise.
190		330
…		…
215	watchers with higher priority will be invoked first. The valid range of	355	watchers with higher priority will be invoked first. The valid range of
216	priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default	356	priorities lies between EV::MAXPRI (default 2) and EV::MINPRI (default
217	-2). If the priority is outside this range it will automatically be	357	-2). If the priority is outside this range it will automatically be
218	normalised to the nearest valid priority.	358	normalised to the nearest valid priority.
219		359
220	The default priority of any newly-created weatcher is 0.	360	The default priority of any newly-created watcher is 0.
221		361
		362	Note that the priority semantics have not yet been fleshed out and are
		363	subject to almost certain change.
		364
222	=item $w->trigger ($revents)	365	=item $w->invoke ($revents)
223		366
224	Call the callback now with the given event mask.	367	Call the callback now with the given event mask.
225		368
		369	=item $w->feed_event ($revents)
		370
		371	Feed some events on this watcher into EV. EV will react to this call as if
		372	the watcher had received the given C<$revents> mask.
		373
		374	=item $revents = $w->clear_pending
		375
		376	If the watcher is pending, this function clears its pending status and
		377	returns its C<$revents> bitset (as if its callback was invoked). If the
		378	watcher isn't pending it does nothing and returns C<0>.
		379
		380	=item $previous_state = $w->keepalive ($bool)
		381
		382	Normally, C<EV::loop> will return when there are no active watchers
		383	(which is a "deadlock" because no progress can be made anymore). This is
		384	convinient because it allows you to start your watchers (and your jobs),
		385	call C<EV::loop> once and when it returns you know that all your jobs are
		386	finished (or they forgot to register some watchers for their task :).
		387
		388	Sometimes, however, this gets in your way, for example when the module
		389	that calls C<EV::loop> (usually the main program) is not the same module
		390	as a long-living watcher (for example a DNS client module written by
		391	somebody else even). Then you might want any outstanding requests to be
		392	handled, but you would not want to keep C<EV::loop> from returning just
		393	because you happen to have this long-running UDP port watcher.
		394
		395	In this case you can clear the keepalive status, which means that even
		396	though your watcher is active, it won't keep C<EV::loop> from returning.
		397
		398	The initial value for keepalive is true (enabled), and you cna change it
		399	any time.
		400
		401	Example: Register an I/O watcher for some UDP socket but do not keep the
		402	event loop from running just because of that watcher.
		403
		404	my $udp_socket = ...
		405	my $udp_watcher = EV::io $udp_socket, EV::READ, sub { ... };
		406	$1000udp_watcher->keepalive (0);
		407
		408	=item $loop = $w->loop
		409
		410	Return the loop that this watcher is attached to.
		411
		412	=back
		413
		414
		415	=head1 WATCHER TYPES
		416
		417	Each of the following subsections describes a single watcher type.
		418
		419	=head3 I/O WATCHERS - is this file descriptor readable or writable?
		420
		421	=over 4
226		422
227	=item $w = EV::io $fileno_or_fh, $eventmask, $callback	423	=item $w = EV::io $fileno_or_fh, $eventmask, $callback
228		424
229	=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback	425	=item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback
230		426
		427	=item $w = $loop->io ($fileno_or_fh, $eventmask, $callback)
		428
		429	=item $w = $loop->io_ns ($fileno_or_fh, $eventmask, $callback)
		430
231	As long as the returned watcher object is alive, call the C<$callback>	431	As long as the returned watcher object is alive, call the C<$callback>
232	when the events specified in C<$eventmask>.	432	when at least one of events specified in C<$eventmask> occurs.
233		433
234	The $eventmask can be one or more of these constants ORed together:	434	The $eventmask can be one or more of these constants ORed together:
235		435
236	EV::READ wait until read() wouldn't block anymore	436	EV::READ wait until read() wouldn't block anymore
237	EV::WRITE wait until write() wouldn't block anymore	437	EV::WRITE wait until write() wouldn't block anymore
…		…
253		453
254	=item $old_eventmask = $w->events ($new_eventmask)	454	=item $old_eventmask = $w->events ($new_eventmask)
255		455
256	Returns the previously set event mask and optionally set a new one.	456	Returns the previously set event mask and optionally set a new one.
257		457
		458	=back
		459
		460
		461	=head3 TIMER WATCHERS - relative and optionally repeating timeouts
		462
		463	=over 4
258		464
259	=item $w = EV::timer $after, $repeat, $callback	465	=item $w = EV::timer $after, $repeat, $callback
260		466
261	=item $w = EV::timer_ns $after, $repeat, $callback	467	=item $w = EV::timer_ns $after, $repeat, $callback
262		468
263	Calls the callback after C<$after> seconds. If C<$repeat> is non-zero,	469	=item $w = $loop->timer ($after, $repeat, $callback)
264	the timer will be restarted (with the $repeat value as $after) after the	470
265	callback returns.	471	=item $w = $loop->timer_ns ($after, $repeat, $callback)
		472
		473	Calls the callback after C<$after> seconds (which may be fractional). If
		474	C<$repeat> is non-zero, the timer will be restarted (with the $repeat
		475	value as $after) after the callback returns.
266		476
267	This means that the callback would be called roughly after C<$after>	477	This means that the callback would be called roughly after C<$after>
268	seconds, and then every C<$repeat> seconds. "Roughly" because the time of	478	seconds, and then every C<$repeat> seconds. The timer does his best not
269	callback processing is not taken into account, so the timer will slowly	479	to drift, but it will not invoke the timer more often then once per event
270	drift. If that isn't acceptable, look at EV::periodic.	480	loop iteration, and might drift in other cases. If that isn't acceptable,
		481	look at EV::periodic, which can provide long-term stable timers.
271		482
272	The timer is based on a monotonic clock, that is if somebody is sitting	483	The timer is based on a monotonic clock, that is, if somebody is sitting
273	in front of the machine while the timer is running and changes the system	484	in front of the machine while the timer is running and changes the system
274	clock, the timer will nevertheless run (roughly) the same time.	485	clock, the timer will nevertheless run (roughly) the same time.
275		486
276	The C<timer_ns> variant doesn't start (activate) the newly created watcher.	487	The C<timer_ns> variant doesn't start (activate) the newly created watcher.
277		488
278	=item $w->set ($after, $repeat)	489	=item $w->set ($after, $repeat)
279		490
280	Reconfigures the watcher, see the constructor above for details. Can be at	491	Reconfigures the watcher, see the constructor above for details. Can be called at
281	any time.	492	any time.
282		493
283	=item $w->again	494	=item $w->again
284		495
285	Similar to the C<start> method, but has special semantics for repeating timers:	496	Similar to the C<start> method, but has special semantics for repeating timers:
		497
		498	If the timer is active and non-repeating, it will be stopped.
286		499
287	If the timer is active and repeating, reset the timeout to occur	500	If the timer is active and repeating, reset the timeout to occur
288	C<$repeat> seconds after now.	501	C<$repeat> seconds after now.
289		502
290	If the timer is active and non-repeating, it will be stopped.
291
292	If the timer is in active and repeating, start it.	503	If the timer is inactive and repeating, start it using the repeat value.
293		504
294	Otherwise do nothing.	505	Otherwise do nothing.
295		506
296	This behaviour is useful when you have a timeout for some IO	507	This behaviour is useful when you have a timeout for some IO
297	operation. You create a timer object with the same value for C<$after> and	508	operation. You create a timer object with the same value for C<$after> and
298	C<$repeat>, and then, in the read/write watcher, run the C<again> method	509	C<$repeat>, and then, in the read/write watcher, run the C<again> method
299	on the timeout.	510	on the timeout.
300		511
		512	=back
		513
		514
		515	=head3 PERIODIC WATCHERS - to cron or not to cron?
		516
		517	=over 4
301		518
302	=item $w = EV::periodic $at, $interval, $reschedule_cb, $callback	519	=item $w = EV::periodic $at, $interval, $reschedule_cb, $callback
303		520
304	=item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback	521	=item $w = EV::periodic_ns $at, $interval, $reschedule_cb, $callback
		522
		523	=item $w = $loop->periodic ($at, $interval, $reschedule_cb, $callback)
		524
		525	=item $w = $loop->periodic_ns ($at, $interval, $reschedule_cb, $callback)
305		526
306	Similar to EV::timer, but is not based on relative timeouts but on	527	Similar to EV::timer, but is not based on relative timeouts but on
307	absolute times. Apart from creating "simple" timers that trigger "at" the	528	absolute times. Apart from creating "simple" timers that trigger "at" the
308	specified time, it can also be used for non-drifting absolute timers and	529	specified time, it can also be used for non-drifting absolute timers and
309	more complex, cron-like, setups that are not adversely affected by time	530	more complex, cron-like, setups that are not adversely affected by time
…		…
319	This time simply fires at the wallclock time C<$at> and doesn't repeat. It	540	This time simply fires at the wallclock time C<$at> and doesn't repeat. It
320	will not adjust when a time jump occurs, that is, if it is to be run	541	will not adjust when a time jump occurs, that is, if it is to be run
321	at January 1st 2011 then it will run when the system time reaches or	542	at January 1st 2011 then it will run when the system time reaches or
322	surpasses this time.	543	surpasses this time.
323		544
324	=item * non-repeating interval timer ($interval > 0, $reschedule_cb = 0)	545	=item * repeating interval timer ($interval > 0, $reschedule_cb = 0)
325		546
326	In this mode the watcher will always be scheduled to time out at the	547	In this mode the watcher will always be scheduled to time out at the
327	next C<$at + N * $interval> time (for some integer N) and then repeat,	548	next C<$at + N * $interval> time (for some integer N) and then repeat,
328	regardless of any time jumps.	549	regardless of any time jumps.
329		550
…		…
341	possible time where C<$time = $at (mod $interval)>, regardless of any time	562	possible time where C<$time = $at (mod $interval)>, regardless of any time
342	jumps.	563	jumps.
343		564
344	=item * manual reschedule mode ($reschedule_cb = coderef)	565	=item * manual reschedule mode ($reschedule_cb = coderef)
345		566
346	In this mode $interval and $at are both being ignored. Instead, each time	567	In this mode $interval and $at are both being ignored. Instead, each
347	the periodic watcher gets scheduled, the first callback ($reschedule_cb)	568	time the periodic watcher gets scheduled, the reschedule callback
348	will be called with the watcher as first, and the current time as second	569	($reschedule_cb) will be called with the watcher as first, and the current
349	argument.	570	time as second argument.
350		571
351	I<This callback MUST NOT stop or destroy this or any other periodic	572	I<This callback MUST NOT stop or destroy this or any other periodic
352	watcher, ever>. If you need to stop it, return 1e30 and stop it	573	watcher, ever>. If you need to stop it, return 1e30 and stop it
353	afterwards.	574	afterwards.
354		575
…		…
377		598
378	The C<periodic_ns> variant doesn't start (activate) the newly created watcher.	599	The C<periodic_ns> variant doesn't start (activate) the newly created watcher.
379		600
380	=item $w->set ($at, $interval, $reschedule_cb)	601	=item $w->set ($at, $interval, $reschedule_cb)
381		602
382	Reconfigures the watcher, see the constructor above for details. Can be at	603	Reconfigures the watcher, see the constructor above for details. Can be called at
383	any time.	604	any time.
384		605
385	=item $w->again	606	=item $w->again
386		607
387	Simply stops and starts the watcher again.	608	Simply stops and starts the watcher again.
388		609
		610	=item $time = $w->at
		611
		612	Return the time that the watcher is expected to trigger next.
		613
		614	=back
		615
		616
		617	=head3 SIGNAL WATCHERS - signal me when a signal gets signalled!
		618
		619	=over 4
389		620
390	=item $w = EV::signal $signal, $callback	621	=item $w = EV::signal $signal, $callback
391		622
392	=item $w = EV::signal_ns $signal, $callback	623	=item $w = EV::signal_ns $signal, $callback
393		624
394	Call the callback when $signal is received (the signal can be specified	625	Call the callback when $signal is received (the signal can be specified by
395	by number or by name, just as with kill or %SIG).	626	number or by name, just as with C<kill> or C<%SIG>).
396		627
397	EV will grab the signal for the process (the kernel only allows one	628	EV will grab the signal for the process (the kernel only allows one
398	component to receive a signal at a time) when you start a signal watcher,	629	component to receive a signal at a time) when you start a signal watcher,
399	and removes it again when you stop it. Perl does the same when you	630	and removes it again when you stop it. Perl does the same when you
400	add/remove callbacks to %SIG, so watch out.	631	add/remove callbacks to C<%SIG>, so watch out.
401		632
402	You can have as many signal watchers per signal as you want.	633	You can have as many signal watchers per signal as you want.
403		634
404	The C<signal_ns> variant doesn't start (activate) the newly created watcher.	635	The C<signal_ns> variant doesn't start (activate) the newly created watcher.
405		636
406	=item $w->set ($signal)	637	=item $w->set ($signal)
407		638
408	Reconfigures the watcher, see the constructor above for details. Can be at	639	Reconfigures the watcher, see the constructor above for details. Can be
409	any time.	640	called at any time.
410		641
411	=item $current_signum = $w->signal	642	=item $current_signum = $w->signal
412		643
413	=item $old_signum = $w->signal ($new_signal)	644	=item $old_signum = $w->signal ($new_signal)
414		645
415	Returns the previously set signal (always as a number not name) and	646	Returns the previously set signal (always as a number not name) and
416	optionally set a new one.	647	optionally set a new one.
417		648
		649	=back
418		650
		651
		652	=head3 CHILD WATCHERS - watch out for process status changes
		653
		654	=over 4
		655
419	=item $w = EV::child $pid, $callback	656	=item $w = EV::child $pid, $trace, $callback
420		657
421	=item $w = EV::child_ns $pid, $callback	658	=item $w = EV::child_ns $pid, $trace, $callback
		659
		660	=item $w = $loop->child ($pid, $trace, $callback)
		661
		662	=item $w = $loop->child_ns ($pid, $trace, $callback)
422		663
423	Call the callback when a status change for pid C<$pid> (or any pid	664	Call the callback when a status change for pid C<$pid> (or any pid
424	if C<$pid> is 0) has been received. More precisely: when the process	665	if C<$pid> is 0) has been received (a status change happens when the
		666	process terminates or is killed, or, when trace is true, additionally when
		667	it is stopped or continued). More precisely: when the process receives
425	receives a SIGCHLD, EV will fetch the outstanding exit/wait status for all	668	a C<SIGCHLD>, EV will fetch the outstanding exit/wait status for all
426	changed/zombie children and call the callback.	669	changed/zombie children and call the callback.
427		670
428	You can access both status and pid by using the C<rstatus> and C<rpid>	671	It is valid (and fully supported) to install a child watcher after a child
429	methods on the watcher object.	672	has exited but before the event loop has started its next iteration (for
		673	example, first you C<fork>, then the new child process might exit, and
		674	only then do you install a child watcher in the parent for the new pid).
430		675
		676	You can access both exit (or tracing) status and pid by using the
		677	C<rstatus> and C<rpid> methods on the watcher object.
		678
431	You can have as many pid watchers per pid as you want.	679	You can have as many pid watchers per pid as you want, they will all be
		680	called.
432		681
433	The C<child_ns> variant doesn't start (activate) the newly created watcher.	682	The C<child_ns> variant doesn't start (activate) the newly created watcher.
434		683
435	=item $w->set ($pid)	684	=item $w->set ($pid, $trace)
436		685
437	Reconfigures the watcher, see the constructor above for details. Can be at	686	Reconfigures the watcher, see the constructor above for details. Can be called at
438	any time.	687	any time.
439		688
440	=item $current_pid = $w->pid	689	=item $current_pid = $w->pid
441
442	=item $old_pid = $w->pid ($new_pid)
443		690
444	Returns the previously set process id and optionally set a new one.	691	Returns the previously set process id and optionally set a new one.
445		692
446	=item $exit_status = $w->rstatus	693	=item $exit_status = $w->rstatus
447		694
…		…
451	=item $pid = $w->rpid	698	=item $pid = $w->rpid
452		699
453	Return the pid of the awaited child (useful when you have installed a	700	Return the pid of the awaited child (useful when you have installed a
454	watcher for all pids).	701	watcher for all pids).
455		702
		703	=back
		704
		705
		706	=head3 STAT WATCHERS - did the file attributes just change?
		707
		708	=over 4
		709
		710	=item $w = EV::stat $path, $interval, $callback
		711
		712	=item $w = EV::stat_ns $path, $interval, $callback
		713
		714	=item $w = $loop->stat ($path, $interval, $callback)
		715
		716	=item $w = $loop->stat_ns ($path, $interval, $callback)
		717
		718	Call the callback when a file status change has been detected on
		719	C<$path>. The C<$path> does not need to exist, changing from "path exists"
		720	to "path does not exist" is a status change like any other.
		721
		722	The C<$interval> is a recommended polling interval for systems where
		723	OS-supported change notifications don't exist or are not supported. If
		724	you use C<0> then an unspecified default is used (which is highly
		725	recommended!), which is to be expected to be around five seconds usually.
		726
		727	This watcher type is not meant for massive numbers of stat watchers,
		728	as even with OS-supported change notifications, this can be
		729	resource-intensive.
		730
		731	The C<stat_ns> variant doesn't start (activate) the newly created watcher.
		732
		733	=item ... = $w->stat
		734
		735	This call is very similar to the perl C<stat> built-in: It stats (using
		736	C<lstat>) the path specified in the watcher and sets perls stat cache (as
		737	well as EV's idea of the current stat values) to the values found.
		738
		739	In scalar context, a boolean is return indicating success or failure of
		740	the stat. In list context, the same 13-value list as with stat is returned
		741	(except that the blksize and blocks fields are not reliable).
		742
		743	In the case of an error, errno is set to C<ENOENT> (regardless of the
		744	actual error value) and the C<nlink> value is forced to zero (if the stat
		745	was successful then nlink is guaranteed to be non-zero).
		746
		747	See also the next two entries for more info.
		748
		749	=item ... = $w->attr
		750
		751	Just like C<< $w->stat >>, but without the initial stat'ing: this returns
		752	the values most recently detected by EV. See the next entry for more info.
		753
		754	=item ... = $w->prev
		755
		756	Just like C<< $w->stat >>, but without the initial stat'ing: this returns
		757	the previous set of values, before the change.
		758
		759	That is, when the watcher callback is invoked, C<< $w->prev >> will be set
		760	to the values found I<before> a change was detected, while C<< $w->attr >>
		761	returns the values found leading to the change detection. The difference (if any)
		762	between C<prev> and C<attr> is what triggered the callback.
		763
		764	If you did something to the filesystem object and do not want to trigger
		765	yet another change, you can call C<stat> to update EV's idea of what the
		766	current attributes are.
		767
		768	=item $w->set ($path, $interval)
		769
		770	Reconfigures the watcher, see the constructor above for details. Can be
		771	called at any time.
		772
		773	=item $current_path = $w->path
		774
		775	=item $old_path = $w->path ($new_path)
		776
		777	Returns the previously set path and optionally set a new one.
		778
		779	=item $current_interval = $w->interval
		780
		781	=item $old_interval = $w->interval ($new_interval)
		782
		783	Returns the previously set interval and optionally set a new one. Can be
		784	used to query the actual interval used.
		785
		786	=back
		787
		788
		789	=head3 IDLE WATCHERS - when you've got nothing better to do...
		790
		791	=over 4
456		792
457	=item $w = EV::idle $callback	793	=item $w = EV::idle $callback
458		794
459	=item $w = EV::idle_ns $callback	795	=item $w = EV::idle_ns $callback
460		796
461	Call the callback when there are no pending io, timer/periodic, signal or	797	=item $w = $loop->idle ($callback)
462	child events, i.e. when the process is idle.	798
		799	=item $w = $loop->idle_ns ($callback)
		800
		801	Call the callback when there are no other pending watchers of the same or
		802	higher priority (excluding check, prepare and other idle watchers of the
		803	same or lower priority, of course). They are called idle watchers because
		804	when the watcher is the highest priority pending event in the process, the
		805	process is considered to be idle at that priority.
		806
		807	If you want a watcher that is only ever called when I<no> other events are
		808	outstanding you have to set the priority to C<EV::MINPRI>.
463		809
464	The process will not block as long as any idle watchers are active, and	810	The process will not block as long as any idle watchers are active, and
465	they will be called repeatedly until stopped.	811	they will be called repeatedly until stopped.
466		812
		813	For example, if you have idle watchers at priority C<0> and C<1>, and
		814	an I/O watcher at priority C<0>, then the idle watcher at priority C<1>
		815	and the I/O watcher will always run when ready. Only when the idle watcher
		816	at priority C<1> is stopped and the I/O watcher at priority C<0> is not
		817	pending with the C<0>-priority idle watcher be invoked.
		818
467	The C<idle_ns> variant doesn't start (activate) the newly created watcher.	819	The C<idle_ns> variant doesn't start (activate) the newly created watcher.
468		820
		821	=back
		822
		823
		824	=head3 PREPARE WATCHERS - customise your event loop!
		825
		826	=over 4
469		827
470	=item $w = EV::prepare $callback	828	=item $w = EV::prepare $callback
471		829
472	=item $w = EV::prepare_ns $callback	830	=item $w = EV::prepare_ns $callback
		831
		832	=item $w = $loop->prepare ($callback)
		833
		834	=item $w = $loop->prepare_ns ($callback)
473		835
474	Call the callback just before the process would block. You can still	836	Call the callback just before the process would block. You can still
475	create/modify any watchers at this point.	837	create/modify any watchers at this point.
476		838
477	See the EV::check watcher, below, for explanations and an example.	839	See the EV::check watcher, below, for explanations and an example.
478		840
479	The C<prepare_ns> variant doesn't start (activate) the newly created watcher.	841	The C<prepare_ns> variant doesn't start (activate) the newly created watcher.
480		842
		843	=back
		844
		845
		846	=head3 CHECK WATCHERS - customise your event loop even more!
		847
		848	=over 4
481		849
482	=item $w = EV::check $callback	850	=item $w = EV::check $callback
483		851
484	=item $w = EV::check_ns $callback	852	=item $w = EV::check_ns $callback
		853
		854	=item $w = $loop->check ($callback)
		855
		856	=item $w = $loop->check_ns ($callback)
485		857
486	Call the callback just after the process wakes up again (after it has	858	Call the callback just after the process wakes up again (after it has
487	gathered events), but before any other callbacks have been invoked.	859	gathered events), but before any other callbacks have been invoked.
488		860
489	This is used to integrate other event-based software into the EV	861	This is used to integrate other event-based software into the EV
…		…
497	# do nothing unless active	869	# do nothing unless active
498	$dispatcher->{_event_queue_h}	870	$dispatcher->{_event_queue_h}
499	or return;	871	or return;
500		872
501	# make the dispatcher handle any outstanding stuff	873	# make the dispatcher handle any outstanding stuff
		874	... not shown
502		875
503	# create an IO watcher for each and every socket	876	# create an I/O watcher for each and every socket
504	@snmp_watcher = (	877	@snmp_watcher = (
505	(map { EV::io $_, EV::READ, sub { } }	878	(map { EV::io $_, EV::READ, sub { } }
506	keys %{ $dispatcher->{_descriptors} }),	879	keys %{ $dispatcher->{_descriptors} }),
		880
		881	EV::timer +($event->[Net::SNMP::Dispatcher::_ACTIVE]
		882	? $event->[Net::SNMP::Dispatcher::_TIME] - EV::now : 0),
		883	0, sub { },
507	);	884	);
508
509	# if there are any timeouts, also create a timer
510	push @snmp_watcher, EV::timer $event->[Net::SNMP::Dispatcher::_TIME] - EV::now, 0, sub { }
511	if $event->[Net::SNMP::Dispatcher::_ACTIVE];
512	};	885	};
513		886
514	The callbacks are irrelevant, the only purpose of those watchers is	887	The callbacks are irrelevant (and are not even being called), the
515	to wake up the process as soon as one of those events occurs (socket	888	only purpose of those watchers is to wake up the process as soon as
516	readable, or timer timed out). The corresponding EV::check watcher will then	889	one of those events occurs (socket readable, or timer timed out). The
517	clean up:	890	corresponding EV::check watcher will then clean up:
518		891
519	our $snmp_check = EV::check sub {	892	our $snmp_check = EV::check sub {
520	# destroy all watchers	893	# destroy all watchers
521	@snmp_watcher = ();	894	@snmp_watcher = ();
522		895
523	# make the dispatcher handle any new stuff	896	# make the dispatcher handle any new stuff
		897	... not shown
524	};	898	};
525		899
526	The callbacks of the created watchers will not be called as the watchers	900	The callbacks of the created watchers will not be called as the watchers
527	are destroyed before this cna happen (remember EV::check gets called	901	are destroyed before this cna happen (remember EV::check gets called
528	first).	902	first).
529		903
530	The C<check_ns> variant doesn't start (activate) the newly created watcher.	904	The C<check_ns> variant doesn't start (activate) the newly created watcher.
531		905
532	=back	906	=back
533		907
		908
		909	=head3 FORK WATCHERS - the audacity to resume the event loop after a fork
		910
		911	Fork watchers are called when a C<fork ()> was detected. The invocation
		912	is done before the event loop blocks next and before C<check> watchers
		913	are being called, and only in the child after the fork.
		914
		915	=over 4
		916
		917	=item $w = EV::fork $callback
		918
		919	=item $w = EV::fork_ns $callback
		920
		921	=item $w = $loop->fork ($callback)
		922
		923	=item $w = $loop->fork_ns ($callback)
		924
		925	Call the callback before the event loop is resumed in the child process
		926	after a fork.
		927
		928	The C<fork_ns> variant doesn't start (activate) the newly created watcher.
		929
		930	=back
		931
		932
		933	=head3 EMBED WATCHERS - when one backend isn't enough...
		934
		935	This is a rather advanced watcher type that lets you embed one event loop
		936	into another (currently only IO events are supported in the embedded
		937	loop, other types of watchers might be handled in a delayed or incorrect
		938	fashion and must not be used).
		939
		940	See the libev documentation at
		941	L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#code_ev_embed_code_when_one_backend_>
		942	for more details.
		943
		944	In short, this watcher is most useful on BSD systems without working
		945	kqueue to still be able to handle a large number of sockets:
		946
		947	my $socket_loop;
		948
		949	# check wether we use SELECT or POLL _and_ KQUEUE is supported
		950	if (
		951	(EV::backend & (EV::BACKEND_POLL \| EV::BACKEND_SELECT))
		952	&& (EV::supported_backends & EV::embeddable_backends & EV::BACKEND_KQUEUE)
		953	) {
		954	# use kqueue for sockets
		955	$socket_loop = new EV::Loop EV::BACKEND_KQUEUE \| EV::FLAG_NOENV;
		956	}
		957
		958	# use the default loop otherwise
		959	$socket_loop \|\|= EV::default_loop;
		960
		961	=over 4
		962
		963	=item $w = EV::embed $otherloop, $callback
		964
		965	=item $w = EV::embed_ns $otherloop, $callback
		966
		967	=item $w = $loop->embed ($otherloop, $callback)
		968
		969	=item $w = $loop->embed_ns ($otherloop, $callback)
		970
		971	Call the callback when the embedded event loop (C<$otherloop>) has any
		972	I/O activity. The C<$callback> should alwas be specified as C<undef> in
		973	this version of EV, which means the embedded event loop will be managed
		974	automatically.
		975
		976	The C<embed_ns> variant doesn't start (activate) the newly created watcher.
		977
		978	=back
		979
		980	=head3 ASYNC WATCHERS - how to wake up another event loop
		981
		982	Async watchers are provided by EV, but have little use in perl directly, as perl
		983	neither supports threads nor direct access to signal handlers or other
		984	contexts where they could be of value.
		985
		986	It is, however, possible to use them from the XS level.
		987
		988	Please see the libev documentation for further details.
		989
		990	=over 4
		991
		992	=item $w = EV::async $callback
		993
		994	=item $w = EV::async_ns $callback
		995
		996	=item $w->send
		997
		998	=item $bool = $w->async_pending
		999
		1000	=back
		1001
		1002
		1003	=head1 PERL SIGNALS
		1004
		1005	While Perl signal handling (C<%SIG>) is not affected by EV, the behaviour
		1006	with EV is as the same as any other C library: Perl-signals will only be
		1007	handled when Perl runs, which means your signal handler might be invoked
		1008	only the next time an event callback is invoked.
		1009
		1010	The solution is to use EV signal watchers (see C<EV::signal>), which will
		1011	ensure proper operations with regards to other event watchers.
		1012
		1013	If you cannot do this for whatever reason, you can also force a watcher
		1014	to be called on every event loop iteration by installing a C<EV::check>
		1015	watcher:
		1016
		1017	my $async_check = EV::check sub { };
		1018
		1019	This ensures that perl gets into control for a short time to handle any
		1020	pending signals, and also ensures (slightly) slower overall operation.
		1021
534	=head1 THREADS	1022	=head1 THREADS
535		1023
536	Threads are not supported by this in any way. Perl pseudo-threads is evil	1024	Threads are not supported by this module in any way. Perl pseudo-threads
537	stuff and must die.	1025	is evil stuff and must die. As soon as Perl gains real threads I will work
		1026	on thread support for it.
		1027
		1028	=head1 FORK
		1029
		1030	Most of the "improved" event delivering mechanisms of modern operating
		1031	systems have quite a few problems with fork(2) (to put it bluntly: it is
		1032	not supported and usually destructive). Libev makes it possible to work
		1033	around this by having a function that recreates the kernel state after
		1034	fork in the child.
		1035
		1036	On non-win32 platforms, this module requires the pthread_atfork
		1037	functionality to do this automatically for you. This function is quite
		1038	buggy on most BSDs, though, so YMMV. The overhead for this is quite
		1039	negligible, because everything the function currently does is set a flag
		1040	that is checked only when the event loop gets used the next time, so when
		1041	you do fork but not use EV, the overhead is minimal.
		1042
		1043	On win32, there is no notion of fork so all this doesn't apply, of course.
538		1044
539	=cut	1045	=cut
540		1046
541	our $DIED = sub {	1047	our $DIED = sub {
542	warn "EV: error in callback (ignoring): $@";	1048	warn "EV: error in callback (ignoring): $@";
543	};	1049	};
544		1050
545	default_loop	1051	default_loop
546	or die 'EV: cannot initialise libev backend. bad $ENV{LIBEV_METHODS}?';	1052	or die 'EV: cannot initialise libev backend. bad $ENV{LIBEV_FLAGS}?';
547
548	push @AnyEvent::REGISTRY, [EV => "EV::AnyEvent"];
549		1053
550	1;	1054	1;
551		1055
552	=head1 SEE ALSO	1056	=head1 SEE ALSO
553		1057
554	L<EV::DNS>, L<EV::AnyEvent>.	1058	L<EV::ADNS> (asynchronous DNS), L<Glib::EV> (makes Glib/Gtk2 use EV as
		1059	event loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient
		1060	coroutines with EV), L<Net::SNMP::EV> (asynchronous SNMP), L<AnyEvent> for
		1061	event-loop agnostic and portable event driven programming.
555		1062
556	=head1 AUTHOR	1063	=head1 AUTHOR
557		1064
558	Marc Lehmann <schmorp@schmorp.de>	1065	Marc Lehmann <schmorp@schmorp.de>
559	http://home.schmorp.de/	1066	http://home.schmorp.de/

Diff Legend

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

Comparing EV/EV.pm (file contents): Revision 1.31 by root, Thu Nov 8 02:21:02 2007 UTC vs. Revision 1.92 by root, Sun May 18 10:45:36 2008 UTC

Diff Legend

Comparing EV/EV.pm (file contents):
Revision 1.31 by root, Thu Nov 8 02:21:02 2007 UTC vs.
Revision 1.92 by root, Sun May 18 10:45:36 2008 UTC