Re: [RFC] Plugin specifc capabilities II

On Tue, 2009-03-31 at 13:22 +0200, Daniel Gollub wrote:
> [1] http://opensync.org/wiki/trunk/features/mergerFormatConversion

>From a didactic point of view I suggest to structure the page
differently: describe the desired solution first, then for those who
disagree with it explain why other solutions don't work.

I can't say I understand all of the tables that explain why they don't
work, but as the proposed solution mirrors what I believe is right (all
comparison/merging must be done in a common format) I won't argue about
that ;-)

So let's focus on the final solution. Can you add information and/or
explain more clearly what kind of input is needed by the "merge" and
"demerge" steps? What is their output besides the "format C" items?

In particular: how many caches are needed?

> [2] http://opensync.org/wiki/trunk/features/mergerCapabilities

Allowing arbitrary combinations of OSyncObjFormat and capabilities
description looks nice in theory; in practice I don't expect that there
will be many mergers that really support many arbitrary combinations.
The API can be left like it is, but sync plugin authors need to know
which combinations they can count on. In particular, both item format
and the corresponding capabilities format must be defined well because
many people will use and depend on them.

Merge plugins and conversion plugins are different beasts, right? At
least according to the Wiki page above, merge plugin's only work with
one particular format, so I suppose conversion plugins are the ones
which deal with two different formats.

How are conversion plugins parameterized?

Like merging they need information about both sides of the conversion.
To give just one example, in SyncML the server is told whether its
client supports UTC or relies on times in local time. This information
would be important when converting between the client's format
(vCalendar 1.0) and the internal, common format (some kind of more
general event description).

--
Bye, Patrick Ohly
--  
Patrick.Ohly@...
http://www.estamos.de/



------------------------------------------------------------------------------
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel