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

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

Diff Legend

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

Comparing EV/EV.pm (file contents): Revision 1.32 by root, Thu Nov 8 17:02:10 2007 UTC vs. Revision 1.82 by root, Fri Jan 25 15:45:08 2008 UTC

Diff Legend

Comparing EV/EV.pm (file contents):
Revision 1.32 by root, Thu Nov 8 17:02:10 2007 UTC vs.
Revision 1.82 by root, Fri Jan 25 15:45:08 2008 UTC