(PECL event >= 1.2.6-beta)
EventBase class represents libevent's event base structure. It holds a set of events and can poll to determine which events are active.
Each event base has a
, or a
that it uses to determine which events are ready. The recognized methods
To configure event base to use, or avoid specific backend EventConfig class can be used.
object as long as resources of the associated
objects are not released. Otherwise, it will lead to unpredictable
$timeout] ) : bool
$flags] ) : bool
$n_priorities) : bool
Flag used with EventBase::loop() method which means: "block until libevent has an active event, then exit once all active events have had their callbacks run".
Flag used with EventBase::loop() method which means: "do not block: see which events are ready now, run the callbacks of the highest-priority ones, then exit".
Configuration flag. Do not allocate a lock for the event base, even if we have locking set up".
Windows-only configuration flag. Enables the IOCP dispatcher at startup.
Configuration flag. Instead of checking the current time every time the event loop is ready to run timeout callbacks, check after each timeout callback.
If we are using the
backend, this flag says that it is safe to use Libevent's internal
change-list code to batch up adds and deletes in order to try to do as
few syscalls as possible.
Setting this flag can make code run faster, but it may trigger a Linux bug: it is not safe to use this flag if one has any fds cloned by dup(), or its variants. Doing so will produce strange and hard-to-diagnose bugs.
This flag can also be activated by settnig the
This flag has no effect if one winds up using a backend other than