Re: Problem with stopModalWithCode on a different thread
Re: Problem with stopModalWithCode on a different thread
- Subject: Re: Problem with stopModalWithCode on a different thread
- From: Bill Appleton <email@hidden>
- Date: Tue, 22 Jun 2010 16:47:55 -0700
then what will you be able to do? nothing? compare what is possible on
windows and mac, they can't get too far out of line. this IS sandboxed ---
its in a separate process
On Tue, Jun 22, 2010 at 4:02 PM, Jens Alfke <email@hidden> wrote:
>
> 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 (email@hidden)
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:
This email sent to email@hidden