On Sep 30, 2007, at 8:31 PM, Brian Rathbone wrote:
> 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.
>
> -- snip --
> 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.
The situation I'm looking at is one in which the user installs my app
on a network drive and then launches the app concurrently from
multiple clients.
From my testing, this is possible on a Win platform.
I want to prohibit this unless a site license has been purchased.
I thought about installing a small hidden file upon launch,
preventing other launches if that file is present, then deleting the
file at exit.
The problem, which quickly became apparent, is that if the app
crashes, the file is left in place preventing any launches.
Suggestions gratefully welcomed.
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>
|