Re: thread protocol modifiers
Re: thread protocol modifiers
- Subject: Re: thread protocol modifiers
- From: Ken Thomases <email@hidden>
- Date: Sat, 5 Jan 2008 01:36:12 -0600
On Jan 4, 2008, at 7:06 PM, William Zumwalt wrote:
#2) I make 3 calls to my server thread in sequence, so I marked all
3 as
(oneway void). After doing this I was able to click on a button in
my GUI
while the thread was running, so I think the GUI was blocking w/ the
default
(inout void) ... at least I think that's the default.
However my problem now is that with all three marked as (oneway void)
(sending async msgs), message #2 requires a few seconds to complete
while
message #3 depends on message #2 before it can start, yet msg #3 is
done
before msg #2 can finish. I've also seen once where they arrived out
of
order.
// from the client
[server sendMsg1];
[server sendMsg2];
[server sendMsg3];
Is there another way to call asynchronously, yet guarantee that the
messages
arrive in order? Or someway to call w/o the GUI blocking for a server
message return?
See here:
http://developer.apple.com/documentation/Cocoa/Conceptual/DistrObjects/Tasks/configuring.html
In particular, the paragraph that discusses
setIndependentConversationQueueing:.
-Ken
_______________________________________________
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