[sync] mapping deletion

[Jan Schneider]

Zitat von Otto Berger <otto at bergerdata.de>:

>
> Hi,
>
> i wonder why the mapping-entries of deleted client-entries (on server
> request) dont gets deleted by the backend. Is there a special reason for
> this?

Without looking at the code, I would guess that it's necessary to keep  
this information if you are going to sync with multiple clients.

> my current situation:
>
> i extended my backend to handle these deletions:
> function deleteUidMap($databaseURI, $suid) {
>      ....
> }
>
> then i call this function at the Syncml_Sync class (line 386):
> $backend->deleteUidMap($this->_targetLocURI, $suid);
>
> Furthermore i also want to call deleteUidMap() at a client-delete
> request (SyncML_Backend::deleteEntry). But on this point i'm sure to get
> other side-effects. The Horde backend describes here:
>
> // We can't remove the mapping entry as we need to keep
> // the timestamp information.
>
> So what is the solution?
>
> Maybe it is a way to track the deletions elsewhere (i.e. session or
> mapping table) and let the Backend-Class clean up the mapping-table
> after an successful sync.
>
> opinions? suggestions?
>
> Otto
>
> --
> sync mailing list - Join the hunt: http://horde.org/bounties/#sync
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: sync-unsubscribe at lists.horde.org
>



Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/