On Mon, 2010-05-24 at 23:12 +0100, Jeff wrote: > As people following my notes already know, I am doing some testing > trying to gain > confidence in the specific configuration of HTTP server and N900 > > It is desirable to do this in the most efficient manner possible and > not repeat effort. > > Towards this end, I wish to understand how the synthesis engine xml > configuration files > work. There is a quite complete, but totally overwhelming, pdf file on > the synthesis web site.
As you said, http://syncevolution.org/development/pim-data-synchronization-why-it-so-hard is a (hopefully) more gentle introduction to that subject. > What seems to be missing is a sort of quick overview - in particular > the recent syncevolution release > notes refer to re-organizing the xml config files to make each file > be reserved for a particular role That only changes the origin of the XML config, not its role or semantic. Instead of editing one large file, you can add or replace individual chunks of it. The README.rst explains that in the section on SYNCEVOLUTION_XML_CONFIG_DIR. > An overview of the directories placed on the wiki would be quite > helpful. > I see directories for datatype files, and remote rules, and scripts. Agreed, some README files in each of these directories would be useful. On the other hand, once you know the outline of a Synthesis XML config, the directories are fairly obvious. > One thing, I am trying to figure out is how the mapping is defined... > I suspect it is all considered in an incoming context, and I need to > go to each > client directory to find the appropriate xml. Right now, the same profile is used for the SyncML peer and the local Evolution data storage. There are no per-client profiles. > For example, for syncevolution the syncevo/configs directory seems to > be the place to start looking. > There is a remoterules directory. In this context what is remote - > client or server side? If running as client, the server is remote. If running as server, the client is remote. > Where would I find the maemo version of this? Are their any special > cases for maemo yet? There are no Maemo specific versions, and the default SyncEvolution in Maemo (the latest stable version 0.9.2) does not yet use the revised XML config layout. The profiles however should be the same. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
