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

Help to understand what the library actually does #177

Open
mdbergmann opened this issue May 2, 2020 · 3 comments
Open

Help to understand what the library actually does #177

mdbergmann opened this issue May 2, 2020 · 3 comments

Comments

@mdbergmann
Copy link

mdbergmann commented May 2, 2020

Hi.

Looking though the functionality of the library it seems that there is a lot of high-level functionality, like DNS, HTTP server and client, etc.
Shouldn't the library just provide facilities to do async I/O so that any HTTP server, client or other libraries can be used on top of what cl-async provides?

I don't want to be disrespectful. But this additional functionality could be a burden to maintain.

@Plisp
Copy link
Contributor

Plisp commented May 2, 2020

The http support has actually been deprecated (the tests are still here, but not loaded).
This library is mostly an interface to libuv (which has some DNS utilities as you mentioned, for nodejs) with lisp abstractions over error handling, libuv's handles and C callbacks.

@mdbergmann
Copy link
Author

OK, thanks.

(the tests are still here, but not loaded)

Why not delete them? It would be still in the git history.

@Plisp
Copy link
Contributor

Plisp commented May 3, 2020

It should be fine to remove them. Probably to do with the maintainer no longer actively working on the project :(

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

2 participants