[API] key=value interface for OSyncAnchor

[bellmich]

Hi,

I need to manage in SyncML two synchronization anchors per data store. So I need an interface in OpenSync where I can store data on a key per value base. This interface can be attached to the plugin (aka main sink) or to the object type sink.

Best regards

Michael

[dgollub]

After some discussion on IRC the ticket changed to "key=value inter for OSyncAnchor".

Definition:

OSyncAnchor can be used to store protocl "anchors" and further peer state information.
Note: that the OSyncAnchor can be flushed at any time by the Engine. Don't use it as persistent cache/store.

The generic database interface for dynamic configratuino gets addressed in #1050

[dgollub]

(In [5462]) Introduced OSyncAnchor key=value interface. This unfortuantely breaks the API and requires all plugins using the anchor to port.

Porting instruction:

char *anchor_value = plugin_specific_anchor();

-osync_anchor_compare(anchor, anchor_value, &anchormatch, &error); +osync_anchor_compare(anchor, "anchor_key"1, anchor_value, &anchormatch, &error);

-osync_anchor_update(anchor, anchor_value, &error); +osync_anchor_update(anchor, "anchor_key1", anchor_value, &error);

-osync_anchor_retrieve(anchor, &error); -osync_anchor_retrieve(anchor, "anchor_key1", &error);

This key=value pair is per ObjTypeSink?. This means you can reuse the key-name for each ObjTypeSink?.

Dropped old and unintended anchor.db file from test fixtures for filter_destobjtype_delete testcase

fixes #1090

[dgollub]

(In [5463]) Ported file-sync to OSyncAnchor key=value API change. refs #1090

[dgollub]

(In [5464]) Ported evolution2-sync to OSyncAnchor key=value API change. refs #1090

[dgollub]

(In [5465]) Ported ldap-sync to OSyncAnchor key=value API change. refs #1090

[dgollub]

(In [5466]) Ported tomboy-sync to OSyncAnchor key=value API change. refs #1090