Sync framework vocabulary

Sync framework vocabulary

This vocabulary lists and defines concepts and terms involved in Microsoft sync framework.

Terms

Batching)

It is divided into several groups to send changes, rather than transmitting all data at one time.

Change Unit)

The minimum unit for tracking changes in the storage area. The change unit is included in the item, such as the name and address fields in the contact item. Only the units that have changed are sent when a change is disseminated. When detecting a conflict, only changes made to the same change organization are considered as conflicts.

Client)

Services and applications to be integrated into the sync framework architectureProgramOr device.

Clock Vector)

Indicates the updated copy key/tick count pair for the copy. Any change between 0 and the tick count will be included in the vector.

Conflict Resolution Method)

The method used to determine which change is written to the storage zone in case of a conflict. Generally, the solution to the conflict is as follows: the writer wins, the source wins, the target wins, the custom solution, or the delay solution. For a custom solution, resolve the conflict in the application's read conflict logs and select a solution. For latency resolution methods, records conflicting change data and the generation knowledge of changes at the same time.

Consistency Unit)

The minimum unit of consistency. Because all changes with the same consistency units are sent together, the synchronization will not be interrupted when only a portion of the consistency units are applied.

Flexible identifier)

The identifier assigned to various synchronization entities (such as copies. The length of an identifier can be fixed or variable.

Global identifier)

The unique identifier assigned to the data item. The identifier must be unique on all clients. A global identifier is a mutable identifier, so it can be in any format. The format is generally guid and 8-byte prefix.

Item)

The unit of the data or metadata being synchronized. The general items of data may be files or records, and the general items of metadata may be knowledge items.

Made-with knowledge)

The current knowledge of the source copy to be used in the conflict detection. Generate knowledge to answer the following questions: What do you knoW When performing these changes?

Learned knowledge)

The current knowledge about the source copy of a specific group of changes and conflict information about the copy recorded. Known Knowledge answers the following questions: what information will be obtained when this batch of changes is applied?

Knowledge)

Metadata maintained by each participant to describe all changes that they know. When using the simplest form (watermark), the Knowledge item is a clock vector consisting of several pair of copy keys and copy tick counts.

Participant)

A provider and its related copies.

Range)

A group of continuous item identifiers that apply the same clock vector. The range is represented by the start point, end point, and the clock vector applied to all IDs between the start and end points.

Replica)

The specified repository for the information to be synchronized.

Copy ID (replica ID)

The value that uniquely identifies the copy.

Replica key)

Ing to the 4-byte value of the copy ID in the copy key ing.

Scope)

The set of data being synchronized.

Synchronization Application)

Software components such as the personal information manager or music database are used to hold synchronization sessions and call synchronization providers to synchronize different data storage.

SynchronizationCommunity(Synchronization Community)

A group of copies that keep data synchronized with each other.

Synchronization provider)

The software component that represents the synchronized copy. As the source, it enumerates the changes of its own copy. As the target, it applies the change to its own copy. When the data format does not match, it performs the required architecture conversion.

Synchronization session)

One-way synchronization in which the source provider enumerates its own changes and sends them to the target provider. The target provider applies the changes to its own storage zone.

Tick count (tick count)

A specific monotonically incrementing number of a copy. It forms a version together with the copy key.

Logical deletion (tombstone)

Used to mark deleted items. Logical deletion is used to track deleted items and prevent re-introducing them to the synchronization community.

Version)

Metadata that identifies the revision of an item. It consists of the copy key and the copy tick count of the item.

See Other resources

Microsoft sync framework