evio(3) [php 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)

Check Out this Related Man Page

EVCHECK(3)								 1								EVCHECK(3)

The EvCheck class

INTRODUCTION

       EvPrepare and EvCheck watchers are usually used in pairs. EvPrepare watchers get invoked before the process blocks, EvCheck afterwards.

	It  is	not allowed to call EvLoop::run or similar methods or functions that enter the current event loop from either EvPrepare or EvCheck
       watchers. Other loops than the current one are fine, however. The rationale behind this is that one don't need to check	for  recursion	in
       those  watchers,  i.e. the sequence will always be: EvPrepare -> blocking -> EvCheck , so having a watcher of each kind they will always be
       called in pairs bracketing the blocking call.

	The main purpose is to integrate other event mechanisms into libev and their use is somewhat advanced. They could be used, for example, to
       track variable changes, implement custom watchers, integrate net-snmp or a coroutine library and lots more. They are also occasionally use-
       ful to cache some data and want to flush it before blocking.

	It is recommended to give EvCheck watchers highest( Ev::MAXPRI ) priority, to ensure that they are being run  before  any  other  watchers
       after the poll (this doesn't matter for EvPrepare watchers).

	Also,  EvCheck	watchers  should  not  activate/feed events. While libev fully supports this, they might get executed before other EvCheck
       watchers did their job.

CLASS SYNOPSIS

       EvCheck

       EvCheckextends
       EvWatcher

       Inherited properties

       o public$is_active

       o public$data

       o public$is_pending

       o public$priority

       Methods

       o public EvCheck::__construct (callable	$callback, [mixed  $data], [int  $priority])

       o finalpublicstatic object EvCheck::createStopped (string  $callback, [string  $data], [string  $priority])

       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  )

PHP Documentation Group 														EVCHECK(3)

Linux and UNIX Man Pages

evio(3) [php man page]

Check Out this Related Man Page