"R. Saravanan" <[EMAIL PROTECTED]> schrieb ...
> I believe you can implement the interface nsISecurityCheckedComponent
> for your plug-in to allow unrestricted access to certain
methods/properties.
Thanks for this hint.
> I heven't used this interface myself, and I don't know how the remote
> Javascript can instantiate the plug-in object in the first place, which
needs
> access to Components.classes ...
Plug-ins are usually instantiated with the HTML embed element:
<embed name="myPlug" type="my-mime/sub-mime" ...></embed>
Assuming that plug-in exposes a SendCommand(string, string)
method, a JavaScript call would look like:
document.myPlug.SendCommand("go", "1234");
At last this was the case in Netscape 4. I hope with
XPConnect there won't be any major changes? Or will I
have to address the XPCOM interface defined in the
corresponding .xpt file? Assuming the name of the interface
is nsIMyPlug, would I have to call
document.myPlug.nsIMyPlug.SendCommand("go", "1234");
?
Regards, Tobias Trelle
--
CyCo Systems GmbH & Co. KG >>> http://www.cycosys.com/
