[turba] Replace VCARD

[Mikael Geijer]

Chuck Hagenbuch wrote:

>Quoting Mikael Geijer <mikael at nufort.net>:
>
>  
>
>>One more design issue here, maybe a totally new subject, but anyway.
>>I would like to be able to sync objects that are modified and newly
>>added in the Turba addressbook. I have a timestamp when the last sync
>>was made in my sync-app and would like to have two timestamps on the
>>Turba objects:
>>- a creation timestamp
>>- a "modified" timestamp (as exists on the kronolith_event object).
>>And then of course some new methods in the api to find newly added and
>>modified objects.
>>    
>>
>
>As Jan pointed out, this is part of what the Horde_History API is for - it makes
>it very easy to track and retrieve this kind of information. That's why I
>mentioned it to you before.
>
>-chuck
>  
>
The History API looks like the right way of doing it.  Planning to use 
it something like:
- Create a Turba_History class
- Add a history entry when a turba object is created (Action => 'add')
- Update history entry when a turba object is modified  (Action => 'update')

Then I need two turba API method's "get all updated since timestamp" and 
"get all updated since timestamp" with apropriate keys.  They in turn 
need to interface w the  History API.

There is no support for these kind of methods in the History API. Any 
suggestions on how to implement this?

Cheers

/Mikael

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=- Mikael Geijer, nufort HB (nufort.net), Oebb AB (oebb.net)
=- mobile: +46 70 7455239 office +46 70 7455239
=- email:  mikael at nufort.net
=- snail:  Kyrklunden 8, 122 32 Enskede, Sweden
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=