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: Jens Alfke <email@hidden>
- Date: Tue, 22 Jun 2010 18:44:29 -0700
On Jun 22, 2010, at 5:28 PM, Bill Appleton wrote:
> so different vendors whip out "security" for different reasons. on mac, it is to prevent browser crashes, thus the separate process. on windows, it is all about preventing system corruption, thus protected mode
This isn’t a Windows thing. Chrome runs on Mac and Unix too. I think the reason Apple stresses preventing crashes is because it’s all they can say now — they haven’t yet implemented any sandboxing of the WebKit engine, so they aren’t actually getting any security improvements in Safari yet. (They do seem to be working on this in the future, judging by what’s going on in the WebKit open source project.)
> which is especially funny, because you are limited in where you can WRITE a file but you can READ just about anything you want. so much for security.
Not sure what you mean here. Sandboxed renderers in Chrome can’t access the filesystem at all. Nor the network, nor IPC except to the main browser process.
> i think browser manufactures should focus on the voluntary aspect of plugin usage. our customers want to use dreamfactory to access cloud services. make it easy for them. i don't like the way some plugins can be used to "bomb" the users machine without notice. like the "dancing mortgage guy" on cnn. did you want to see him?
I don’t understand what this means. What are you asking for?
—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