Overview

Packages

  • None
  • SyncMl

Classes

  • Horde_SyncMl
  • Horde_SyncMl_Backend
  • Horde_SyncMl_Backend_Horde
  • Horde_SyncMl_Command
  • Horde_SyncMl_Command_Alert
  • Horde_SyncMl_Command_Final
  • Horde_SyncMl_Command_Get
  • Horde_SyncMl_Command_Map
  • Horde_SyncMl_Command_Put
  • Horde_SyncMl_Command_Replace
  • Horde_SyncMl_Command_Results
  • Horde_SyncMl_Command_Status
  • Horde_SyncMl_Command_Sync
  • Horde_SyncMl_Command_SyncHdr
  • Horde_SyncMl_ContentHandler
  • Horde_SyncMl_DataStore
  • Horde_SyncMl_Device
  • Horde_SyncMl_Device_Nokia
  • Horde_SyncMl_Device_P800
  • Horde_SyncMl_Device_sync4j
  • Horde_SyncMl_Device_Sync4JMozilla
  • Horde_SyncMl_Device_Synthesis
  • Horde_SyncMl_DeviceInfo
  • Horde_SyncMl_Property
  • Horde_SyncMl_PropertyParameter
  • Horde_SyncMl_State
  • Horde_SyncMl_Sync
  • Horde_SyncMl_SyncElement
  • Horde_SyncMl_Translation
  • Horde_SyncMl_XmlOutput
  • Overview
  • Package
  • Class
  • Tree

Class Horde_SyncMl_Device_P800

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)

Encoding: String values are encoded "QUOTED-PRINTABLE"

Other: This devices handles tasks and events in one database.

As the P800 was the first device to work with package, most of the required conversions are in Device.php's default handling.

Copyright 2005-2012 Horde LLC (http://www.horde.org/)

See the enclosed file COPYING for license information (LGPL). If you did not receive this file, see http://www.horde.org/licenses/lgpl21.

Horde_SyncMl_Device
Extended by Horde_SyncMl_Device_P800
Package: SyncMl
Author: Karsten Fourmont karsten@horde.org
Located at Horde/SyncMl/Device/P800.php
Methods summary
public array
# convertClient2Server( string $content, string $contentType )

Convert the content.

Convert the content.

Parameters

$content
The content to convert.
$contentType
The contentType of the content.

Returns

array

array($newcontent, $newcontentType): the converted content and the (possibly changed) new ContentType.

Overrides

Horde_SyncMl_Device::convertClient2Server()
public array
# convertServer2Client( string $content, string $contentType, string $database )

Converts the content from the backend to a format suitable for the client device.

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.

Parameters

$content
The content to convert
$contentType
<p>The content type of content as returned from the backend</p>
$database
The server database URI.

Returns

array

Three-element array with the converted content, the (possibly changed) new content type, and encoding type (like b64 as used by Funambol).

Overrides

Horde_SyncMl_Device::convertServer2Client()
public boolean
# handleTasksInCalendar( )

Some devices like the Sony Ericsson P800/P900/P910 handle vtodos (tasks) and vevents in the same "calendar" sync. This requires special actions on our side as we store this in different databases (nag and kronolith). This public function could directly return true but tries to be a bit more generic so it might work for other phones as well.

Some devices like the Sony Ericsson P800/P900/P910 handle vtodos (tasks) and vevents in the same "calendar" sync. This requires special actions on our side as we store this in different databases (nag and kronolith). This public function could directly return true but tries to be a bit more generic so it might work for other phones as well.

Returns

boolean

True if tasks and events are processed in a single request.

Overrides

Horde_SyncMl_Device::handleTasksInCalendar()
public boolean
# omitIndividualSyncStatus( )

Send individual status response for each Add,Delete,Replace. The P800 class of devices seem to have trouble with too many status responses. So omit them for these (and only these),

Send individual status response for each Add,Delete,Replace. The P800 class of devices seem to have trouble with too many status responses. So omit them for these (and only these),

Returns

boolean
False if individual status responses should be send.

Overrides

Horde_SyncMl_Device::omitIndividualSyncStatus()
Methods inherited from Horde_SyncMl_Device
factory(), getPreferredContentType(), getPreferredContentTypeClient(), useCdataTag(), useLocalTime()
Properties inherited from Horde_SyncMl_Device
$requestedContentType
API documentation generated by ApiGen