Skip to content

Event stream: Allow empty messages #18

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

Open
vvilimek wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Event stream: Allow empty messages #18

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 5 additions & 2 deletions draft-ietf-core-comi.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -705,8 +705,11 @@ Reception of notification instances is enabled with the CoAP Observe
{{RFC7641}} function. Clients subscribe to the notifications by sending a
GET request with an "Observe" option to the stream resource.

Each response payload carries one or multiple notifications. The number of
notifications reported, and the conditions used to remove notifications
Each response payload carries zero or more notifications. Sending event
stream messages without any notifications may be useful as a reponse to
subscribing request (GET with Observe(0) Option) or as a periodic heartbeat.
However it is not recommended to send messages without any notification if there is not reason to.
The number of notifications reported, and the conditions used to remove notifications
from the reported list are left to implementers.
When multiple notifications are reported, they MUST be ordered starting from
the newest notification at index zero. Note that this could lead to
Expand Down
Loading