Skip to content

doc: clarify QUIC stream state wording#63660

Open
EduardF1 wants to merge 1 commit into
nodejs:mainfrom
EduardF1:fix/quic-doc-wording
Open

doc: clarify QUIC stream state wording#63660
EduardF1 wants to merge 1 commit into
nodejs:mainfrom
EduardF1:fix/quic-doc-wording

Conversation

@EduardF1

@EduardF1 EduardF1 commented May 30, 2026

Copy link
Copy Markdown

Summary

  • describe createBidirectionalStream() without a body as half-open instead of half-closed
  • make the same clarification for createUnidirectionalStream()
  • note explicitly that omitting body does not send a FIN immediately

Fixes #63655

Validation

  • node tools/lint-md/lint-md.mjs doc/api/quic.md

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/quic

@nodejs-github-bot nodejs-github-bot added doc Issues and PRs related to the documentations. quic Issues and PRs related to the QUIC implementation / HTTP/3. labels May 30, 2026
@EduardF1 EduardF1 force-pushed the fix/quic-doc-wording branch from 478cae7 to a9a4f4e Compare May 30, 2026 12:31
@EduardF1 EduardF1 changed the title doc: fix half-closed wording in quic createBidirectionalStream and createUnidirectionalStream doc: clarify QUIC stream state wording May 30, 2026
@EduardF1 EduardF1 force-pushed the fix/quic-doc-wording branch from a9a4f4e to 6f7ce01 Compare June 4, 2026 00:07
…ted, no FIN is sent immediately and the writable side remains open. Describing that state as "half-closed" (or, for unidirectional streams, "closed immediately") is therefore misleading. Update both `createBidirectionalStream()` and `createUnidirectionalStream()` to describe the stream as half-open and explicitly note that no FIN is sent immediately. Fixes nodejs#63655  Signed-off-by: Eduard Fischer-Szava <fischer_eduard@yahoo.com>
@EduardF1

EduardF1 commented Jun 4, 2026

Copy link
Copy Markdown
Author

Friendly ping — just checking in on this documentation clarification. Happy to make any changes if needed!

@Qard

Qard commented Jun 5, 2026

Copy link
Copy Markdown
Member

Note that half-open and half-closed generally have different meanings in networking. Half-open is a failure case, implying one side has crashed or broken somehow. Half-closed implies one side was explicitly/intentionally closed, but the other remains open for listening, this exact scenario.

@EduardF1

EduardF1 commented Jun 6, 2026

Copy link
Copy Markdown
Author

Hi @Qard, thank you for the feedback on the terminology. You make a great point regarding 'half-open' implying a failure state in networking contexts vs 'half-closed' implying intentional closure of one stream direction. I will update the documentation to explicitly use 'half-closed' instead to avoid any ambiguity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Issues and PRs related to the documentations. quic Issues and PRs related to the QUIC implementation / HTTP/3.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

quic: Wording docu createBidirectionalStream (and uni)

4 participants