Implement incremental sync (delta changes only) #9

Open
opened 2025-10-28 19:46:57 +00:00 by PhilflowIO · 0 comments
PhilflowIO commented 2025-10-28 19:46:57 +00:00 (Migrated from github.com)

Instead of full migration, sync only changed events since last run.

Requirements:

  • Use WebDAV sync tokens to detect changes
  • Only fetch/update changed objects
  • Much faster for large calendars with few changes
  • Maintain sync tokens in state file

Technical Details:

  • Use syncToken from calendar
  • On subsequent runs: Use syncToken to fetch only changes
  • tsdav's smartCollectionSync handles this internally

Related: Issue #4 (Bi-Directional Sync) - similar technology

Dependencies:

  • tsdav smartCollectionSync (see /docs/docs/smart calendar sync.md)

Estimated Effort: Medium (3-4 days)

Related to: DAV Migration CLI - Phase 2

Instead of full migration, sync only changed events since last run. **Requirements:** - Use WebDAV sync tokens to detect changes - Only fetch/update changed objects - Much faster for large calendars with few changes - Maintain sync tokens in state file **Technical Details:** - Use `syncToken` from calendar - On subsequent runs: Use `syncToken` to fetch only changes - tsdav's `smartCollectionSync` handles this internally **Related:** Issue #4 (Bi-Directional Sync) - similar technology **Dependencies:** - tsdav `smartCollectionSync` (see `/docs/docs/smart calendar sync.md`) **Estimated Effort:** Medium (3-4 days) **Related to:** DAV Migration CLI - Phase 2
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Phil/tsdav#9
No description provided.