[Kde-pim] KABC Contact Groups

[Christian Mollekopf]

On Wednesday 15 May 2013 16.19:45 Kevin Krammer wrote:
> On Wednesday, 2013-05-15, Christian Mollekopf wrote:
> > On Wednesday 15 May 2013 12.42:45 Christian Mollekopf wrote:
> > > Hey,
> > > 
> > > KABC::ContactGroup uses the akonadi item id of a contact as uid, which
> > > is
> > > IMO a bad design decision, because contact groups are synchronized to
> > > other systems where the id's are obviously not valid any more.
> >  
> >  also, if the kolab proxy syncs an updated contact, it removes the old
> >  item
> > 
> > and creates a new one, which breaks the link for obvious reasons.
> > That's arguably a shortcoming of the kolabproxy, but I think nevertheless
> > that references should refer to the underlying logical contact object (by
> > it's uid), and not to the container (the akonadi item).
> 
> Lets take a look at the goals and the assumptions that lead to the current
> implementation.
> 
> One goal was to have the option of linking contacts into groups such that
> changing any contacts details would automatically be reflected by the group.
> Assumption of course being that all contacts have an item id and that this
> id is always unique, even in the worst case of the same vcard being used by
> two resources.
> 

Whoops, missed that point. I suppose a heuristic based on resource or similar 
would have to be used in this fringe case.

It's very much the same problem domain of ical incidences referencing other 
incidences by uid. We must address this somehow, but I don't think relying on 
internal id's is the way to go.

Cheers,
Christian
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/