The Change Manager application API primarily consists of functions for tracking changes to logical content objects. These functions should be called by any application that needs to modify an object in a DataStore. The change manager uses the IdMgr services to generate ids for new objects.
When a DataStore registers with the Change Manager, it initializes the data structures it needs to track changes for the DataStore. If the DataStore stores its data in one of the database types supported by the Change Manager (see AlpHsSupportedDbType), then it can request local storage of the Change Manager's data. Local storage results in a performance benefit for both writes and reads.
The Change Manager allows conflicted versions of an object to be edited or deleted. Edits and deletes to conflicted objects are syncable; for example, when a conflicted version of an object in a local DataStore is modified, the modified version will replace the unmodified version at a remote DataStore the next time the two DataStores sync. An object remains conflicted until the penultimate version of its content is deleted. When a conflict is resolved in favor of a non-referenceable version of the content, the Change Manager will ask the DataStore to "rekey" the "winning" version's content to the referenceable id.
Modules | |
| Data Types | |
| API's | |
Generated on Wed Jul 30 07:06:41 2008 by Doxygen 1.4.6 for ALP SDK + Hiker Documentation
Copyright © 1999-2008 ACCESS CO., LTD. All rights reserved.