>Resent-Date: Wed, 21 Feb 2001 16:27:12 -0800 (PST)
>To: [EMAIL PROTECTED], [EMAIL PROTECTED]
>From: [EMAIL PROTECTED] (Dan Mosedale)
>Subject: Re: addressbook prefs UI change proposal; feedback requested (was Re:
LDAP server preferences)
>Date: 22 Feb 2001 00:26:31 GMT
>NNTP-Posting-Host: adsl-63-194-215-4.dsl.snfc21.pacbell.net
>X-Newsreader: trn 4.0-test74 (May 26, 2000)
>Originator: [EMAIL PROTECTED] (Dan Mosedale)
>Resent-Message-ID: <"PZXTOC.A.-jC.VzFl6"@gila.mozilla.org>
>Resent-From: [EMAIL PROTECTED]
>X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/11957
>X-Loop: [EMAIL PROTECTED]
>Resent-Sender: [EMAIL PROTECTED]
Dan Mosedale <[EMAIL PROTECTED]> writes:
>Well, there maybe issues in the amount of information that a standard
>LDAP URI can hold, as per the other message I just posted. But doing
>the new URI schemes suggested in the refactoring proposal might work.
>Although maybe just changing the syntax of the existing abook: scheme
>and putting the ldap || mdb || ... after the colon would help keep us
>from polluting the URI scheme namespace too much. After talking this
>over with hixie and dbaron, I filed bug 69513; if adding more schemes
>is the right thing to do, that will be relevant to how the new
>schemes get named.
>
I don't think it is necessary to store all preferences
in the URI, the minimum to identify the type, location
and maybe user would suffice for LDAP. An interim
solution could be to maintain both in the preferences
reusing one preference attribute as the uri, a good
candidate would be 'filename'. Hmm... maybe not because
this is used to identify the off-line db file for ldap,
but there is no concept of offline for ldap yet +
the offline address book could be identified as a uri
as well... ramble ramble....
<slightly-off-topic>
I presume at some point that this .js file is going
to change to RDF?, a general prefs editor using an RDF
schema could be interesting esp. for enterprise where
preferences could be stored in an LDAP server.
</slightly-off-topic>
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'
Also perhaps the scheme 'abmdbdirectory' could be better
stored as 'moz-pab' in the preferences?
It is possible to use the number defining the type
of address book i.e. type=0, but i think that it is
really ugly. Or even uglier have a:
if (dirType == 0)
else if
.
.
We can get by with the former 'ugly' as an interim solution.
Thanks,
Paul.
| ? + ? = To question
----------------\
Paul Sandoz
x19219
+353-1-8199219
