On Jun 22, 2010, at 2:40 PM, Charles Srstka wrote: > You get a separate process for your plug-in, but there is no guarantee that > that process will have a full Cocoa environment running. You are recommended > to use only plug-in APIs as much as possible, and not to spawn new windows.
Yup. The only reason you can do AppKit stuff in plugins is that the browser vendors haven’t been able to sandbox the plugin environment completely yet for compatibility reasons. (It turns out Flash gets unhappy if it doesn’t have access to things like the local filesystem.) This is a bug, not a feature. Securing plugins is very important — most browser exploits nowadays go through Flash and Reader, apparently — and doing that will require running them in a fully sandboxed process just like Chrome’s WebKit renderers. In that environment you will not be able to make arbitrary AppKit calls. —Jens_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
