Przemek:
>> Something has changed for this case since Aug 2007 ?
>I created new code for MT mode which also can use BSD or POSIX locks
>for deny flags emulation so now it works between aliased work areas
>even in single process.
>This code were copied from Harbour repository to xHarbour CVS by:
> 2008-10-22 10:30 UTC+0100 Miguel Angel Marchuet <miguelangel at
>marchuet.net>
>even with my original ChangeLog notes but without even single word that
>these were my modifications :-(
>So this code is present in xHarbour. I haven't checked if it was ported
>correctly or not. Few times in last years my code from Harbour was
>copied without necessary updates to work correctly with xHarbour
>internal structures so you should ask about details xHarbour
>developers.
[...]
>Code is present but I do not have time to test current xHarbour CVS
>locate the bugs and document them. The are bugs I reported four or more
>years ago to xHarbour devel list and never fixed though some of them
>are even registered at xHarbour bug track so I think it's waste of
>time.
Thanks, with these explanations now is more clear:
- In Linux nothing prevent two applications open file in EXCLUSIVE from
each side
- Harbour applications can emulate EXCLUSIVE mode if them are build with
this feature
- Maybe xHarbour have same feature if it was properly copied/implemented
- So EXCLUSIVE may work between Harbour-xHarbour applications if work
properly in xHarbour
- hbnetio is an alternative in remote environment to properly manage
EXCLUSIVE, in place of Samba
I found this old subject due I was searching for "locking-scheme" to
ensure proper implementation.
Until now my conclusions are:
- Two applications, one build with Harbour and other with xHarbour may
have locking-corruption problems if each one is using a different
"locking scheme" in same RDD type
So we must to check which is default "locking-scheme" in each compiler
or force same in both
- Two applications, both build with Harbour may have locking-corruption
problems if each one is using a different "locking scheme" in same RDD type
So we must to check which is default "locking-scheme" in each build or
force same in both builds
- Two applications, one build with (x)Harbour and other with other
compiler (Clipper, FoxPro, ... ) may have locking-corruption problems if
each one is using a different "locking scheme" in same RDD type
So we must to check which is default "locking-scheme" in each build or
force same in both builds
I was relying in default "locking scheme" in any build
David Macias
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
