Hi Roger,
When you say "running over a network" what do you mean exactly? Is it
being executed over a network drive or UNC path?
From my experience, mutexes allow you to limit a *user* to a single
instance within their session. In the case of a terminal server, you can
use a global mutex to limit your application to only one instance on a
server.
I submitted a tip to Aaron a while back about using his existing WFS
mutex code to create a global mutex, so either type is possible with WFS.
This thread contains some really useful insights on Windows mutexes:
<http://support.realsoftware.com/listarchives/realbasic-nug/2004-11/msg01630.html>
As far as limiting your app to only a single instance on a network, I
don't think a mutex is what you will need. Maybe a single socket on the
server that allows only one concurrent connection, but even that could
get messy.
Let me know what the specifics are, and I'll see if I can offer some help.
hth,
Brian
Roger Clary wrote:
>Re: My first attempt to use Mutex class to prevent multiple versions
>of my app running over a network.
>I have Aaron 's Windows Functionality Suite 2.5, but having
>difficulty understanding how to use the Win32Mutex for this purpose.
>Example code of how to implement to prevent multiple app instances
>much appreciated.
>
>
>Roger M. Clary
>Class One Software
>http://www.classonesoftware.com
>roger at classonesoftware dot com
>
>_______________________________________________
>Unsubscribe or switch delivery mode:
><http://www.realsoftware.com/support/listmanager/>
>
>Search the archives:
><http://support.realsoftware.com/listarchives/lists.html>
>
>
>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|