Skip to content

docs(client.tcp): requests are pipelined over a connection, not handled concurrently - #2

Merged
dmitrat merged 1 commit into
mainfrom
docs/tcp-readme-per-connection-order
Sep 7, 2026
Merged

dmitrat merged 1 commit into
mainfrom
docs/tcp-readme-per-connection-order

Conversation

@dmitrat

@dmitrat dmitrat commented Sep 7, 2026

Copy link
Copy Markdown
Owner

Why

WitCloud roadmap review (@Docs/Roadmap/REVIEW-2026-09-03-roadmap-verification.md) verified the design documents against the code and found this README sentence contradicted by the implementation. The WitCloud plan tracks the correction as P0.0 (f).

What

One bullet reworded so the README states what the code does. No code change.

🤖 Generated with Claude Code

…ed concurrently

The README said multiple requests and responses are handled concurrently
over a single connection. The client does keep many requests in flight,
but the server processes a connection's requests one at a time in arrival
order (per-connection inbound queue and send lock, server-wide cap), so a
connection's throughput is bounded by handler time - about 1 000 light
requests per second measured against a WitCloud gateway on the 3.x line -
and independent connections scale in parallel. WitCloud roadmap review
R4 / P0.0 (f).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@dmitrat
dmitrat merged commit 35bf0b3 into main Sep 7, 2026
2 checks passed
@dmitrat
dmitrat deleted the docs/tcp-readme-per-connection-order branch September 7, 2026 05:26
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.

1 participant