-
Notifications
You must be signed in to change notification settings - Fork 27
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
discuss the future of HTTP client and Undici #66
Comments
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. |
Can we close this since we did cover it in the meeting? Or do you want to use this to track the ongoing discussion? |
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? |
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.
The text was updated successfully, but these errors were encountered: