Each datastore is identified by a unique local URI, or locURI, that is relative to the device. For example the URI, "./alp/PIM/Contacts/Content" might identify the contacts datastore on an ALP device.
When a local datastore registers it must specify a unique target URI. HotSync will sync data from the datastore with remote datastores that specify the same target URI.
The ChangeMgr provides a basic object change notification mechanism for any datastore that registers a non-NULL notifyType string. Whenever an object in the datastore is successfully modified, the ChangeMgr sends a notification via the Notification Manager to any subscribers registered for notifications with the datastore's notifyType. A process that plans to make a sequence of modifications can cause a single notification to be sent for the entire sequence by using the ChangeMgr's batch modify API. AlpDatamodelChangeData specifies the notification structure. For a single modification, the notification specifies the type of change made (e.g., delete, modify or create) and the local id of the object affected. For batched modifications, the notification specifies the number of changes made. There are no uniqueness constraints for a datastore's notifyType; for example, multiple datastores may specify the same notifyType if this is convenient for users. Please refer to the datastore's design documentation for the specific notifyType string and notification usage.
Functions | |
| alp_status_t | alp_hscm_register_data_store (uint32_t userId, AlpHsDataStoreRegistrationPtr pReg) |
| Register a datastore with the ChangeMgr. | |
| alp_status_t | alp_hscm_unregister_data_store (const _TCHAR *nodeName, uint32_t userId, const _TCHAR *locURI) |
| Unregister a datastore with the ChangeMgr (NOTE: this function is not implemented). | |
|
||||||||||||
|
Register a datastore with the ChangeMgr.
|
|
||||||||||||||||
|
Unregister a datastore with the ChangeMgr (NOTE: this function is not implemented).
|
Copyright © 1999-2008 ACCESS CO., LTD. All rights reserved.