Saves one contact into the remote side.
When the overwrite_existing is true, then the descendant can overwrite an object with the
same UID on the remote side (usually used for modify). The conflict_resolution defines what to do when the remote side had
made any changes to the object since the last update.
The contact has already converted locally stored photos and logos into inline variants, thus it's not needed to call
inline_local_photos_sync by the descendant.
The out_new_uid can be populated with a UID of the saved contact as the server assigned it to it. This UID, if set, is
loaded from the remote side afterwards, also to see whether any changes had been made to the contact by the remote side.
The out_new_extra can be populated with a new extra data to save with the contact. Left it null
, to keep the same value as the extra.
The descendant can use an OUT_OF_SYNC error to
indicate that the save failed due to made changes on the remote side, and let the this resolve this
conflict based on the conflict_resolution on its own. The
OUT_OF_SYNC error should not be used when the
descendant is able to resolve the conflicts itself.
It is mandatory to implement this virtual method by the writable descendant.
| this | |
| overwrite_existing |
true when can overwrite existing contacts, false otherwise |
| conflict_resolution |
one of ConflictResolution, what to do on conflicts |
| contact |
an Contact to save |
| extra |
extra data saved with the contacts in an BookCache |
| opflags |
bit-or of EBookOperationFlags |
| out_new_uid |
return location for the UID of the saved contact |
| out_new_extra |
return location for the extra data to store with the contact |
| cancellable |
optional Cancellable object, or null |
|
Whether succeeded. |