Re: Should I add properties to ABPerson?
Re: Should I add properties to ABPerson?
- Subject: Re: Should I add properties to ABPerson?
- From: Aurélien Hugelé <email@hidden>
- Date: Tue, 24 May 2005 09:00:07 +0200
To my concern, there is a major caveats : i've seen people writing
huge datas in private properties (entire HTML pages, archived
NSImages etc...)
you can probably store you custom datas, but please, only store, like
Apple do, tiny datas there : for example UIDs, few bytes NSString etc...
the AddressBook database performance decrease *greatly* when some
properties store huge datas... and ALL APPLICATIONS WILL BE IMPACTED,
NOT ONLY YOURS. We had some of our user angry because they found our
software (OD4Contact) to be very slow... i've looked at their
database and discovered that they tried almost all (sometimes crappy
in this respect) AddressBook compatible applications that stored
exotic datas in their database... after a cleaning, performance was
up, by a important factor !
Le 23 mai 05 à 22:38, Guy English a écrit :
Hi everyone,
I've written an app that add properties to the AddressBook
ABPerson records. Properties like Keywords and Labels. They are only
used for my application and it's not really expected that other apps
would need to access them, although it'd be nice if they could.
I have a few concerns with this approach. Firstly it takes a
significant amount of time to add the properties during the inital run
of the application. This isn't a big deal since I can handle it
reasonably in the UI but it's a bit annoying. Second ABPerson
removeProperties isn't implemened yet. So, once added, those
properties are going to be there for a long time. ( I've filed an
enhancement request to get that fixed ). Third is that I haven't seen
any other apps do this despite it seeming like a useful method of
attaching data to people. Delicious Library, for example, uses it's
own data store even though using the Address Book would make sense for
them. On the positive side I believe that these custom fields will be
synched at the same time the Address Book is without me doing any work
- which is nice.
Does anyone have any insight as to weather I should do this or
simply manage my own data store? Would you, as a user, be annoyed that
my app played with your Address Book data base?
Thanks,
Guy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gumitech.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden