Skip to content

Remove NYM mixFetch per-host queue#712

Open
bobbythelobster wants to merge 3 commits intoEdgeApp:masterfrom
bobbythelobster:claudine/remove-nym-mixfetch-queue
Open

Remove NYM mixFetch per-host queue#712
bobbythelobster wants to merge 3 commits intoEdgeApp:masterfrom
bobbythelobster:claudine/remove-nym-mixfetch-queue

Conversation

@bobbythelobster
Copy link

Summary

  • remove custom per-host request serialization in
  • keep export as a thin pass-through to
  • remove stale comments at NYM callsites in browser/react-native IO
  • add changelog note under Unreleased

Why

was upgraded in 2.43.1 for native concurrency improvements. Keeping our own host queue can unnecessarily serialize NYM traffic and increase timeout risk.

Validation

Risk

  • behavior changes from serialized per-host to library-managed concurrency; relies on current mix-fetch behavior.

The @nymproject/mix-fetch library now handles concurrency natively,
so the custom per-host serialization queue is no longer needed.
queueMixFetch is now a thin pass-through to mixFetch.

Made-with: Cursor
src/util/nym.ts Outdated
* mixFetch only allows one concurrent request per host, so we chain them.
* Thin wrapper around mixFetch with pre-configured options.
*/
export async function queueMixFetch(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need queueMixFetch at all. We can just inline mixFetch where queueMixFetch is being invoked.

Remove the queueMixFetch wrapper from util/nym and call mixFetch
inline at browser and react-native NYM call sites.

This follows PR feedback and reduces unnecessary abstraction
while keeping initMixFetch setup behavior unchanged.
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

Successfully merging this pull request may close these issues.

2 participants