Table of Contents
Advertisement
Figure 4 SyncML architecture
Benefits of a common synchronization
protocol
•
End users
Today's user of mobile devices probably
uses a different synchronization product
with every device. Each technology can
synchronize only a few applications, or is
limited to a particular type of network con-
nection. This arrangement is expensive to
install, confusing to configure and operate,
and costly to administer. With SyncML,
users will be able to buy devices that syn-
chronize with a broader range of data.
•
Device manufacturers
Device manufacturers will benefit from a
common protocol that will make the device
interoperable with a broader range of appli-
cations, services, and network and trans-
mission technologies.
•
Service providers
Service providers moving into the growth
arena of application hosting are particularly
concerned that a proliferation of synchroni-
zation technologies will make it impossible
to deploy and support their customers in a
cost-effective manner. To support the
range of data types and devices in use
today, service providers must install and
configure multiple server infrastructures,
maintain and support that infrastructure,
and maintain compatibility and perfor-
mance. The alternative now available, to
use a single solution for data connectivity,
involves the risk of a tight coupling to a
propriety solution. With SyncML, they will
be able to provide connectivity to a wider
selection of applications.
•
Application developers
Choosing to support multiple synchroniza-
tion technologies enables an application to
support more types of devices and net-
worked data, but that choice comes at a
cost. With SyncML, application developers
will be able to develop an application that
can connect to a more diverse set of
devices and network data.
T68i
White Paper, April 2002
18
Advertisement
Table of Contents
