Open Bug 145367 Opened 24 years ago Updated 2 years ago

use nspr's base64 code in the LDIF import code, instead of having our own implementation

Categories

(MailNews Core :: Import, defect)

defect

Tracking

(Not tracked)

People

(Reporter: sspitzer, Unassigned)

Details

(Keywords: helpwanted)

use nspr's base64 code in the LDIF import code, instead of having our own implementation see nsTextAddress.cpp // XXX TODO fix me // use the NSPR base64 library. see plbase64.h
this is low priority, code cleanup.
Severity: normal → minor
Keywords: helpwanted
Target Milestone: --- → Future
Another possible approach might be to use the LDAP C SDK code for reading and writing LDIF format stuff. This would perhaps involve adding an interface or two to the LDAP XPCOM SDK, but that shouldn't be hard, or perhaps just linking statically with libldif. The C SDK functions are defined here: http://lxr.mozilla.org/mozilla/source/directory/c-sdk/ldap/include/ldif.h http://lxr.mozilla.org/mozilla/source/directory/c-sdk/ldap/libraries/libldif/line64.c
And in case someone asks: the libldif code does not use NSPR's base64 encode/decode functions because: 1) The code pre-dates NSPR to some extent. 2) I didn't know NSPR had that functionality. 3) There is still a desire from some users of libldap to not have it depend on NSPR. But I don't think libldap uses libldif so this is not important (the LDAP command line utilities under ldap/clients/tools do use libldap).
QA Contact: gayatri → stephend
Product: MailNews → Core
QA Contact: stephend → database
Product: Core → MailNews Core
Assignee: cavin → nobody
Component: Database → Import
OS: Windows 2000 → All
QA Contact: database → import
Hardware: PC → All
Target Milestone: Future → ---
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.