Closed Bug 64541 Opened 24 years ago Closed 15 years ago

Change xpcomproxy contractid to xpcom/proxy contractid

Categories

(Core :: XPCOM, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX
Future

People

(Reporter: mbosch, Unassigned)

Details

(Keywords: topembed-, Whiteboard: [T2])

xpcom/proxy/public/nsIProxyObjectManager.idl defines NS_XPCOMPROXY_CONTRACTID as "@mozilla.org/xpcomproxy;1". I think it would be better to change this to "@mozilla.org/xpcom/proxy;1". This would better follow the contractID rules, which suggest a modules/submodule structure. The only users in the Mozilla codebase of this contractid are all in the same file: /directory/xpcom/base/src/nsLDAPChannel.cpp, line 104 -- do_GetService("@mozilla.org/xpcomproxy;1", &rv); /directory/xpcom/base/src/nsLDAPChannel.cpp, line 462 -- do_GetService("@mozilla.org/xpcomproxy;1", &rv); /directory/xpcom/base/src/nsLDAPChannel.cpp, line 529 -- do_GetService("@mozilla.org/xpcomproxy;1", &rv); So it seems like a four character / 2 files change....
Marking NEW so someone who more experience can look at it.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Ray? Is this appropriate?
Assignee: scc → rayw
This name change seems appropriate from a logical perspective. Having changed a few contractid's before, it is sound advice to look in lxr for references. lxr lists several additional places that this CONTRACTID is used, and at least one of those (nsLDAPDataSource.js) does not use the .h file definition. We should first be confident that this change does not break external users, especially who may have written .js scripts. It was used by nsLDAPDataSource to add an observer to a datasource. Netscape 6 is one such external user that might have used it that should be checked.
Assignee: rayw → kandrot
Reassigning to default xpcom owner
Apply a tested patch if you strongly want to see this changed.
Assignee: kandrot → dougt
Target Milestone: --- → Future
Blocks: 98278
Target Milestone: Future → mozilla1.0
Keywords: mozilla1.0
xpcom proxy code is not frozen nor will be for mozilla 1.0
Target Milestone: mozilla1.0 → Future
removing keyword
Keywords: mozilla1.0
Keywords: topembed
this is *not* part of any SDK. and therefore should not be a topembed.
No longer blocks: 98278
Keywords: topembedtopembed-
Confirming this bug as topembed- for 1.3 triage.
Whiteboard: [T2]
QA Contact: kandrot → nobody
Assignee: dougt → nobody
QA Contact: nobody → xpcom
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.