Closed Bug 28298 Opened 25 years ago Closed 15 years ago

Clean-up the wstring/string nsIRegistry API

Categories

(Core :: XPCOM, defect, P3)

defect

Tracking

()

RESOLVED INVALID

People

(Reporter: dveditz, Assigned: dveditz)

Details

Attachments

(1 file)

The nsIRegistry API has had wstring methods added to fix PDT+ bug 23859, but 
the old methods were not not removed because there were too many clients of the 
interface to change this close to shipping a beta.

This bug tracks final clean-up of the API, marking the UTF8 string versions 
[noscript], altering registry clients other than the Profile Manager, etc.
Target Milestone: --- → M16
It looks like the registry is storing everything in UTF-8, and the wstring 
versions of the methods use the UTF-8 versions to store the data. If the UTF-8 
versions are removed from the nsIRegistry interface, then there will be some 
UTF-8 to UTF-16 to UTF-8 conversions. Is this okay?
I'm going to keep both, the UTF-8 versions are definitely more efficient if you 
have valid UTF8 (or ASCII) data. But there is still some cleanup to do. For one 
thing the UTF8 versions must NOT be scriptable, because xpconnect will convert 
Unicode javascript data to something other than UTF8 for "string" arguments.

I also want to kill the stupid "subtree" API names.
Status: NEW → ASSIGNED
M16 has been out for a while now, these bugs target milestones need to be 
updated.
Target Milestone: M16 → ---
Resetting missed milestones
leger@netscape.com is no longer a valid email. reassigning qa contact to the
component's default.
QA Contact: leger → rayw
Component: XPCOM Registry → XPCOM
QA Contact: rayw → xpcom
nsIRegistry is no more
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: