Skip to content
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

Open
rcmcdonald91 opened this issue Apr 26, 2024 · 2 comments
Open

[FR] Introduce libunbound-control library for external consumers #1055

rcmcdonald91 opened this issue Apr 26, 2024 · 2 comments

Comments

@rcmcdonald91
Copy link
Contributor

rcmcdonald91 commented Apr 26, 2024

Current behavior
Currently all the business logic for unbound-control is self-contained within unbound-control.c.

Describe the desired feature
Break out this core functionality into a shared library (say libunbound-control) and reimplement unbound-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.

@rcmcdonald91
Copy link
Contributor Author

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.

@rcmcdonald91
Copy link
Contributor Author

#1058

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant