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

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

Diff Legend

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

Comparing EV/EV.pm (file contents): Revision 1.34 by root, Fri Nov 9 19:38:56 2007 UTC vs. Revision 1.73 by root, Fri Dec 21 05:10:01 2007 UTC

Diff Legend

Comparing EV/EV.pm (file contents):
Revision 1.34 by root, Fri Nov 9 19:38:56 2007 UTC vs.
Revision 1.73 by root, Fri Dec 21 05:10:01 2007 UTC