seconsdkcrkeys.h File Reference



Detailed Description

A CenRep interface for last used sync solutions.

Purpose:

Calendar/contact data easily gets corrupted if a user is using several remote synchronization solutions at the same time. The purpose of this API is to provide the synchronization solution vendors a way to

API Description:

Synchronizing content over several mechanisms from the device causes easily difficult problems, as the different protocols and systems are not aware of each other.

For example, a synchronization solution using standard OMA DS technology is not aware of the simultaneous existence of some proprietary synchronization (aka. mobile PIM) solution, and vice versa. This is likely to cause problems, as the users may not be aware of the side effects that may occur from using several such solutions at the same time. Currently the problem is recognized by the vendors, and device applications do their best to warn user from using any other synchronization solution than the one being installed.

This API intends to enhance the warning mechanism in two ways:

This is achieved with a simple setting API utilizing Symbian OS Central Repository.

Use cases:

The use cases supported by this API are:

  1. Detect currently active synchronization solution
    • When a synchronization solution is about to take some supported content type into use, it should check whether there is some other Uid already present in the setting. If there isn’t, the solution should put it’s own Uid into the setting value. If there is some unknown Uid, the setting should be aware that it’s changelog for that particular content may be out-of-date, and a full re-sync should be issued. It’s up to the solution vendor to decide, whether the user should be notified about this. The user readable name of the active solution is readable using Symbian AppArc API method
       RApaLsSession::GetAppInfo() 
      
  2. Activate a synchronization solution for certain content type
    • This use case allows the synchronization solution to register it’s Uid into the Central Repository. This information is used by other compliant solutions to find out the active solution for all supported content types
Using the Synchronization Capability API:
  1. Detect currently active synchronization solution
  2. Activate a solution for the content type
  3. Error handling

Go to the source code of this file.


Variables

const TUid KCRUidSecon = {0x2000F83D}
 Repository Uid.
const TUint32 KSeconCalendarUid = 0x00000001
 Calendar Uid Setting Integer.
const TUint32 KSeconCalendarTime = 0x00000002
 Calendar Time Setting Integer.
const TUint32 KSeconContactsUid = 0x00000003
 Contacts Uid Setting Integer.
const TUint32 KSeconContactsTime = 0x00000004
 Contacts Time Setting Integer.
const TUint32 KSeconSmsUid = 0x00000005
 Sms Uid Setting Integer.
const TUint32 KSeconSmsTime = 0x00000006
 Sms Time Setting Integer.
const TUint32 KSeconBookmarkUid = 0x00000007
 Bookmark Uid Setting Integer.
const TUint32 KSeconBookmarkTime = 0x00000008
 Bookmark Time Setting Integer.

Variable Documentation

const TUid KCRUidSecon = {0x2000F83D}
 

Repository Uid.

Contains settings for the supported content types. Each setting is integer, which is to hold either the Application Uid or the package Uid of the active solution.

const TUint32 KSeconBookmarkTime = 0x00000008
 

Bookmark Time Setting Integer.

const TUint32 KSeconBookmarkUid = 0x00000007
 

Bookmark Uid Setting Integer.

const TUint32 KSeconCalendarTime = 0x00000002
 

Calendar Time Setting Integer.

const TUint32 KSeconCalendarUid = 0x00000001
 

Calendar Uid Setting Integer.

const TUint32 KSeconContactsTime = 0x00000004
 

Contacts Time Setting Integer.

const TUint32 KSeconContactsUid = 0x00000003
 

Contacts Uid Setting Integer.

const TUint32 KSeconSmsTime = 0x00000006
 

Sms Time Setting Integer.

const TUint32 KSeconSmsUid = 0x00000005
 

Sms Uid Setting Integer.


Copyright © Nokia Corporation 2001-2007
Back to top