Paul Sandoz <[EMAIL PROTECTED]> writes:
> 
> >>    Also i think that there is no need to impose the address
> >>    book name space on an organisational ldap preferences.
> >>    
> >>    We would like to instantiate nsIAbDirectory RDF resource
> >>    components through corresponding factory components
> >>    which have contract ids like:
> >>    
> >>    @mozilla.org/addressbook/directory-factory;1?type=ldap
> >>    @mozilla.org/addressbook/directory-factory;1?type=abmdbdirectory
> >>    @mozilla.org/addressbook/directory-factory;1?type=outlook
> >>    
> >>    An LDAP address book directory factory can return an
> >>    RDF resource component with a URI defined by the scheme
> >>    'abldapdirectory'
> >
> >So shouldn't the first contract id use "type=ldapabldapdirectory"?  Or
> >I am misunderstanding how you mean to construct these contract ids?
> >
> 
>       The plan would be somthing like:
>               o obtain the uri in the preferences,
>               o call somthing like GetDirectoryFactory (uri) on
>                 an address book factory interface
>                 - this would obtain the scheme prefix
>                   @mozilla.org/addressbook/directory-factory;1?type=
>                   to the scheme and instantiate the relevant
>                   component to return which implements a directory
>                   factory interface
>                 - We would then call CreateDirectory (pref properties...)
>                   which returns a directory interface of an RDF
>                   directory resource component which represents
>                   the address book implementation.
>                   
>       I was trying to distinguish between URIs used in the
>       preferences and URIs used for RDF resources. The LDAP
>       factory will return a RDF directory resource with the
>       URI scheme 'abldapdirectory'.

OK, this part I understand:

>       The LDAP preferences could be used by other clients which
>       are not interested in address books directories like the
>       LDAP auto-completion code. So I thought it was better to
>       keep the generic scheme and let the factories return more
>       specific schemes in line with the more specific functionality.

But what I don't get is if I'm looking for preferences unrelated to
the addressbook, why would I be going through something called
'@mozilla.org/addressbook/directory-factory...' to get them?  Sorry if 
I'm being overly slow here.

Dan
-- 

Reply via email to