-
-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Introduce libunbound-control library for external consumers #1055
Comments
I have a functional PoC One thing that I would like is to be able to recycle the connection, SSL context between requests. Any advice here would be most welcomed. It doesn't look like daemon/remote.c is able to handle this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behavior
Currently all the business logic for
unbound-control
is self-contained withinunbound-control.c
.Describe the desired feature
Break out this core functionality into a shared library (say
libunbound-control
) and reimplementunbound-control
in terms of this library.Potential use-case
The ability for external consumers to link against
libunbound-control
and communicate with Unbound in a variety of ways.We should also start a conversation about the design of this library. My initial thought is to start moving functionality from unbound-control into libunbound. I don't think we strictly need another library when we already have libunbound and the requisite build infrastructure.
The text was updated successfully, but these errors were encountered: