Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

evwatcher(3) [php man page]

EVWATCHER(3)								 1							      EVWATCHER(3)

The EvWatcher class

INTRODUCTION
EvWatcher is a base class for all watchers( EvCheck , EvChild etc.). Since EvWatcher 's constructor is abstract , one can't(and don't need to) create EvWatcher objects directly. CLASS SYNOPSIS
EvWatcher abstract EvWatcher Properties o public$is_active o public$data o public$is_pending o public$priority Methods o public int EvWatcher::clear (void ) o abstractpublic EvWatcher::__construct (void ) o public void EvWatcher::feed (int $revents) o public EvLoop EvWatcher::getLoop (void ) o public void EvWatcher::invoke (int $revents) o public bool EvWatcher::keepalive ([bool $value]) o public void EvWatcher::setCallback (callable $callback) o public void EvWatcher::start (void ) o public void EvWatcher::stop (void ) PROPERTIES
o $is_active - Readonly . TRUE if the watcher is active. FALSE otherwise. o $data - User custom data associated with the watcher o $is_pending - Readonly . TRUE if the watcher is pending, i.e. it has outstanding events, but its callback has not yet been invoked. FALSE otherwise. As long, as a watcher is pending(but not active), one must not change its priority. o $priority - Integer between Ev::MINPRI and Ev::MAXPRI . Pending watchers with higher priority will be invoked before watchers with lower priority, but priority will not keep watchers from being executed(except for EvIdle watchers). EvIdle watchers provide functional- ity to suppress invocation when higher priority events are pending. PHP Documentation Group EVWATCHER(3)

Check Out this Related Man Page

EVIO(3) 								 1								   EVIO(3)

The EvIo class

INTRODUCTION
EvIo watchers check whether a file descriptor(or socket, or a stream castable to numeric file descriptor) is readable or writable in each iteration of the event loop, or, more precisely, when reading would not block the process and writing would at least be able to write some data. This behaviour is called level-triggering because events are kept receiving as long as the condition persists. To stop receiving events just stop the watcher. The number of read and/or write event watchers per $fd is unlimited. Setting all file descriptors to non-blocking mode is also usually a good idea(but not required). Another thing to watch out for is that it is quite easy to receive false readiness notifications, i.e. the callback might be called with Ev::READ but a subsequent read() will actually block because there is no data. It is very easy to get into this situation. Thus it is best to always use non-blocking I/O: An extra read() returning EAGAIN (or similar) is far preferable to a program hanging until some data arrives. If for some reason it is impossible to run the $fd in non-blocking mode, then separately re-test whether a file descriptor is really ready. Some people additionally use SIGALRM and an interval timer, just to be sure thry won't block infinitely. Always consider using non-blocking mode. CLASS SYNOPSIS
EvIo EvIoextends EvWatcher Properties o public$fd o public$events Inherited properties o public$is_active o public$data o public$is_pending o public$priority Methods o public EvIo::__construct (mixed $fd, int $events, callable $callback, [mixed $data], [int $priority]) o finalpublicstatic EvIo EvIo::createStopped NULL (mixed $fd, int $events, callable $callback, [mixed $data], [int $priority]) o public void EvIo::set (mixed $fd, int $events) Inherited methods o public int EvWatcher::clear (void ) o abstractpublic EvWatcher::__construct (void ) o public void EvWatcher::feed (int $revents) o public EvLoop EvWatcher::getLoop (void ) o public void EvWatcher::invoke (int $revents) o public bool EvWatcher::keepalive ([bool $value]) o public void EvWatcher::setCallback (callable $callback) o public void EvWatcher::start (void ) o public void EvWatcher::stop (void ) PROPERTIES
o $fd - o $events - PHP Documentation Group EVIO(3)
Man Page