New or changed features for native client Object API development include using Afaria certificates for device authentication and standalone Afaria libraries; writing to the database while synchronizing; synchronization parameter enhancements; consuming a native (push) notification; tracking KPIs; performing end-to-end trace from the device client; and supporting HTTPS. Customization resource bundles are now available for Object API applications; message text can be localized and customized; and BlackBerry signing is handled through a new API.
Documented in: Developer Guide: <Device Platform> Object API Applications (Android and iOS only), see Using Certificates from Afaria for Authentication
Standalone Afaria libraries are now used with Sybase Mobile SDK.
A new connection profile property lets developers use multiple threads to write to the database while synchronizing.
Documented in: Developer Guide: <Device Platform> Object API Applications, see Setting Up the Connection Profile
In earlier versions, synchronization parameter values were cumulative. Calling [MBO]SynchronizationParameter.save() twice produced two synchronization parameters values, with no way to query all current (cumulative) values, and update them (except using delete all ! and add again). You can now use the methods in [MBO]Subscription class to perform create, update, or delete functions for all active synchronization parameter sets.
Documented in: Developer Guide: <Device Platform> Object API Applications, see Managing Synchronization Parameters
Documented in: Developer Guide: <Device Platform> Object API Applications, see Nonblocking Synchronization
You can consume a native push notification on the device using the native device operating system.
When a push notification is received, the onPushNotification method is invoked. You can add logic to handle the notification.
Documented in: Developer Guide: <Device Platform> Object API Applications, see: ApplicationCallback API
Object API clients for Android, BlackBerry, and iOS can access performance libraries through a new PerformanceAgentService interface, for tracing or collecting key performance indicators (KPIs).
Performance data is written to a log file on the device. The administrator can retrieve the performance log through Sybase Control Center.
Documented in: Developer Guide: <Device Platform> Object API Applications (Android, BlackBerry, and iOS), see Tracking KPI
Developers can now use the API to enable users to initiate end-to-end tracing from the device client side.
Documented in: Developer Guide: <Device Platform> Object API Applications, see Debugging Runtime Errors and Performance Analysis
HTTPS support is now available for messaging and replication clients that use messaging communications between the messaging client and server. Previously, HTTPS communication was available only through Relay Server. Some minimal client code change and server setup is required.
Customization resource bundles are now available for Object API applications (Android, BlackBerry, iOS, Windows, and Windows Mobile). This enables you to provision applications using metadata rather than recompiling code; gives you more configuration and versioning control over applications; and enables you to deliver packaged applications that are configurable and extensible.
The Object API message text used in end-user application-visible error messages can be localized and customized.
A new API [setApplicationIdentifier (String value, signerId)] has been introduced for signing BlackBerry applications. The API is based on the BlackBerry Password Based Code Signing Authority tool.