On 13 Jun 2013, at 20:05, Tom Davie <tom.da...@gmail.com> 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. _______________________________________________ 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
