Skip to content

Light editorial around delivery agnostic subscriptions #959

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 16, 2022
Merged

Light editorial around delivery agnostic subscriptions #959

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
77607d2
Light editorial around delivery agnostic subscriptions
benjie Jun 5, 2022
ed6ce6c
Reword to avoid introducing 'subscription stream' term
benjie Jun 11, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions spec/Section 6 -- Execution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -236,12 +236,12 @@ connectivity.
**Delivery Agnostic**

GraphQL subscriptions do not require any specific serialization format or
transport mechanism. Subscriptions specifies algorithms for the creation of a
stream, the content of each payload on that stream, and the closing of that
stream. There are intentionally no specifications for message acknowledgement,
buffering, resend requests, or any other quality of service (QoS) details.
Message serialization, transport mechanisms, and quality of service details
should be chosen by the implementing service.
transport mechanism. GraphQL specifies algorithms for the creation of the
response stream, the content of each payload on that stream, and the closing of
that stream. There are intentionally no specifications for message
acknowledgement, buffering, resend requests, or any other quality of service
(QoS) details. Message serialization, transport mechanisms, and quality of
service details should be chosen by the implementing service.

#### Source Stream

Expand Down