c-ares

484 Commits

14 Branches

96 Tags

22 MiB

Tag: Branch: Tree: 138e387710

Commit Graph

Author	SHA1	Message	Date
Brad House	7963c519fc	Event Subsystem: No longer require integrators to have their own (#696 ) This PR implements an event thread to process all events on file descriptors registered by c-ares. Prior to this feature, integrators were required to understand the internals of c-ares and how to monitor file descriptors and timeouts and process events. Implements OS-specific efficient polling such as epoll(), kqueue(), or IOCP, and falls back to poll() or select() if otherwise unsupported. At this point, it depends on basic threading primitives such as pthreads or windows threads. If enabled via the ARES_OPT_EVENT_THREAD option passed to ares_init_options(), then socket callbacks cannot be used. Fixes Bug: #611 Fix By: Brad House (@bradh352)	10 months ago
Brad House	45698509d8	remove a simply	1 year ago
Brad House	a9442bd828	Basic Thread Safety (#636 ) c-ares does not have any concept of thread-safety. It has always been 100% up to the implementor to ensure they never call c-ares from more than one thread at a time. This patch adds basic thread-safety support, which can be disabled at compile time if not desired. It uses a single recursive mutex per channel, which should be extremely quick when uncontested so overhead should be minimal. Fixes Bug: #610 Also sets the stage to implement #611 Fix By: Brad House (@bradh352)	1 year ago

Author

SHA1

Message

Date

Brad House

7963c519fc

Event Subsystem: No longer require integrators to have their own (#696 )

This PR implements an event thread to process all events on file descriptors registered by c-ares. Prior to this feature, integrators were required to understand the internals of c-ares and how to monitor file descriptors and timeouts and process events.

Implements OS-specific efficient polling such as epoll(), kqueue(), or IOCP, and falls back to poll() or select() if otherwise unsupported. At this point, it depends on basic threading primitives such as pthreads or windows threads.

If enabled via the ARES_OPT_EVENT_THREAD option passed to ares_init_options(), then socket callbacks cannot be used.

Fixes Bug: #611
Fix By: Brad House (@bradh352)

10 months ago

Brad House

45698509d8

remove a simply

1 year ago

Brad House

a9442bd828

Basic Thread Safety (#636 )

c-ares does not have any concept of thread-safety. It has always been 100% up to the implementor to ensure they never call c-ares from more than one thread at a time. This patch adds basic thread-safety support, which can be disabled at compile time if not desired. It uses a single recursive mutex per channel, which should be extremely quick when uncontested so overhead should be minimal.

Fixes Bug: #610

Also sets the stage to implement #611

Fix By: Brad House (@bradh352)

1 year ago

3 Commits (138e3877101a29439ad8a179d5fe143e1886a864)