Skip to content
This repository has been archived by the owner on Apr 13, 2022. It is now read-only.

[proposed spec change] subscribe to whole subtree of container #191

Closed
wants to merge 2 commits into from
Closed

[proposed spec change] subscribe to whole subtree of container #191

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f225c34
subscribe to whole subtree of container
michielbdejong Jun 18, 2019
16388f6
subcontainers and subsub and subsubsub...
michielbdejong Jun 18, 2019
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
6 changes: 3 additions & 3 deletions api-websockets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,9 +52,9 @@ pub https://example.org/data/test
Only absolute URIs should be used in both the `sub` and the `pub` message.

Subscribing to a container can also be really useful, since all CRUD operations
(POST, PUT, PATCH, DELETE) performed on resources of that container will trigger
a notification for the container URI. This makes synchronization between
multiple apps really easy.
(POST, PUT, PATCH, DELETE) performed on resources of that container and its subcontainers (recursively) will trigger
a notification for the container URI, provided the identified agent has read access to the resource
that changed. This makes synchronization between multiple apps really easy.

For example, a client subscribes to the `data/` container:

Expand Down