You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 24, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 24, 2026. It is now read-only.
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.
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.
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.
Activity
mcollina commentedon 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 commentedon Sep 17, 2020
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 commentedon Sep 18, 2020
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?