[sync] Turba and Syncml status?

Chuck Hagenbuch chuck at horde.org
Tue Nov 30 14:18:05 PST 2004


Quoting Karsten Fourmont <fourmont at gmx.de>:

> This requires changes to the database, config/sources.php and
> config/attributes.php. As this is all configuration data it should be
> easy to provide the required data as a _seperate_ config example. Shall
> I put it directly into the turba package or just somewhere into syncml/docs?

In Turba's docs/example files.

> 2) changes to api.php. This is a bit more of an issue. Currently
> turba_exports reads like this:
>
> // Need to reference some sort of mapping here to turn the UID
> // into a source id and contact id:
> // $source = $uid['addressbook'];
> // $objectId = $uid['contactId'];
> return PEAR::raiseError('Turba needs a UID map');
>
> And this will obviously do nothing, only complain :-(
>
> Syncml already has a UID map to relate client (PDA) UIDs to horde UIDs.
> Currently it stores a turba ID like this:
> turba:localsql:a7852bb273265eb258ed2ea53692497c

That's what the old uids used to look like. It should probably just be storing
the UID and what kind of entry it is (contact, task, etc.).

> So what format am I supposed to pass the uid in? Will something like
> $uid= array('addressbook' => 'localsql' , 'contactId' =>
> 'a7852bb273265eb258ed2ea53692497c') ;
> for the above example do?

No. You need to pass in the actual UID as stored in the __uid field in the
source. Turba may need its own map to determine what addressbook a UID is
associated with, but we *must* be able to take the plain UID as input do both
of those functions and to figure things out from there. I haven't worked over
how to do that yet.

> The same applies for turba_replace as well.

Same.

-chuck

-- 
"But she goes not abroad in search of monsters to destroy." - John 
Quincy Adams


More information about the sync mailing list