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

Chapter 12. The SyncML Server > Data Paths in Synchronization

Data Paths in Synchronization

In designing a SyncML Server, it is important to understand the paths of dataflow from Clients to the actual back-end datastores. In some cases, all updates to data pass through the synchronization Server. Thus, from the perspective of the Server, the data has a single path from Clients to datastores, running through the Server itself. This is called single-path synchronization. In some other cases, there may be updates to data that do not pass through the synchronization Server. This is called multiple-path synchronization. These two kinds of synchronization occur commonly in real usage scenarios. The synchronization data paths have profound effects on the design of a SyncML Server, especially on the Data Management part of the Server function.

Single-Path Synchronization

Figure 12-4 shows a schematic for single-path synchronization. The individual Clients could be such diverse entities as mobile phones, PDAs, or desktop PCs. The data items being synchronized could be calendar events, email, or music files. Every update, however, must pass through the synchronization Server. This is a common scenario in many Service Provider Servers. Consumers carry mobile devices or desktop PCs and synchronize through the Server. External applications (e.g., an email Server) also update the email datastore through the synchronization Server. The basic underlying philosophy in single-path synchronization is that the synchronization Server is the central focal point of all operations. Hence, all updates must pass through the synchronization Server.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


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