6.0.0-git
2018-12-15

[#9412] SYNCML Alert Code 203 wrong implemented
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 2010-11-29 (2938 days ago)
Due
Updated 2011-08-26 (2668 days ago)
Assigned 2011-07-02 (2723 days ago)
Resolved 2011-07-30 (2695 days ago)
Milestone
Patch No

History
2011-08-26 10:14:26 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.
2011-07-30 12:06:38 Jan Schneider Type ⇒ Enhancement
State ⇒ Stalled
Priority ⇒ 1. Low
 
2011-07-30 12:06:24 Jan Schneider Comment #3
State ⇒ Stalled
Reply to this comment
Stalled until someone has a bright idea how to implement this.
2011-07-02 17:16:56 Jan Schneider Comment #2
State ⇒ Feedback
Version ⇒ Git master
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?
2010-11-29 11:16:51 info (at) ionum (dot) ch Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ SYNCML Alert Code 203 wrong implemented
Queue ⇒ Synchronization
Milestone ⇒
Patch ⇒ No
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.

Saved Queries