Re: Multiple Resources in kabc

On Wed, May 29, 2002 at 09:44:34AM -0400, Mike Pilone wrote:
> On Wednesday 29 May 2002 09:12 am, Tobias Koenig wrote:
> > > Once this is functional, it would be nice to add multiple read
> > > resources and a single write resource.
> >
> > can't distinguish what addressee is from what source. This distinction
> > is necessary to save only the addressee entries from write resource.
> >
> > Any objections against adding
> >     Resource *resource;
> > to Addressee::AddresseeData?
> 
> I would prefer if we had a unique ID or unique string (much like the 
> Addressee's uid) for each resource so that we do not have pointers to the 
> resources all over the application. There is no functional need for the 
> Addressee (or AddresseeData) to have a pointer to the resource. The 
> AddressBook can maintain a simple map of uid to resource and look it up as 
> the addressees are saved.
Ok, but a pointer costs 4 bytes memory and a _good_ unique string min. 9 bytes.
Furthermore, comparing pointers is much faster than comparing strings, and
especially when saving the addressee entries we have to be fast.

There shouldn't be problems with inncorrect pointers, since you do not call
a methode of the pointer object, but compare them.

Ciao,
Tobias
-- 
In a world without walls and fences who
needs Windows and Gates???
_______________________________________________
kde-pim mailing list
kde-pim@xxxxxxxxxxxx
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/