Re: Isolated process for each NSDocument of my app
Re: Isolated process for each NSDocument of my app
- Subject: Re: Isolated process for each NSDocument of my app
- From: Tom Davie <email@hidden>
- Date: Thu, 13 Jun 2013 21:27:43 +0200
On 13 Jun 2013, at 20:29, Daniele Margutti <email@hidden> wrote:
>
> On 13 Jun 2013, at 20:05, Tom Davie <email@hidden> wrote:
>
>> 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.
>
> Overall stability is not my reason to evaluate this kind of a architecture; for a particular reason each document should interact with an external singleton class but each singleton must be unique around the app; think about UIApplication on iOS; I need to work with a similar thing so I need to “run” multiple projects and each one must see a single instance of this object. I cannot change this kind for several reason, so an architecture like this could be a great answer to enable multiple documents support in my application.
So really, what you're saying is "Someone stuck a singleton where a singleton shouldn't be (anywhere at all), and now I'm screwed that I need more than one of them." Your solution to this should be to not use a singleton (ever), rather than to try and hack about the application structure to carry on using a singleton.
Tom Davie
_______________________________________________
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