> Ideally i think that all address book/directory
> operations should be performed on the 'abbsdirectory'
> RDF data resource, i.e. the boot strap resource (not
> a good name i know).
> The global address book container could be represented
> as:
> abbsdirectory://
>
> An account specific address book container could be
> represented as:
>
> abbsdirectory://MailAccount1
>
s/abbsdirectory/abdirectory
Got confused with the name of the class which
implemented the 'abdirectory' data resource.
If there is effort underway to write/read
ldap directory entries i wonder if we can
work together to try and get a unified way
of accessing these preferences and other
types of address book for global and
account specific?
Thereby we could replace the nsDirPrefs
code with a new service and we could
change the abdirectory data resource to
use this service.
Paul.
| ? + ? = To question
----------------\
Paul Sandoz
x19219
+353-1-8199219
- Address book functionality, proposed putback 2. Paul Sandoz
- Re: Address book functionality, proposed putback 2. Dan Mosedale
- Re: Address book functionality, proposed putback 2. Paul Sandoz
- Re: Address book functionality, proposed putback 2. Dan Mosedale
- Re: Address book functionality, proposed putback 2. Paul Sandoz
- Re: Address book functionality, proposed putback 2. Dan Mosedale
- Re: Address book functionality, proposed putback 2. Paul Sandoz
- Re: Address book functionality, proposed putback 2. Paul Sandoz
- Re: Address book functionality, proposed putback 2. Dan Mosedale
- Address book functionality, proposed putback 2. John Marmion
- Re: Address book functionality, proposed putback 2. Dan Mosedale
- Re: Address book functionality, proposed putback... Dan Mosedale
- Re: Address book functionality, proposed putback 2. Paul Sandoz
