From 91d808ed099faf395ce6f040102f9de3acd2678e Mon Sep 17 00:00:00 2001 From: Ricki Hirner Date: Sat, 8 Mar 2025 17:56:52 +0100 Subject: [PATCH] Update abstract --- abstract.md | 4 ++-- content.mkd | 2 +- webdav-push.mkd | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/abstract.md b/abstract.md index f5677cd..8aba253 100644 --- a/abstract.md +++ b/abstract.md @@ -1,3 +1,3 @@ -This document specifies a protocol to notify WebDAV clients over push (vs. polling) when contents of a collection are changed on the WebDAV server. +This document specifies a protocol to notify WebDAV clients over push notifications when contents of a collection are changed on the WebDAV server. -The protocol is intended to work with any push transport, however additional details are needed for each transport. Details for Web Push as a push transport are specified in the document. +The protocol is primarily specified to be used with Web Push (RFC 8030), but can be used with other transports as well. diff --git a/content.mkd b/content.mkd index 8fa0158..011910a 100644 --- a/content.mkd +++ b/content.mkd @@ -5,7 +5,7 @@ WebDAV-Push is intended as a tool for WebDAV {{RFC4918}} clients to get notified about updates in collections in near time so that they can refresh their views, perform synchronization etc. -A client SHOULD NOT rely solely on WebDAV-Push, so it should also perform regular polling like when WebDAV-Push is not available. However if WebDAV-Push is available, the polling frequency can be significantly reduced. +A client MUST NOT rely solely on WebDAV-Push, so it should also perform regular polling like when WebDAV-Push is not available. However if WebDAV-Push is available, the polling frequency can be significantly reduced. Typical use cases: diff --git a/webdav-push.mkd b/webdav-push.mkd index d718fd4..2555d57 100644 --- a/webdav-push.mkd +++ b/webdav-push.mkd @@ -1,5 +1,5 @@ --- -title: Push for WebDAV +title: Push for WebDAV (WebDAV-Push) abbrev: WebDAV-Push docname: draft-bitfire-webdav-push-00 category: exp