• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 2. SyncML: An Introduction > An Overview of SyncML

An Overview of SyncML

Logically, synchronization between two applications requires the sharing of changes that the applications have made to data common to both applications. Synchronization also involves potential reconciliation of conflicting changes made concurrently. If applications can represent what has changed in a manner that is mutually understood, and are able to communicate those changes in an agreed upon fashion, they can synchronize their data. SyncML is primarily based upon this observation. Naturally, the two fundamental parts of the SyncML data synchronization specification are the SyncML Representation Protocol and the SyncML Synchronization Protocol. The Representation Protocol is essentially the syntax for specifying the changes that an application has made to its data. The Synchronization Protocol is the specification of the sequence of packages that applications must exchange in order to communicate their changes to each other.

Figure 2-2 illustrates the scope of the SyncML framework. The framework encompasses the Representation Protocol, the Synchronization Protocol, and the various transport bindings such as Hyper Text Transfer Protocol (HTTP) [RFC2616] and Object Exchange Protocol (OBEX™) [OBEX99]. The framework also includes elements of the SyncML reference implementation, such as the SyncML API and the SyncML adapter. The SyncML framework, however, does not include other synchronization-related programs, such as application, synchronization engine, and synchronization agent, that drive the framework. Instead, the framework assumes their existence.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint