synce(7) [sunos man page]
SynCE(7) http://www.synce.org/ SynCE(7) NAME
SynCE - A project for connecting to devices running Microsoft Windows Mobile. DESCRIPTION
The SynCE project aims to provide libraries and tools to connect to and synchronise with PDA's and other devices running Microsoft Windows Mobile, or Windows CE. The main components include :- libsynce Core library that provides various support services and functions. librapi2 Core library implementing the RAPI protocol, equivalent to rapi.dll on a Windows OS. RAPI is used for most kinds of interaction with a WM device. This library actually implements two versions of the protocol. RAPI 1 is used for devices up to and including CE 5.0, with RAPI 2 coming into use from 5.1 (WM5). librra Library implementing RRA (Remote Replication Agent), a protocol used for synchronisation. This protocol is used for all data synchronisa- tion until WM5, at which point Airsync is used for the majority. RRA is still used for file synchronisation however. dccm The dccm daemon negotiates the initial connection with a WM device, and may provide keep-alive signals and client connections, depending on the device version and flavour of dccm. There have been a number of dccm 'flavours'. The original, also known as synce-dccm, is now considered obsolete and should not be used. Vdccm is a natural progression of dccm which is not greatly used anymore. Odccm is the most common in use at the moment, and uses dbus to provide connections to both legacy and modern devices. Hal-dccm is a new option that integrates the dccm functionality into hal to provide a more platform consistent interface. The following steps are required to get started with SynCE: (1) Ensure the rndis kernel module or a serial connection mechanism is installed To use advanced network features (rndis) with a WM5 or later device, which is recommended, you must use the usb-rndis-[lite|ng] driver from SynCE. For older devices or to use serial with WM5, if synce-hal is not used you will require the synce-serial package. You will of course also need a dccm daemon, synce-hal or odccm is recommended. (2) Start the connection daemon (as root) If using odccm, this daemon must run as the root user. With synce-hal, dccm will be started as required. Older dccm implementations must be run as your user. (3) Run tools that access the device (as user) See for example pls(1) and pcp(1). See http://www.synce.org/ for more information about the SynCE project. AUTHOR
This manual page was written by David Eriksson <twogood@users.sourceforge.net>. It was later updated by Jonny Lamb <jonnylamb@jonny- lamb.com> and Mark Ellis <mark@mpellis.org.uk>. SEE ALSO
odccm(1) The SynCE project November 2002 SynCE(7)
Check Out this Related Man Page
RAPI_CONNECTION_FROM_NAME(3) http://www.synce.org/ RAPI_CONNECTION_FROM_NAME(3) NAME
rapi_connection_from_name - obtain connection for RAPI function calls SYNOPSIS
#include <rapi.h> RapiConnection *rapi_connection_from_name(const char *device_name); RapiConnection *rapi_connection_from_info(SynceInfo *info); void rapi_connection_select(RapiConnection *connection); void rapi_connection_destroy(RapiConnection *connection); HRESULT CeRapiInit(); STDAPI CeRapiUninit(); DESCRIPTION
The rapi_connection_from_info() function returns a pointer to a newly allocated RapiConnection struct, used for remote function calls to a mobile device. The RapiConnection keeps a pointer to the SynceInfo struct but does not copy it, therefore freeing the SynceInfo before the RapiConnection is not recommended. rapi_connection_from_name() accomplishes the same for the connected device named device_name. Refer to synce_info_new(3) for insight on how this name and the connection daemon in use can affect the device contacted. rapi_connection_select() allows for selection between multiple active connections. NULL can be passed to result in no active connection. rapi_connection_destroy() frees a RapiConnection. This should not be called before CeRapiUninit(). CeRapiInit() connects the current RapiConnection to it's mobile device. If already initialised, CERAPI_E_ALREADYINITIALIZED is returned. CeRapiUninit() destroys the connection for the current RapiConnection. The RapiConnection cannot be re-initialised, it must be destroyed. An example of using multiple devices follows. /* * SynCE support for switching between multiple devices * * Example code for two devices follows! * * It shows two different ways to get a RapiConnection object. * */ RapiConnection* a = rapi_connection_from_name("device_a"); rapi_connection_select(a); CeRapiInit() SynceInfo* info_b = synce_info_new("device_b"); RapiConnection* b = rapi_connection_from_info(info_b); rapi_connection_select(b); CeRapiInit() rapi_connection_select(a); ...some RAPI calls to device A... rapi_connection_select(b); ...some RAPI calls to device B... rapi_connection_select(a); CeRapiUninit(); rapi_connection_destroy(a); rapi_connection_select(b); CeRapiUninit(); rapi_connection_destroy(b); synce_info_destroy(info_b); RETURN VALUE
rapi_connection_from_name() and rapi_connection_from_info() return a pointer to a new RapiConnection. CeRapiInit() and CeRapiUninit() return S_OK on success or an error code on failure. AUTHOR
This manual page was written by Mark Ellis <mark_ellis@users.sourceforge.net>. SEE ALSO
synce(7), synce_info_new(3), odccm(1), vdccm(1) The SynCE Project 2007-08-26 RAPI_CONNECTION_FROM_NAME(3)