DO independentConversationQueueing, invocation from callback
DO independentConversationQueueing, invocation from callback
- Subject: DO independentConversationQueueing, invocation from callback
- From: Dave Keck <email@hidden>
- Date: Fri, 24 Jun 2011 17:01:21 -1000
Hey list,
I use independentConversationQueueing to make my DO invocations block,
but doing so causes incorrect behavior in the following scenario:
1. ProcessA sends -handleMessage to ProcessB
2. ProcessB's -handleMessage executes, which sends -doSomething to ProcessC
In Step 2, the DO internals in ProcessB attempt to send a message to
ProcessA instead of ProcessC. (I know this by inspecting the instance
of NSPort that receives the -sendBeforeDate:... message in ProcessB.)
That is, the DO internals appear to be confused about which
NSConnection/NSPort instance to use when attempting to message a third
process (ProcessC) from a DO callback (-handleMessage in ProcessB).
Everything works as expected when independentConversationQueueing is
disabled, but I need my DO invocations to block.
Ideally I'd be able to set a unique reply mode for each NSConnection
instance, which would solve all my problems in a jiffy. Any idea how I
might do so, or how I might fix independentConversationQueueing?
Thanks!
David
_______________________________________________
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