>> I am used to a more robust threading model. > I'm curious, what is not "robust" about the Cocoa threading model, and > what are you comparing it to?
Well, only being able to draw and process events on the main thread mainly. I am comparing it to Windows where a secondary thread can do what it likes, as far as Windows itself is concerned. Each thread has its own input queue and can create windows, process its own events, draw whatever and whenever it likes and so forth. We wrote a remote control app that took advantage of this by running each remote control session in a separate thread. The remote control sessions (each one handling the screen and keyboard of a remote PC) were therefore completely independent of each other should they wish to perform blocking operations (such as file transfers) and that made writing the code much easier. It's a facility I am going to miss. _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
