File Locking with Cooperative Semaphores

[orbs 197]

i find it hard to follow the SQL code, but that's probably because i'm not an SQL expert...

anyway this UDF is a general-purpose tool (also capable of handling SQLite "lock", among many others), so i think youshould post this SQL code in one of the SQLite-related threads (or a new thread), where SQLite users can find it more easily, because the question of "locking" SQLite DB over network is repeatedly asked.

[orbs 197]

i needed to know if, when a semaphore was created successfully, was an ancient semaphore needed to be cleaned-up.

so i added the usage of @extended in _CFS_RequestSemaphore() so it is set to 1 if cleanup of ancient semaphore was due:

Func _CFS_RequestSemaphore($sRequestedResource, $iTimeout = 300, $iClean = 900)
    Local $sCFS_Semaphore = _CFS_ResourseLockName($sRequestedResource)
    Local $iStart = TimerInit()
    Local $iExtended = 0
    While True
        If _CFS_LockAge($sCFS_Semaphore, $iClean) Then ; Too old?
            _CFS_RemoveLock($sCFS_Semaphore)
            $iExtended = 1
        EndIf
        If TimerDiff($iStart) > ($iTimeout * 1000) Then ; have we timed out?
            Return 0
        Else
            If _CFS_CreateLock($sCFS_Semaphore) Then Return SetExtended($iExtended, 1) ; did we get the lock?
        EndIf
        Sleep(100) ; didn't get a lock, pause and try again
    WEnd
EndFunc   ;==>_CFS_RequestSemaphore

[jchd 1,450]

Zedna,

Sorry for the very late followup, but this scheme doesn't work reliably. You hit the problem of individual local cacheing of the remote DB by SQLite page cache in as many "clients" which have a live connection to it. There are other, lower-level issues with that which all make the scheme pretty risky.

SQLite has no clue whether the open connection is on a local drive or remote mapped drive.

[willichan 220]

Sorry that I haven't chimed in for a while here.

I am always open to improvements to the UDF.  One thing to clarify though.

Even though I initially wrote this for an SQLite project, it is for locking any resource, not just SQLite databases.  I have also used this to keep multiple scripts that share an INI file from stomping on each other, as well as for scripts running on multiple PCs writing to a single log file.

[jchd 1,450]

Granted. I was only warning.

[willichan 220]

Granted. I was only warning.

​I was really more responding to Zedna, but like I said, I am always open to improvements.