Dear all,
I've successfully finished an additional backend for syncevolution,
which connects to a web application using XMLRPC (using xmlrpc-c).
I'm planning to use this to connect our webmail application to an external
SyncML service, provided by O3SIS.
The file backend was used as template for the new backend, therefore
TrackingSyncSource is used.
Only four methods have to be implemented on the web application:
* listAllItems
* readItem
* insertItem
* removeItem
The URL for the web application as well as parameters like database,
username and password are configured using the evolutionsource
configuration parameter.
Even I'm no automake/autoconf expert, I've adapted the respective files,
so that my changes should integrate into the current building process
without troubles.
How would you like to integrate the new backend (which is a set of files
in their own backend directory) into the repository? May I push them back,
shall I send a patch?
Which is the preferred way to make the documentation for the configuration
as well the XMLRPC interface description?
How can I adopt the unit tests in a way, that a user configurable web
service can be set in the evolutionsource parameter?
Have a good day,
Franz
--
NEUE MOBILNUMMER: +43 660 4859550
Franz Knipp, Dipl.-Ing.
---------------------------------------------------------------------
[email protected]
+43 660 4859550
https://www.xing.com/profile/Franz_Knipp
---------------------------------------------------------------------
m-otion GmbH
Favoritenstr 4-6/III, 1040 Wien
+43 1 205705 (Fax 99)
---------------------------------------------------------------------
www.m-otion.com
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
