No cache version.
Caching disabled. Default setting for this page:enabled (code LNG204)
If the display is too slow, you can disable the user mode to view the cached version.
The EventBase class
(PECL event >= 1.2.6-beta)
Introduction
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 method , or a backend that it uses to determine which events are ready. The recognized methods are: select , poll , epoll , kqueue , devpoll , evport and win32 .
To configure event base to use, or avoid specific backend EventConfig class can be used.
Do NOT destroy the EventBase object as long as resources of the associated Event objects are not released. Otherwise, it will lead to unpredictable results!
Class synopsis
Predefined Constants
-
EventBase::LOOP_ONCE
-
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".
-
EventBase::LOOP_NONBLOCK
-
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".
-
EventBase::NOLOCK
-
Configuration flag. Do not allocate a lock for the event base, even if we have locking set up".
-
EventBase::STARTUP_IOCP
-
Windows-only configuration flag. Enables the IOCP dispatcher at startup.
-
EventBase::NO_CACHE_TIME
-
Configuration flag. Instead of checking the current time every time the event loop is ready to run timeout callbacks, check after each timeout callback.
-
EventBase::EPOLL_USE_CHANGELIST
-
If we are using the epoll 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 EVENT_EPOLL_USE_CHANGELIST environment variable.
This flag has no effect if one winds up using a backend other than epoll .
Table of Contents
- EventBase::__construct — Constructs EventBase object
- EventBase::dispatch — Dispatch pending events
- EventBase::exit — Stop dispatching events
- EventBase::free — Free resources allocated for this event base
- EventBase::getFeatures — Returns bitmask of features supported
- EventBase::getMethod — Returns event method in use
- EventBase::getTimeOfDayCached — Returns the current event base time
- EventBase::gotExit — Checks if the event loop was told to exit
- EventBase::gotStop — Checks if the event loop was told to exit
- EventBase::loop — Dispatch pending events
- EventBase::priorityInit — Sets number of priorities per event base
- EventBase::reInit — Re-initialize event base(after a fork)
- EventBase::stop — Tells event_base to stop dispatching events
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-class.eventbase.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.