site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Note that I am not interested in getting a reply. Thanks, david. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... -- I got a suggestion to post this question here rather than on Carbon-dev; apologies if you got it there too. Does anyone here have experience with timeouts and CFMessagePortSendRequest? As far as I understand CFTimeInterval is in seconds, so if I pass 0.02 for sendTimeout when calling CFMessagePortSendRequest I would expect a kCFMessagePortSendTimeout error if more than 0.02 secs are needed. However, what I am seeing is that CFMessagePortSendRequest can take for example 6 ticks (= 0.1 sec) and still return with noErr, so not timing out as I would have hoped. Am I doing something wrong, is the documentation incorrect, or is this a bug? I am running on 10.3.8 and calling it like this: result = CFMessagePortSendRequest( sMessagePort, inMessageID, inData, 0.02, 0, NULL, &replyData ) ; A related question: What kind of things influence the duration of this call. To what degree does what happens at the receiving end influence the duration of the call. I am not working with return values so I am presuming that as soon as the CFMessagePortCallBack at the receiving end is called CFMessagePortSendRequest is able to return and not delayed by any processing inside the callback, is this a correct assumption? This email sent to site_archiver@lists.apple.com