site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com User-agent: Microsoft-Entourage/10.1.6.040913.0 I am doing simple IPC with mach messages, and I need a timeout mechanism. The alternatives of which I am aware -- creating the receive port using mk_timer_create(), or waiting on a port set that includes a timer -- are suboptimal in this situation. As for mig, I am aware of it, but it doesn't seem necessary. Everything seems to be working fine (save for this timeout issue). Thanks again, Eric Grant On 12/6/06 9:10 AM, "Dave Zarzycki" <zarzycki@apple.com> wrote:

More to the point, how did you find yourself in such a scenario where the answer to that question matters?

Have you considered using the tool called 'mig' to automate IPC stub generation and demux?

davez

On Dec 6, 2006, at 9:02 AM, Dave Zarzycki wrote:

...

Why do you ask?

davez

On Dec 6, 2006, at 8:48 AM, Eric Grant wrote:

...

The mach_msg man page states:

If MACH_RCV_TIMEOUT is used without MACH_RCV_INTERRUPT, then the timeout duration might not be accurate. When the call is interrupted and automatically retried, the original timeout is used. If interrupts occur frequently enough, the timeout interval might never expire. MACH_SEND_TIMEOUT without MACH_SEND_INTERRUPT suffers from the same problem.

http://www.opensource.apple.com/darwinsource/10.4.8.x86/xnu-792.13.8/osfmk/m an/mach_msg.html.

Is this statement true for Darwin's implementation of mach?

_______________________________________________ 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... This email sent to site_archiver@lists.apple.com