Message-Based Synchronization APIs

Message-based synchronization uses the publish/subscribe model. During a subscription, the subscriber indicates the data to be received from the publisher. When a subscription is established, the publisher must send all relevant data to the subscriber (to maintain the data state on the client).

The following operations are available when performing message based synchronization.

• Subscribe Data
  The following example shows how to notify the server of your subscription to a specific package.
• Unsubscribe Data
  If the client does not require the subscribed data, it can send an unsubscribe request to remove it. The following example shows how to notify the server to remove a subscription so it does not have to push to the application/device any longer.
• Suspend Operation
  This operation is used if the device is going offline or user has no need to receive updates for a significant amount of time. The following example shows how to notify the server to stop delivering data change notifications for a specific package.
• Resume Operation
  The Resume operation notifies the server to resume sending the data change notifications from the last suspension. All modified data since suspension is pushed the application/device.
• Recover Operation
  If data on the device is corrupted or a Resume request is rejected, you can use this operation to recover the data.
• Start Background Synchronization
  This operation starts background synchronization for the database class.
• Stop Background Synchronization
  This operation stops background synchronization for the database class.
• HasPendingOperations Operation
  The HasPendingOperation operation returns false if there are some requests that have not yet been processed by server. The following code shows how to wait until the replay operation is processed by the server.