Interface HttpTransportOptions

Group concurrent calls into JSON-RPC arrays. Disabled by default. true uses 100 calls and a zero-delay scheduling window.

Requires an endpoint that accepts JSON-RPC arrays. Even one queued call is sent as an array. Responses are matched by ID, not response order. RPC errors reject their own calls; HTTP failures affect the whole batch. No retries or fallback requests are made, including for submissions.

Batching provides no shared snapshot, execution order, or atomicity. Await dependent calls separately. Slow calls can delay other results. Cancelling one call rejects it without cancelling its peers; cancelling every call aborts the HTTP request. Cancellation cannot undo submitted work. timeoutMs starts at dispatch and covers reading the response body; the scheduling window is additional to that timeout.

Custom fetch implementation, useful for tests or non-standard runtimes.

Additional HTTP headers to include with each JSON-RPC request.

Abort the request, including response-body reading, with a TimeoutError after this many milliseconds.