Closed Bug 328441 Opened 19 years ago Closed 19 years ago

Observer service does not specify threading behaviour

Categories

(Core :: XPCOM, defect)

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

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: Mook, Assigned: dougt)

References

(
URL
)

Details

(See URL) I'm going to be having a secondary thread calling nsIObserverService::notifyObservers(). nsIObserverService does not define which thread the registered observers will be notified on (at least, according to the IDL). It would be very useful to have this actually specified. Currently guessing this will be whichever thread the notify was on, but please actually say that in the IDL because I'm probably wrong :p
Flags: blocking1.9a1+
fixed by bug 326491, nsXPCOMCID.h now says: * Observer Service ContractID * The observer service implements the global nsIObserverService object. * It should be used from the main thread only. */ #define NS_OBSERVERSERVICE_CONTRACTID "@mozilla.org/observer-service;1"
Status: NEW → RESOLVED
Closed: 19 years ago
Depends on: 326491
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.