Located in /SyncML/SyncML/Sync.php (line 21)
Sync Anchors determine the interval from which changes are retrieved.
Add due to client replace request when map entry is not found. Happens during SlowSync.
Number of objects that have been sent to the server for adding.
Number of objects that have been sent to the server for deletion.
Number of objects that have been sent to the server for replacement.
Number of failed actions, for logging purposes only.
Map data is expected whenever an add is sent to the client.
List of object UIDs (in the keys) that have been added on the server since the last synchronization and are supposed to be sent to the client.
Number of objects that have been sent to the client for adding.
List of object UIDs (in the keys) that have been deleted on the server since the last synchronization and are supposed to be sent to the client.
Number of objects that have been sent to the client for deletion.
List of object UIDs (in the keys) that have been changed on the server since the last synchronization and are supposed to be sent to the client.
Number of objects that have been sent to the client for replacement.
List of task UIDs (in the keys) that have been added on the server since the last synchronization and are supposed to be sent to the client.
This is only used for clients handling tasks and events in one database. We need to seperately store the server tasks adds, so when we get a Map command from the client, we know whether to put this in tasks or calendar.
Source (server) URI (database).
State of the current sync.
A sync starts in STATE_INIT and moves on to the next state with every <Final> received from the client: STATE_INIT, STATE_SYNC, STATE_MAP, STATE_COMPLETED. STATE_MAP doesn't occur for _FROM_CLIENT syncs.
Counts the <Sync>s received by the server. Currently unused.
Counts the <Sync>s sent by the server.
The synchronization method, one of the ALERT_* constants.
Target (client) URI (database).
Completes a sync once everything is done: store the sync anchors so the next sync can be a delta sync and produce some debug info.
Creates a <Sync> output containing the server changes.
Returns the client ID of server change identified by the change type and server ID.
Here's where the actual processing of a client-sent Sync Item takes place. Entries are added, deleted or replaced from the server database by using backend API calls.
Notifies the sync that a final has been received by the client.
Depending on the current state of the sync this can mean various things: a) Init phase (Alerts) done. Next package contaings actual syncs. b) Sync sending from client done. Next package are maps (or finish or finish if ONE_WAY_FROM_CLIENT sync c) Maps finished, completly done.
Returns true if there are still outstanding server sync items to be sent to the client.
This is the case if the MaxMsgSize has been reached and the pending elements are to be sent in another message.
Sets the client ID of server change identified by the change type and server ID.
Unsets the server-client-map of server change identified by the change type and server ID.
Retrieves and condenses the changes on the server side since the last synchronization.
Converts a calendar databaseURI to a tasks databaseURI for devices with handleTasksInCalendar.
Documentation generated on Sun, 30 Jan 2011 05:22:32 +0000 by phpDocumentor 1.4.3