Closed Bug 362645 Opened 18 years ago Closed 13 years ago

Google Calendar Provider: Support for Optimistic Concurrency

Categories

(Calendar :: Provider: GData, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Fallen, Assigned: Fallen)

References

()

Details

Google implements Optimistic concurrency. See URL for details. This needs to be considered for the Google Calendar provider.

In short, if the event has been changed remotely and the client wants to update an older version, a 409 Conflict HTTP response is returned from google. The event details need to be updated and potential conflicts need to be resolved before sending the event again with the new edit URI.

Trivial changes can be merged between events, but remote changes that concern fields that were changed locally need to be blessed by the user. This goes into event syncronization and could potentially use the same code. It just need to be written first.
Component: Internal Components → Provider: GData
QA Contact: base → gdata-provider
I would suggest the same handling like we have (or ought to have) for the other providers -> get before put and if the event is different only write after confirmation. I wouldn't check for event-details...
I have no code written for this bug. Assigning back to nobody to clean up my bug lists.
Assignee: philipp → nobody
This was fixed by bug 697553
Assignee: nobody → philipp
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0
Depends on: 697553
You need to log in before you can comment on or make changes to this bug.