There are changes in the Object API in SDK 2.1 ESD #2 (the changes were introduced in SDK 2.1 ESD #1 for Android). If your application is built with an earlier version of the SDK, update your application to include the required or recommended API changes.
Sybase Unwired Platform now supports and requires clients to use the Application APIs to manage mobile application registrations, application connections, and context. These APIs are provided in the Application (or SUPApplication) class.
Sybase Unwired Platform supports a new ApplicationCallback interface that is invoked by events of interest to a mobile application.
Sybase Unwired Platform supports new large attribute APIs to allow clients to import large messages containing binary objects (BLOBs) from the server or send a replay message without using excessive memory or throwing exceptions.
These new classes support large attributes:
(Not available in SDK version 2.1 ESD #2 for iOS). New change log APIs allow a client to retrieve entity changes from the backend. If a client application already has a list view constructed, it simply needs to add, modify, or delete entries in the list according to the change logs.
(Not available in SDK version 2.1 ESD #2 for iOS). Asynchronous Operation Replay allows users to submit changed data outside a synchronization session without waiting for EIS execution. When an application calls submitPending on an MBO on which a create, update, or delete operation is performed, an operation replay record is created on the device local database.
New methods in the connection profile support managing the encryption key for the local client database.
(Not available in SDK version 2.1 ESD #2 for iOS). Sybase Unwired Platform now supports using a messaging channel to send change notifications from the server to the client device. Clients receive device notifications when a data change is detected for any of the MBOs in the synchronization group to which they are subscribed. By default, change notification is disabled. You can enable the change notification through setting properties in the synchronization group.
The Messaging Client APIs (SUPMessageClient interface) are removed. If your application uses the SUPMessageClient interface, you must rewrite it to use functionality from SUPApplication.