Re: Blocking Method Return
Re: Blocking Method Return
- Subject: Re: Blocking Method Return
- From: j o a r <email@hidden>
- Date: Fri, 2 Dec 2005 17:09:26 +0100
On 2 dec 2005, at 16.19, Josh Ferguson wrote:
Simply put, I don't have that design flexibility.
I find that hard to believe, but as I know next to nothing about your
project, I'll have to take your word for it.
Regardless, it's certainly not an argument against windows apps.
It certainly is an argument against any app that uses networking and
that doesn't use threads while waiting for network operations to
return...
Classic Mac apps and most unix libraries employ the same tactic -
you call into a function, wait for it to return, and grab the
return value. It's not like it's a terrible paradigm. It's just not
very cocoa-friendly.
In the general case, calling a method and waiting for it to return,
is of course perfectly OK. I don't see why you would claim that Cocoa
doesn't like when you do that?
That said - Blocking the main thread in a GUI application while
waiting for a network operation to return can't be good design -
regardless of the underlying OS / framework.
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden