Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

discuss the future of HTTP client and Undici #66

Closed
ghermeto opened this issue Sep 3, 2020 · 3 comments
Closed

discuss the future of HTTP client and Undici #66

ghermeto opened this issue Sep 3, 2020 · 3 comments

Comments

@ghermeto
Copy link
Contributor

ghermeto commented Sep 3, 2020

I would like to have a discussion with @ronag or @mcollina about the future of HTTP client and Undici (which just moved to Node.js) with us and how it aligns with the future HTTP technical plans we have been discussing.

@mcollina
Copy link
Member

mcollina commented Sep 3, 2020

I might not have much time for meetings unfortunately. Undici was born as an experiment to measure the overhead of the current agent-based http client. It turns out that it can deliver quite an amazing throughput increase.

@ronag improved it impressively, and I think it's now very stable.

The idea would be to have something like that in core.

@wesleytodd
Copy link
Member

Can we close this since we did cover it in the meeting? Or do you want to use this to track the ongoing discussion?

@ghermeto
Copy link
Contributor Author

I think it would be important to align with @jasnell where sees Undici fitting on his long term plans before closing this issue.

My impression from the meeting was that @mcollina isn't bullish on Undici API and the concepts behind Undici are more important than the API, so we might leave this issue open until that discussion happens.

Thoughts?

@sheplu sheplu closed this as completed Feb 27, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

4 participants