nextcloud / nextcloud/server

Webdav propfind: use revision similar like caldav

Open
#38,669 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage client: 💻 desktop client: 🤖🍏 mobile enhancement feature: dav hotspot: file transfer performance performance 🚀
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

I currently cannot find the RFC, but it exists somewhere in internet.
Idea is that

  • client sends revision 40 of a folder to server
  • server maintains a changelog of this folder
  • server compares 40 to latest revision, e.g. 50
  • servers sends an reponse, with 3 updates, 2 removals, 1 addition

This way the transferred size is much smaller and clients only need to pare small amount of results.

@AndyScherzinger as discussed. I tried to find the corresponding RFC

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the WebDAV PROPFIND entry point and comparing it with the existing CalDAV revision handling. Verify the relevant RFC or protocol design, then determine how folder changelogs, revision comparison, additions, updates, and removals should be represented in the response. Done means an agreed protocol and implementation scope, with tests covering incremental results.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.