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

Comparing EV/EV.pm (file contents):
Revision 1.50 by root, Sat Nov 24 08:42:38 2007 UTC vs.
Revision 1.79 by root, Sat Dec 22 16:37:07 2007 UTC

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

Diff Legend

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

Comparing EV/EV.pm (file contents): Revision 1.50 by root, Sat Nov 24 08:42:38 2007 UTC vs. Revision 1.79 by root, Sat Dec 22 16:37:07 2007 UTC

Diff Legend

Comparing EV/EV.pm (file contents):
Revision 1.50 by root, Sat Nov 24 08:42:38 2007 UTC vs.
Revision 1.79 by root, Sat Dec 22 16:37:07 2007 UTC