Open Bug 67696 Opened 24 years ago Updated 2 years ago

LDAP replication could ignore dup DNs in changelog

Categories

(MailNews Core :: Address Book, defect)

x86
Windows NT
defect

Tracking

(Not tracked)

People

(Reporter: phil, Unassigned)

References

Details

This bug is a placeholder for an optimization to consider for LDAP replication. The original root of this bug is: http://scopus.netscape.com/bugsplat/show_bug.cgi?id=334179 When we're reading the changelog and pulling the DN for each change, it would be nice if we had some way to remember that we'd pulled a DN recently, and not pull it again. Apparently, some customers have usage models where the same DN appears in the changelog several times in a row, and we ask for the same entry multiple times. In the 4.x code, we only knew one DN at a time, but we might be able to keep a cache of the last 50 or so DNs (but not the whole entry) on an LRU basis to make this problem smaller. Obviously, keeping every DN we've seen in memory would be expensive.
*** Bug 7743 has been marked as a duplicate of this bug. ***
QA Contact: esther → yulian
Moving to Future, as this doesn't yet apply to any code that's in the tree (ie we don't do replication yet).
Assignee: dmose → dmose
Target Milestone: --- → Future
Status: NEW → ASSIGNED
Target Milestone: Future → ---
Product: Browser → Seamonkey
Component: Address Book → MailNews: Address Book
Product: Mozilla Application Suite → Core
QA Contact: yulian → addressbook
Assigning bugs that I'm not actively working on back to nobody; use SearchForThis as a search term if you want to delete all related bugmail at once.
Assignee: dmose → nobody
Status: ASSIGNED → NEW
Product: Core → MailNews Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.