Could someone describe for me what an OJI plugin needs to do with
respects to implementing nsIModule?  I'm an interested in understanding
how the browser queries the DLL that contains the plugin.

Under the current, documented, scheme the browser looks for a function
[NSGetFactory()] and uses that to create instances of plugins.

How does the switch to nsIModule effect this?

TIA,

skatz

Reply via email to