Potential support for webdav-push?

[CiaranG]

I'm wondering if anyone has yet looked into whether it will be possible to support this proposed webdav-push protocol extension: https://github.com/bitfireAT/webdav-push/

[pbiering]

this would require persistent connections from client to server with I assume huge extension on server side (and also clients must be extended).

[lukeuser]

this would require persistent connections from client to server with I assume huge extension on server side (and also clients must be extended).

Surely that's not true, unless I'm mistaken. Radicale wouldn't be acting as the push server, it would simply be sending a message to the push server each time the data is updated. For instance, using ntfy, radicale would simply be POSTing to ntfy.sh (or a self-host).

Cf. https://f-droid.org/2022/12/18/unifiedpush.html

[pbiering]

radicale supports already a hook, feel free to use it and create a surrounding prototype of what you require.

[lukeuser]

While a hook could be used to achieve the desired functionality, the webdav-push protocol itself is more complex (the server should advertise its support, manage push subscriptions). I don't have the competency to implement this myself. I feel like providing support for this protocol at some point would make a lot of sense, since push support is a notable enhancement—it's up to you and your fellow contributors of course. Have a look at the draft specification perhaps.

https://bitfireat.github.io/webdav-push/draft-bitfire-webdav-push-00.html

[CiaranG]

I guess one next step would be to get an idea of the scale of server-side work necessary by looking at the working NextCloud implementation of this here.

[symphorien]

davx5 now supports webdav push https://github.com/bitfireAT/davx5-ose/releases/tag/v4.5-ose so client support is here.