evperiodic(3) [php man page]

EVPERIODIC(3)								 1							     EVPERIODIC(3)

The EvPeriodic class

INTRODUCTION

	Periodic watchers are also timers of a kind, but they are very versatile.

	Unlike	EvTimer  ,  EvPeriodic	watchers  are  not  based  on real time(or relative time, the physical time that passes) but on wall clock
       time(absolute time, calendar or clock). The difference is that wall clock time can run faster or slower than real time, and time jumps  are
       not uncommon(e.g. when adjusting it).

       EvPeriodic  watcher  can be configured to trigger after some specific point in time. For example, if an EvPeriodic watcher is configured to
       trigger "in 10 seconds" (e.g.  EvLoop::now + 10.0 , i.e. an absolute time, not a delay), and the system clock is reset to  January  of  the
       previous  year  ,  then	it will take a year or more to trigger the event (unlike an EvTimer , which would still trigger roughly 10 seconds
       after starting it as it uses a relative timeout).

	As with timers, the callback is guaranteed to be invoked only when the point in time where it is supposed to trigger has passed. If multi-
       ple  timers become ready during the same loop iteration then the ones with earlier time-out values are invoked before ones with later time-
       out values (but this is no longer true when a callback calls EvLoop::run recursively).

CLASS SYNOPSIS

       EvPeriodic

       EvPeriodicextends
       EvWatcher

       Properties

       o public$offset

       o public$interval

       Inherited properties

       o public$is_active

       o public$data

       o public$is_pending

       o public$priority

       Methods

       o public void EvPeriodic::again (void  )

       o public double EvPeriodic::at (void  )

       o public EvPeriodic::__construct NULL (double  $offset, string  $interval, callable  $reschedule_cb, callable  $callback,  [mixed   $data],
	 [int  $priority])

       o finalpublicstatic  EvPeriodic	EvPeriodic::createStopped  NULL  (double   $offset,  double  $interval, callable  $reschedule_cb, callable
	 $callback, [mixed  $data], [int  $priority])

       o public void EvPeriodic::set (double  $offset, double  $interval)

       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 $offset
		- When repeating, this contains the offset value, otherwise this is the absolute point in time(the offset value passed to  EvPeri-
		odic::set , although libev might modify this value for better numerical stability).

	      o $interval
		-  The	current  interval  value.  Can be modified any time, but changes only take effect when the periodic timer fires or EvPeri-
		odic::again is being called.

PHP Documentation Group 													     EVPERIODIC(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

evperiodic(3) [php man page]

Check Out this Related Man Page