On 13 Jun 2013, at 21:04, Jens Alfke <j...@mooseyard.com> wrote: > > On Jun 13, 2013, at 11:29 AM, Daniele Margutti <m...@danielemargutti.com> > wrote: > >> 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. > > I think you’ll find it easier to refactor your code to avoid depending on a > global/singleton*, than to implement low-level system functionality to split > your app across processes.
That’s not possible due to some important reason I can’t explain here :( Belive me, if it was the right way I would have used them :( _______________________________________________ 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
