Basically there are two sets of topics. The topic notifications which are generated from xpcom and those that are defined and generated by clients of xpcom.
XPCOM has no public topics yet. We were thinking about making NS_XPCOM_SHUTDOWN_OBSERVER_ID public, but we have not reached a decision. Client of XPCOM may have public observer topic. I know of none. Judson Valeski wrote: > Do we have a list of topics that are also "frozen?" It would be bad if > people thought all topics were frozen, only to have a topic removed, > or its semantics changed. > > Jud > > Doug Turner wrote: > >> The nsIObserver and nsIObserverService are now frozen: >> >> nsIObserverService >> http://lxr.mozilla.org/seamonkey/source/xpcom/ds/nsIObserverService.idl >> >> nsIObserver >> http://lxr.mozilla.org/seamonkey/source/xpcom/ds/nsIObserver.idl >> >> >> Please note, that you can track the progress of XPCOM API changes on >> this bug: >> >> http://bugzilla.mozilla.org/show_bug.cgi?id=98278 >> >> >> Please note that this interface is frozen. It will not change and >> you can depend on it. The only interfaces that are frozen are marked: >> >> http://lxr.mozilla.org/seamonkey/search?string=us+frozen >> >> If your component or plugin is using interfaces outside of this set, >> please note that they are most likely unfrozen and have the >> possibility to change. >> >> doug turner >> [EMAIL PROTECTED] >> >> > >
