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

Sync API in terms of Async API #108

Open
vanrein opened this issue Mar 28, 2019 · 0 comments
Open

Sync API in terms of Async API #108

vanrein opened this issue Mar 28, 2019 · 0 comments

Comments

@vanrein
Copy link
Contributor

vanrein commented Mar 28, 2019

We started off with a synchronous library which basically supports sox = tlspool_starttls (sox) forms. Later, we added an Asynchronous API for use in async and event-driven code. We now have two code bases with somewhat overlapping activities. We might consider rewriting the Synchronous API in terms of the Asynchronous API to simplify the code base and reduce library sizes. At least the master thread can be rewritten easily with select() and tlspool_async_process(), and the registry can be recoded with the UThash primitive included in the Asynchronous API. Note differences in API safety properties though.

Relates to issues #57 , #99 and #95 .

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