Watcher callbacks
All watchers can be active(waiting for events) or inactive(paused). Only
active watchers will have their callbacks invoked. All callbacks will be
called with at least two arguments:
watcher
- the watcher, and
revents
a bitmask of received events.
Watcher callbacks are passed to the watcher constructors (the classes derived from EvWatcher - EvCheck::__construct() , EvChild::__construct() etc.). A watcher callback should match the following prototype:
$watcher
= NULL
[,
int
$revents
= NULL
]] ) : void
-
watcher -
The watcher instance(of a class extending EvWatcher ).
-
revents
Each watcher type has its associated bit in
revents
, so one can use the same callback for multiple watchers. The event mask is
named after the type, i.e.
EvChild
(or
EvLoop::child()
) sets
EV::CHILD
,
EvPrepare
(or
EvLoop::prepare()
) sets
Ev::PREPARE
,
EvPeriodic
(or
EvLoop::periodic()
) sets
Ev::PERIODIC
and so on, with the exception of I/O events (which can set both
Ev::READ
and
Ev::WRITE
bits).
English translation
You have asked to visit this site in English. For now, only the interface is translated, but not all the content yet.If you want to help me in translations, your contribution is welcome. All you need to do is register on the site, and send me a message asking me to add you to the group of translators, which will give you the opportunity to translate the pages you want. A link at the bottom of each translated page indicates that you are the translator, and has a link to your profile.
Thank you in advance.
Document created the 30/01/2003, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/php-rf-ev.watcher-callbacks.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.
