safari - Developing an out-of-process browser plugin on Mac OS X v10.6 -- restriction against platform APIs? -
i'm developing browser plugin macosx 10.6, , planning use netscape api portability across browsers , architectures. according apple's documentation, of 10.6 such plugins run out-of-process improve integrity of browser session. i'm concerned following directive give in documentation:
use platform apis sparingly. wherever possible, should use new plug-in apis need. if no such apis exist, file bugs requesting them.
i'm not sure nature of directive is. advice improve portability of plugin, reminder accessing operating system's other apis can open possibility of crashing client or corrupting user's data, or indication access platform apis in way "broken?"
its portability advice. npapi is, although not officially standardized, stable , wraps platform specific apis you.
if try use npapi whenever possible, avoid quite porting e.g. happened relatively apple deprecating carbon when transitioning 64 bit.
Comments
Post a Comment