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-via and `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.
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.