Hello Scott.
My answers are inline.

> 1. How long does it typically take for the OS to delet the
>    mutex on its own? I would think it's just a few seconds.
This time depends on current loading OS.
On my PC (Win 2000) this time is about 0.4 - 1 second.

> 2. Is there anything we can do to accelerate this?
We can not to accelerate this.
I don't understand why VNC not delete own mutex after finishing.

> 3. Can we have Kaboodle simply wait until the mutex clears
>    before it tries to restart VNC?
Presently Kaboodle does exactly this.
a) - Kaboodle deletes VNC server,
b) - OS says to Kaboodle: "VNC server have already delete",
c) - Kaboodle ask OS "Do you have mutex with name
<WinVNC_Win32_Instance_Mutex>".
d) - if reply is YES, then Kaboodle waits 0.2 second and go to c).

- Igor


_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel

Reply via email to