Closed GoogleCodeExporter closed 8 years ago
For best compatibility, should we acquire both the Local and the Global mutex?
Or does acquiring the Global mutex also block any application using the Local
mutex?
The code on the techPowerUp wiki suggests to use the Local mutex if it already
exists. But this could cause problems if there are other programs that use the
Global mutex only.
A which supports only Local creates a Local mutex
B which supports Local and Global just opens the Local, because it exists alreay
C which support only Global creates a Global because no Global exists so far
Or are there any situations where Local and Global are actually the same, and
acquiring both would cause the application to dead lock?
Original comment by moel.mich
on 10 Feb 2011 at 11:36
[deleted comment]
a) On most XP systems there is only one namespace, so you can't have both.
b) The only totally reliable solution is for ALL programs to use Global.
c) By using Local if Local exists on startup locking will work if a 3rd program
is then started and just uses Glocal then things will not work.
d) On W95 and NT4 you can't have a prefix.
e) On W2K and later Local\Access_ISABUS.HTP.Method and Access_ISABUS.HTP.Method
are the same.
f) AFAIK most programs have been changed to unconditionally use Global.
Original comment by r...@rh-software.com
on 10 Feb 2011 at 3:42
This issue was closed by revision r293.
Original comment by moel.mich
on 15 Mar 2011 at 5:55
Original issue reported on code.google.com by
r...@rh-software.com
on 9 Feb 2011 at 9:35