>> 1) Implementing nsISecurityCheckedComponent (to allow access to >> specific >> properties or methods). >> 2) Implementing nsIClassInfo with the right magic flags (claiming to >> be a DOM >> class?). This will, for example, allow same-origin access to > > >These are mutually exclusive, by the way. So do one or the other. > > >> But I can't understand the suggestion,more concretely speaking,I >> can't follow even one step.Can someone give me some implement >> example.Thanks very much... > > >Didn't I say at the time to look at the way XMLHttpRequest works in Gecko >1.8.0.x? See the classinfo stuff in nsXMLHttpRequest.cpp and >nsXMLExtrasModule.cpp there if you want to do classinfo; I believe the category >manager stuff in nsXMLExtrasModule.cpp is what you need to set up constructors.
Er. So if i just have the gecko 1.7.13 sdk (for component developers) from http://www.mozilla.org/releases/, then - for the nsISecurityCheckedComponent solution i've got to go get the seamonkey source too? - the JavaScript DOM solution needs some mozilla dom stuff also not found in the sdk? It is a wee bit strange that just the sdk isn't enough to develop a public XPCOM component. _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
