The SyncML_Device:: class provides functionality that is potentially (client) device dependant.
If a sync client needs any kind of special conversion of the data sent to it or received from it, this is done here. There are two sources of information to identify an device: The first (and better) one is the DevInf device info sent by the device during a request. If DevInf is not supported or sent by the client, the Source/LocURI of the device request might be sufficent to identify it.
$Horde: framework/SyncML/SyncML/Device.php,v 1.7.2.17 2010-10-26 10:13:49 jan Exp $
Copyright 2005-2009 The Horde Project (http://www.horde.org/)
See the enclosed file COPYING for license information (LGPL). If you did not receive this file, see http://www.fsf.org/copyleft/lgpl.html.
Located in /SyncML/SyncML/Device.php (line 23)
Class | Description |
---|---|
![]() |
P800/P900/P910: --------------- Charset: This device is able to handle UTF-8 and sends its XML packages in UTF8. |
![]() |
The SyncML_Device_Sync4JMozilla:: class provides functionality that is specific to the Sync4JMozilla Plugin. See http://sourceforge.net/projects/sync4jmozilla/ |
![]() |
The SyncML_Device_Synthesis:: class provides functionality that is specific to the Synthesis.ch SyncML clients. |
![]() |
The SyncML_Device_Nokia:: class provides functionality that is specific to the Nokia SyncML clients. |
![]() |
Sync4j (www.sync4j.org) |
Converts the content received from the client for the backend.
Currently strips UID (primary key) information as client and server might use different ones.
Charset conversions might be added here too.
Converts the content from the backend to a format suitable for the client device.
Strips the UID (primary key) information as client and server might use different ones.
Charset conversions might be added here too.
Converts an UTC timestamp like "20061222T110000Z" into a local timestamp like "20061222T130000" using the server timezone.
Attempts to return a concrete SyncML_Device instance based on $driver.
Returns the guessed content type for a database URI.
When a client sends data during a sync but does not provide information about the MIME content type with this individual item, this function returns the content type the item is supposed to be in.
Returns the preferrred MIME content type of the client for the given sync data type (contacts/tasks/notes/calendar).
The result is passed as an option to the backend export functions. This is not the content type ultimately passed to the client but rather the content type presented to the backend export functions.
After the data is retrieved from the backend, convertServer2Client() can do some post-processing and set the correct content type acceptable for the client if necessary.
The default implementation tries to extract the content type from the device info. If this does not work, some defaults are used.
If the client does not provice proper DevInf data, this function may have to be overwritten to return the correct values.
Returns whether the device handles tasks and events in a single "calendar" sync.
This requires special actions on our side as we store this in different backend databases.
Returns whether to send individual status response for each Add, Delete and Replace.
Returns whether the payload data should be enclosed in a [CDATA[ section when sending via XML.
The synchronized data may contain XML special characters like &, < or >. Clients might choke when sending these embedded in XML. The data should be enclosed in [CDATA[ in these cases. This applies only to XML, not to WBXML devices.
Returns whether the device accepts datetimes only in local time format (DTSTART:20061222T130000) instead of the more robust UTC time (DTSTART:20061222T110000Z).
Documentation generated on Sun, 30 Jan 2011 05:16:46 +0000 by phpDocumentor 1.4.3