Closed Bug 183507 Opened 22 years ago Closed 22 years ago

Make COM connect a runtime option

Categories

(Core :: XPConnect, defect)

Product:
Core
Component:
XPConnect
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED WONTFIX
Milestone:
mozilla1.3beta

People

(Reporter: adamlock, Assigned: dbradley)

Details

COM connect is conditionally compiled with a build flag. Make COM connect build
by default but control its enabled/disabled state using a pref read at startup.
So, we need to create a JS Component to serve as a service that implements an
interface defined by XPConnect. XPConnect creates the service, if that fails,
then it's a no, other wise it asks the service. The JS would then ask the prefs?

We need to ask this everytime we instantiate a COM object. So this isn't just at
startup.

Does that seem right Adam?
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.3beta
It may be possible to extend the nsAxSecurityPolicy.js object with the attribute
you require. 

Is xpconnect able to read the prefs for itself or would this cause a dependency
issue?
That would create another dependency problem. nsAxSecurityPolicy.js sounds like
a decent place to hang this, though.
I was thinking about this again, and I think I need to have a seperate JS file.
This is because we may need to detect this when ActiveX is not present. For the
ActiveX it would work, but I'd like to put something in place that could be
usable for future projects that may not have ActiveX enabled.
What's the code footprint hit?

/be
I'm not sure we'll switch the compile time option to be defaulted to on. I think
we only need to provide this for embedders that need it. So the runtime option
is in addition to the build time option. The embedders interested would have to
make the decision on whether they want to take the additional code to gain
IDispatch functionality.

I'll try and get some numbers together and post them to this bug.
I don't believe that this should be built in regular Mozilla builds. I think
it's an optional feature that embedders can choose to support or not. The
ability to turn this on/off at runtime will be addressed with the patch for bug
188229
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Marking Verified -
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.