Package SyncMl

A SyncML Backend provides the interface between the SyncML protocol and an actual calendar or address book application. This "actual application" is called the "data store" in this description.

The Horde_SyncMl_Command class provides a base class for handling all commands.

The Horde_SyncMl_Command_Alert class provides a SyncML implementation of the Alert command as defined in SyncML Representation Protocol, version 1.1, section 5.5.2.

The Horde_SyncMl_Command_Final class provides a SyncML implementation of the Final command as defined in SyncML Representation Protocol, version 1.1, section 5.1.7.

The Horde_SyncMl_Command_Get class provides a SyncML implementation of the Get command as defined in SyncML Representation Protocol, version 1.1, section 5.5.7.

The Horde_SyncMl_Command_Map class provides a SyncML implementation of the Map command as defined in SyncML Representation Protocol, version 1.1, section 5.5.8.

The Horde_SyncMl_Command_Put class provides a SyncML implementation of the Put command as defined in SyncML Representation Protocol, version 1.1, section 5.5.10.

The Horde_SyncMl_Command_Replace class provides a SyncML implementation of the Replace command as defined in SyncML Representation Protocol, version 1.1, section 5.5.11.

The Horde_SyncMl_Command_Results class provides a SyncML implementation of the Results command as defined in SyncML Representation Protocol, version 1.1, section 5.5.12.

The Horde_SyncMl_Command_Status class provides a SyncML implementation of the Status response as defined in SyncML Representation Protocol, version 1.1, section 5.4.

The Horde_SyncMl_Command_Sync class provides a SyncML implementation of the Sync command as defined in SyncML Representation Protocol, version 1.1, section 5.5.15.

The Horde_SyncMl_Command_SyncHdr class provides a SyncML implementation of the SyncHdr as defined in SyncML Representation Protocol, version 1.1, section 5.2.2.

There is one global object used by SyncML: 1) $GLOBALS['backend'] Backend to handle the communication with the datastore.

The Horde_SyncMl_DataStore class describes one of the possible datastores (i.e. databases) of the device.

The Horde_SyncMl_Device:: class provides functionality that is potentially (client) device dependant.

The Horde_SyncMl_Device_Nokia:: class provides functionality that is specific to the Nokia SyncML clients.

P800/P900/P910:

Charset: This device is able to handle UTF-8 and sends its XML packages in UTF8. However even though the XML itself is UTF-8, it expects the enclosed vcard-data to be ISO-8859-1 unless explicitly stated otherwise (using the CHARSET option, which is deprecated for VCARD 3.0)

The Horde_SyncMl_Device_Sync4JMozilla:: class provides functionality that is specific to the Sync4JMozilla Plugin. See http://sourceforge.net/projects/sync4jmozilla/

The Horde_SyncMl_Device_Synthesis:: class provides functionality that is specific to the Synthesis.ch SyncML clients.

Horde_SyncMl_DeviceInfo represents a device information set according to the SyncML specification.

The Horde_SyncMl_Property class is used to define a single property of a data item supported by the device.

The Horde_SyncMl_PropertyParameter class is used to define a single parameter of a property of a data item supported by the device.

The class Horde_SyncMl_Command_SyncElement stores information from the , and elements found inside a command.

This class creates the actual XML data and passes it on to a ContentHandler for optional WBXML encoding.