The best way is to write an application that's stable. The only reason browsers started doing this was because they had to deal with 3rd party code (e.g. flash) that was giving them a terrible reputation for instability. If you're controlling the entire app, you have no reasonable reason to do this. Simply fix your crasher bugs instead.
On Thu, Jun 13, 2013 at 12:52 PM, Daniele Margutti <m...@danielemargutti.com>wrote: > Hi guys, > While I’m making an app (it’s docs based) I would to have a separated > process for each opened NSDocument. > The main idea is to have the main app which launch a process for each > opened NSDocument/NSWindow and forward all messages to foreground > window/process. > In this case each process is isolated from the others as like with Safari. > What’s the best way to accomplish it on OS X? > Thanks a lot > Daniele > _______________________________________________ > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/tom.davie%40gmail.com > > This email sent to tom.da...@gmail.com _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
