1
.\" $OpenBSD: event.3,v 1.4 2002/07/12 18:50:48 provos Exp $
3
.\" Copyright (c) 2000 Artur Grabowski <art@openbsd.org>
4
.\" All rights reserved.
6
.\" Redistribution and use in source and binary forms, with or without
7
.\" modification, are permitted provided that the following conditions
10
.\" 1. Redistributions of source code must retain the above copyright
11
.\" notice, this list of conditions and the following disclaimer.
12
.\" 2. Redistributions in binary form must reproduce the above copyright
13
.\" notice, this list of conditions and the following disclaimer in the
14
.\" documentation and/or other materials provided with the distribution.
15
.\" 3. The name of the author may not be used to endorse or promote products
16
.\" derived from this software without specific prior written permission.
18
.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
19
.\" INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
20
.\" AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
21
.\" THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
22
.\" EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
23
.\" PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
24
.\" OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
25
.\" WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
26
.\" OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
27
.\" ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
39
.Nm event_base_dispatch ,
41
.Nm event_base_loopexit ,
42
.Nm event_base_loopbreak ,
50
.Nm event_initialized ,
51
.Nm event_priority_init ,
52
.Nm event_priority_set ,
57
.Nm evtimer_initialized ,
62
.Nm signal_initialized ,
64
.Nm bufferevent_free ,
65
.Nm bufferevent_write ,
66
.Nm bufferevent_write_buffer ,
67
.Nm bufferevent_read ,
68
.Nm bufferevent_enable ,
69
.Nm bufferevent_disable ,
70
.Nm bufferevent_settimeout ,
71
.Nm bufferevent_base_set ,
75
.Nm evbuffer_add_buffer ,
76
.Nm evbuffer_add_printf ,
77
.Nm evbuffer_add_vprintf ,
82
.Nm evbuffer_readline ,
84
.Nm evhttp_bind_socket ,
86
.Nd execute a function when a specific event occurs
88
.Fd #include <sys/time.h>
89
.Fd #include <event.h>
90
.Ft "struct event_base *"
91
.Fn "event_init" "void"
93
.Fn "event_dispatch" "void"
95
.Fn "event_loop" "int flags"
97
.Fn "event_loopexit" "struct timeval *tv"
99
.Fn "event_loopbreak" "void"
101
.Fn "event_set" "struct event *ev" "int fd" "short event" "void (*fn)(int, short, void *)" "void *arg"
103
.Fn "event_base_dispatch" "struct event_base *base"
105
.Fn "event_base_loop" "struct event_base *base" "int flags"
107
.Fn "event_base_loopexit" "struct event_base *base" "struct timeval *tv"
109
.Fn "event_base_loopbreak" "struct event_base *base"
111
.Fn "event_base_set" "struct event_base *base" "struct event *"
113
.Fn "event_base_free" "struct event_base *base"
115
.Fn "event_add" "struct event *ev" "struct timeval *tv"
117
.Fn "event_del" "struct event *ev"
119
.Fn "event_once" "int fd" "short event" "void (*fn)(int, short, void *)" "void *arg" "struct timeval *tv"
121
.Fn "event_base_once" "struct event_base *base" "int fd" "short event" "void (*fn)(int, short, void *)" "void *arg" "struct timeval *tv"
123
.Fn "event_pending" "struct event *ev" "short event" "struct timeval *tv"
125
.Fn "event_initialized" "struct event *ev"
127
.Fn "event_priority_init" "int npriorities"
129
.Fn "event_priority_set" "struct event *ev" "int priority"
131
.Fn "evtimer_set" "struct event *ev" "void (*fn)(int, short, void *)" "void *arg"
133
.Fn "evtimer_add" "struct event *ev" "struct timeval *"
135
.Fn "evtimer_del" "struct event *ev"
137
.Fn "evtimer_pending" "struct event *ev" "struct timeval *tv"
139
.Fn "evtimer_initialized" "struct event *ev"
141
.Fn "signal_set" "struct event *ev" "int signal" "void (*fn)(int, short, void *)" "void *arg"
143
.Fn "signal_add" "struct event *ev" "struct timeval *"
145
.Fn "signal_del" "struct event *ev"
147
.Fn "signal_pending" "struct event *ev" "struct timeval *tv"
149
.Fn "signal_initialized" "struct event *ev"
150
.Ft "struct bufferevent *"
151
.Fn "bufferevent_new" "int fd" "evbuffercb readcb" "evbuffercb writecb" "everrorcb" "void *cbarg"
153
.Fn "bufferevent_free" "struct bufferevent *bufev"
155
.Fn "bufferevent_write" "struct bufferevent *bufev" "void *data" "size_t size"
157
.Fn "bufferevent_write_buffer" "struct bufferevent *bufev" "struct evbuffer *buf"
159
.Fn "bufferevent_read" "struct bufferevent *bufev" "void *data" "size_t size"
161
.Fn "bufferevent_enable" "struct bufferevent *bufev" "short event"
163
.Fn "bufferevent_disable" "struct bufferevent *bufev" "short event"
165
.Fn "bufferevent_settimeout" "struct bufferevent *bufev" "int timeout_read" "int timeout_write"
167
.Fn "bufferevent_base_set" "struct event_base *base" "struct bufferevent *bufev"
168
.Ft "struct evbuffer *"
169
.Fn "evbuffer_new" "void"
171
.Fn "evbuffer_free" "struct evbuffer *buf"
173
.Fn "evbuffer_add" "struct evbuffer *buf" "const void *data" "size_t size"
175
.Fn "evbuffer_add_buffer" "struct evbuffer *dst" "struct evbuffer *src"
177
.Fn "evbuffer_add_printf" "struct evbuffer *buf" "const char *fmt" "..."
179
.Fn "evbuffer_add_vprintf" "struct evbuffer *buf" "const char *fmt" "va_list ap"
181
.Fn "evbuffer_drain" "struct evbuffer *buf" "size_t size"
183
.Fn "evbuffer_write" "struct evbuffer *buf" "int fd"
185
.Fn "evbuffer_read" "struct evbuffer *buf" "int fd" "int size"
187
.Fn "evbuffer_find" "struct evbuffer *buf" "const u_char *data" "size_t size"
189
.Fn "evbuffer_readline" "struct evbuffer *buf"
190
.Ft "struct evhttp *"
191
.Fn "evhttp_new" "struct event_base *base"
193
.Fn "evhttp_bind_socket" "struct evhttp *http" "const char *address" "u_short port"
195
.Fn "evhttp_free" "struct evhttp *http"
197
.Fa (*event_sigcb)(void) ;
198
.Ft volatile sig_atomic_t
203
API provides a mechanism to execute a function when a specific event
204
on a file descriptor occurs or after a given time has passed.
208
API needs to be initialized with
210
before it can be used.
212
In order to process events, an application needs to call
214
This function only returns on error, and should replace the event core
215
of the application program.
219
prepares the event structure
221
to be used in future calls to
225
The event will be prepared to call the function specified by the
229
argument indicating the file descriptor, a
231
argument indicating the type of event, and a
233
argument given in the
238
indicates the file descriptor that should be monitored for events.
239
The events can be either
243
indicating that an application can read or write from the file descriptor
244
respectively without blocking.
248
will be called with the file descriptor that triggered the event and
249
the type of event which will be either
255
Additionally, an event which has registered interest in more than one of the
256
preceeding events, via bitwise-OR to
258
can provide its callback function with a bitwise-OR of more than one triggered
268
Once initialized, the
270
structure can be used repeatedly with
274
and does not need to be reinitialized unless the function called and/or
275
the argument to it are to be changed.
278
structure has been added to libevent using
280
the structure must persist until the event occurs (assuming
282
is not set) or is removed
285
You may not reuse the same
287
structure for multiple monitored descriptors; each descriptor
293
schedules the execution of the
295
event when the event specified in
297
occurs or in at least the time specified in the
303
no timeout occurs and the function will only be called
304
if a matching event occurs on the file descriptor.
307
argument must be already initialized by
309
and may not be used in calls to
311
until it has timed out or been removed with
315
argument already has a scheduled timeout, the old timeout will be
316
replaced by the new one.
320
will cancel the event in the argument
322
If the event has already executed or has never been added
323
the call will have no effect.
329
.Fn evtimer_initialized ,
332
are abbreviations for common situations where only a timeout is required.
333
The file descriptor passed will be \-1, and the event type will be
340
.Fn signal_initialized ,
344
The event type will be a persistent
351
In order to avoid races in signal handlers, the
353
API provides two variables:
360
to indicate that a signal has been received.
363
to a callback function.
364
After the signal handler sets
367
will execute the callback function to process received signals.
368
The callback returns 1 when no events are registered any more.
369
It can return \-1 to indicate an error to the
382
However, it schedules a callback to be called exactly once and does not
383
require the caller to prepare an
386
This function supports
394
function can be used to check if the event specified by
403
the expiration time of the event will be returned in
407
.Fn event_initialized
408
macro can be used to check if an event has been initialized.
412
function provides an interface for single pass execution of pending
421
function exits from the event loop. The next
424
given timer expires will complete normally (handling all queued events) then
425
exit without blocking for events again. Subsequent invocations of
427
will proceed normally.
430
function exits from the event loop immediately.
432
will abort after the next event is completed;
434
is typically invoked from this event's callback. This behavior is analogous
435
to the "break;" statement. Subsequent invocations of
437
will proceed normally.
439
It is the responsibility of the caller to provide these functions with
440
pre-allocated event structures.
445
schedules all active events with the same priority.
446
However, sometimes it is desirable to process some events with a higher
447
priority than others.
450
supports strict priority queues.
451
Active events with a lower priority are always processed before events
452
with a higher priority.
454
The number of different priorities can be set initially with the
455
.Fn event_priority_init
457
This function should be called before the first call to
460
.Fn event_priority_set
461
function can be used to assign a priority to an event.
464
assigns the middle priority to all events unless their priority
466
.Sh THREAD SAFE EVENTS
468
has experimental support for thread-safe events.
469
When initializing the library via
471
an event base is returned.
472
This event base can be used in conjunction with calls to
474
.Fn event_base_dispatch ,
475
.Fn event_base_loop ,
476
.Fn event_base_loopexit ,
477
.Fn bufferevent_base_set
479
.Fn event_base_free .
481
should be called after preparing an event with
485
assigns the provided event to the most recently created event base.
486
.Fn bufferevent_base_set
487
should be called after preparing a bufferevent with
488
.Fn bufferevent_new .
490
should be used to free memory associated with the event base
491
when it is no longer needed.
494
provides an abstraction on top of the regular event callbacks.
495
This abstraction is called a
496
.Va "buffered event" .
497
A buffered event provides input and output buffers that get filled
498
and drained automatically.
499
The user of a buffered event no longer deals directly with the IO,
500
but instead is reading from input and writing to output buffers.
502
A new bufferevent is created by
503
.Fn bufferevent_new .
506
specifies the file descriptor from which data is read and written to.
507
This file descriptor is not allowed to be a
509
The next three parameters are callbacks.
510
The read and write callback have the following form:
512
.Fn "(*cb)" "struct bufferevent *bufev" "void *arg" .
513
The error callback has the following form:
515
.Fn "(*cb)" "struct bufferevent *bufev" "short what" "void *arg" .
516
The argument is specified by the fourth parameter
519
.Fa bufferevent struct
520
pointer is returned on success, NULL on error.
521
Both the read and the write callback may be NULL.
522
The error callback has to be always provided.
524
Once initialized, the bufferevent structure can be used repeatedly with
525
bufferevent_enable() and bufferevent_disable().
526
The flags parameter can be a combination of
530
When read enabled the bufferevent will try to read from the file
531
descriptor and call the read callback.
532
The write callback is executed
533
whenever the output buffer is drained below the write low watermark,
539
.Fn bufferevent_write
540
function can be used to write data to the file descriptor.
541
The data is appended to the output buffer and written to the descriptor
542
automatically as it becomes available for writing.
543
.Fn bufferevent_write
544
returns 0 on success or \-1 on failure.
547
function is used to read data from the input buffer,
548
returning the amount of data read.
550
If multiple bases are in use, bufferevent_base_set() must be called before
551
enabling the bufferevent for the first time.
552
.Sh NON-BLOCKING HTTP SUPPORT
554
provides a very thin HTTP layer that can be used both to host an HTTP
555
server and also to make HTTP requests.
556
An HTTP server can be created by calling
558
It can be bound to any port and address with the
559
.Fn evhttp_bind_socket
561
When the HTTP server is no longer used, it can be freed via
564
To be notified of HTTP requests, a user needs to register callbacks with the
566
This can be done by calling
568
The second argument is the URI for which a callback is being registered.
569
The corresponding callback will receive an
570
.Va struct evhttp_request
571
object that contains all information about the request.
573
This section does not document all the possible function calls; please
576
for the public interfaces.
578
It is possible to disable support for
579
.Va epoll , kqueue , devpoll , poll
582
by setting the environment variable
583
.Va EVENT_NOEPOLL , EVENT_NOKQUEUE , EVENT_NODEVPOLL , EVENT_NOPOLL
587
By setting the environment variable
588
.Va EVENT_SHOW_METHOD ,
590
displays the kernel notification method that it uses.
592
Upon successful completion
597
Otherwise, \-1 is returned and the global variable errno is
598
set to indicate the error.
608
API manpage is based on the
610
manpage by Artur Grabowski.
613
to Windows is due to Michael A. Davis.
614
Support for real-time signals is due to Taral.
618
library was written by Niels Provos.
620
This documentation is neither complete nor authoritative.
621
If you are in doubt about the usage of this API then
622
check the source code to find out how it works, write
623
up the missing piece of documentation and send it to
624
me for inclusion in this man page.