Need to synchronize preferences LDAP's and the addresbook

VERIFIED DUPLICATE of bug 125821

Status

SeaMonkey
MailNews: Address Book & Contacts
VERIFIED DUPLICATE of bug 125821
16 years ago
13 years ago

People

(Reporter: Cuchulainn, Assigned: John Marmion)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
Need to ensure that preference updates for LDAP directories
are synchronised with the address book and vice versa

Comment 1

16 years ago
Srilatha has a bug for the same issue with the addressing widget autocomplete
(bug 79792).  I think the most recent theory was to use an nsIPrefsObserver, but
I'm not sure about that.  She probably has some comments.

By the way, these last few bugs you filed are great -- keeping tracking of this
in bugzilla with this finer resolution is very helpful. It's probably best to
have them assigned to whoever is working on the code for this particular thing,
however, rather than me.
(Reporter)

Comment 2

16 years ago
Csaba will probably be working on this bug so I reassigned it to him
Assignee: dmose → csaba.borbola

Comment 3

16 years ago
From my limited understanding on how preference observations work i think care
has to be taken to manage multiple events occuring for an address book instance.
Is this correct? i.e. there is no transactional nature to the preferences and
the ability to get a single event for a particular branch pattern associated
with the "ldap_2.servers.*".

The same issues will occur for outlook related preferences too.

A possible future idea might be for all address book preference manipulation to
occur in the 'abdirectory://' resource, but i don't think this is practical
given the time frame. Then listeners to the nsIAddressBookSession interface will
get notifications for additions and deletions and XUL templates can be used to
display address books on the resource, in addition the view can be limited to
certain types of address book.
However, i don't think all the infrastructure is there for notification of
changes to address book properties.

Comment 4

16 years ago
I am planning on using AddObserver and RemoveObserver from nsIPrefBranch to fix 
79792. I believe you can use AddObserver on ldap_2.servers.* but you will get n 
events if n preferences in that branch are changed.

Comment 5

16 years ago
How do you propose to manage the multiple event problem? since i am not sure if
this can be avoided when address books are added and removed.
I presume 'changed' means new, delete & modify?

Comment 6

16 years ago
LDAP is Yulian's area. Assign it to her.
QA Contact: fenella → yulian

Comment 7

16 years ago
Passing the ownership to John Marmion@sun, because I was moved to another
project.
Assignee: csaba.borbola → john.marmion

Comment 8

16 years ago
Seeing this seems to be tied in to all that, maybe a dupe of one of the other
bugs linked to bug 125821
Blocks: 125821

Comment 9

16 years ago
When you import a profile from NS4.x which already has directory servers setup
then they appear under prefs addressing in mozilla but don't appear in the
address book and can't be made to appear there without deleting and recreating.

Using buildID 2002022009 on windows 2000 SP2
(Assignee)

Comment 10

16 years ago
Ian, this bug had disappeared from my radar. It originally was created to
compliment bug #83091. Now that it has been landed and bug #125821 was set up as
a placeholder for outstanding issues and bugs arising from #83091, I agree that
we should close this as a duplicate of #125821.

But even more important is your comment #9, I can confirm that this indeed is a
bug. Because the imported LDAP Directory Server gets created with a filename
suffix of "na2" then it is ignored by the Address Book Factory creation. This is
a bad bug and likely to cause people grief. The AutoCompletion works correctly.
 
I would like to see us close this is a duplicate and spin off a new bug devoted
solely to this issue. It can be tied to #125821 and use the nab-ldap keyword.

Comment 11

16 years ago
Logged a new bug 127007 for above.
(Assignee)

Comment 12

16 years ago
yulian@netscape.com can you close this is a duplicate of bug #125821 ?

Comment 13

16 years ago
dup of bug 125821

*** This bug has been marked as a duplicate of 125821 ***
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → DUPLICATE

Comment 14

16 years ago
Verified as dup
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.