Repository navigation
Clarify you can watch a WebSocket for a resource to be created #5
Description
Activity
See also
solid-contrib/test-suite#89NSS sends an
ackon a non-existant resource when you subscribe to it but does not send apubon creation. It sends apubwhen you delete this resource thereafter.IMHO the current spec is painful in the sense that the way to determine a new resource (say, created by someone else) when subscribing to a container would be to read its contents again and diff it against the previous contents. This puts unnecessary burden for client to track contents (such as in my use case for a recursive watcher) and extra fetch (in case one is interested in notification only) without any benefit to the server. Even something simple like emitting the HTTP verbs and the slug value, which requires almost no extra burden on the part of the server, would allow for simpler client designs.
I've transferred this issue from https://github.com/solid/solid-spec/issues/217 .
Noting that there is also solid/solid-spec#216 which seems to be duplicate of this issue - the only difference is the issue title. Leaving solid-spec's 216 as is for now but ongoing work here should take existing comments in that issue.
In the bit about live update,
https://github.com/solid/solid-spec/blob/master/api-websockets.md
we need to specify that you can subscribe to changes in a resource which currently does not exist, and get a ping when it is created (and thereafter to any changes).
The headers
Update-viaand `MS-Author-Via: are sent on 404 as well as 200.NSS sends the headers now. i haven't tested the actual WS ping message on file creation.
See also
linkeddata/rdflib.js#392 in rdflib
which is depended on by
https://github.com/solid/solid-ui/issues/228 a issue with the chat UI needing this.