Tickets :: [#9412] SYNCML Alert Code 203 wrong implemented

6.0.0-alpha10

5/14/25

Summary	SYNCML Alert Code 203 wrong implemented
Queue	Synchronization
Queue Version	Git master
Type	Enhancement
State	Stalled
Priority	1. Low
Owners
Requester	info (at) ionum (dot) ch
Created	11/29/2010 (5280 days ago)
Due
Updated	08/26/2011 (5010 days ago)
Assigned	07/02/2011 (5065 days ago)
Resolved	07/30/2011 (5037 days ago)
Milestone
Patch	No

08/26/2011 10:14:26 AM	info (at) ionum (dot) ch	Comment #4	Reply to this comment
I would only sync "my calendars" because syncml depends on a client-server model, so the database on the server-side should be the master.

07/30/2011 12:06:38 PM	Jan Schneider	Type ⇒ Enhancement State ⇒ Stalled Priority ⇒ 1. Low

07/30/2011 12:06:24 PM	Jan Schneider	Comment #3 State ⇒ Stalled	Reply to this comment
Stalled until someone has a bright idea how to implement this.

07/02/2011 05:16:56 PM	Jan Schneider	Comment #2 Version ⇒ Git master State ⇒ Feedback	Reply to this comment
This is technically correct, but I'm not sure how to implement this. Especially since we allow synchronization with more than one server resource. Should we empty all calendars/address books that are synchronized? Should we error out if a resource is read-only or just skip it?

11/29/2010 11:16:51 AM	info (at) ionum (dot) ch	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ SYNCML Alert Code 203 wrong implemented Queue ⇒ Synchronization Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
If Alert 203 is received from client, horde sync should delete all contacts and events and replace them with the client ones.