Lines Matching +full:protected +full:- +full:clocks

27   There is a work-in-progress book with reference manual at
28 http://www.wangafu.net/~nickm/libevent-book/ .
31 on the mailing list at libevent-users@freehaven.net. The mailing list
32 is subscribers-only, so you will need to subscribe before you post.
36 Our source-compatibility policy is that correct code (that is to say,
44 probably need to be recompiled against Libevent 2.1.4-alpha if you
52 We now provide an --enable-gcc-hardening configure option to turn on
55 There is also an --enable-silent-rules configure option to make
58 You no longer need to use the --enable-gcc-warnings option to turn on
66 There is now an alternative cmake-based build process; cmake users
74 that time-consuming or numerous low-priority events don't keep it from
75 checking for new high-priority events. You can now use the
85 environment variable to a non-empty string.
92 memory-leak-checking tools, because Libevent allocated some global
95 globally held resources before exiting, so that your leak-check tools
96 don't complain. (Note: this function doesn't free non-global things
99 your process exit()s. If you aren't using a leak-checking tool, there
131 you'll might need a way to de-allocate yourself.
138 active event callbacks, and re-scan for new events right away.
142 user-supplied callback on each. The callback must not alter the events
148 of "event_add(ev, NULL)" on an already-added event with a timeout. But
149 that's a no-op in past versions of Libevent, and we don't want to
192 But now suppose that the data structure is protected by a lock, and we
198 event_del(connection->read_event);
212 thread on libevent-users starting on 6 August 2012 and running through
214 http://archives.seul.org/libevent/users/Feb-2012/msg00053.html and
220 2.1.3-alpha adds a new flag, "EV_FINALIZE". You can pass it to
231 EV_FINALIZE has no effect on a single-threaded program, or on a
236 more fine-grained control:
250 To safely tear down an event that may be running, Libevent 2.1.3-alpha
259 A finalized event cannot be re-added or activated. The finalizer
292 file-segment object, and evbuffer_add_file_segment() to insert it (or
317 NUL-terminated strings from buffers.
344 rate-limit settings for a bufferevent; bufferevent_getwatermark() can
366 packets were sent. The current evdns interface-detection code uses
386 LEV_OPT_DEFERRED_ACCEPT -- Tells the OS that it doesn't need to
392 LEV_OPT_REUSEABLE_PORT -- Indicates that we ask to allow multiple servers
396 LEV_OPT_DISABLED -- Creates an evconnlistener in the disabled (not
408 Ellzey's libevhtp library. Don't worry -- this won't happen until
416 microsecond-granularity timeouts.
444 You can override the default HTTP Content-Type with the new
460 You can add linger-close for http server by passing
470 - EVHTTP_CON_REUSE_CONNECTED_ADDR -- reuse connection address on retry (avoid
472 - EVHTTP_CON_READ_ON_WRITE_ERROR - try read error, since server may already
489 its (sort-of) secure RNG.
493 There are new API to work with monotonic timer -- monotonic time is
494 guaranteed never to run in reverse, but is not necessarily epoch-based. Use
497 - evutil_monotonic_timer_new()/evutil_monotonic_timer_free()
498 - evutil_configure_monotonic_time()
499 - evutil_gettime_monotonic()
507 2. Cross-platform performance improvements
527 0-second timeout to ensure that a callback will get run 'as soon as
534 timeout in the event loop was adjusted--whether it had become earlier
541 Instead of checking for a wall-clock time jump every time we call
569 The EVBUFFER_EOL_CRLF line-ending type is now much faster, thanks to
589 3. Backend/OS-specific improvements
591 3.1. Linux-specific improvements
594 a table-driven lookup, rather than the previous pile of cascading
596 code run a little faster on change-heavy loads.
601 close-on-exec. This should save syscalls throughout our codebase, and
602 avoid race-conditions if an exec() occurs after a socket is socket is
603 created but before we can make it close-on-execute on it.
605 3.2. Windows-specific improvements
608 significantly faster and more accurate than our old ftime()-based approach.
613 improvements from Libevent 2.0. Notably, it keeps track of per-fd
615 linear scans over recently-added events. This last change makes it
625 3.5. Monotonic clocks on even more platforms
629 Libevent has support for monotonic clocks on OSX and Windows too, and a
630 fallback implementation for systems without monotonic clocks that will at
635 NTP, or in large amounts due to users who move their system clocks all over
638 3.6. Faster cross-thread notification on kqueue
659 On my desktop, a full "make verify" run of Libevent 2.0.18-stable
660 requires about 218 seconds. Libevent 2.1.1-alpha cuts this down to
666 4.2. Finicky tests are now off-by-default
672 issues. To re-enable all tests, run ./test/regress using the "@all"
677 Our autotools-based build system has been updated to build without
692 Libevent now uses large-file support internally on platforms where it
700 enable per-system macros needed to enable not-on-by-default features.
702 internal-use-only evconfig-private.h header, since their names need to
707 Libevent now tries to detect OpenSSL via pkg-config.
737 internal light-weight event_callback supertype, and both support
738 priorities and take part in the other anti-priority-inversion
752 There are some under-tested modules, though: we need to fix those.
755 - https://travis-ci.org/libevent/libevent
756 - https://ci.appveyor.com/project/nmathewson/libevent
759 - https://coveralls.io/github/libevent/libevent
762 travis-ci allows, and there is a wrapper (in python) that will parse logs and
764 - https://github.com/libevent/libevent-extras/blob/master/tools/vagrant-tests.py