Multiple Users Concurrently Editing Processing Tables

[Fairlight]

On Sun, Jun 19, 2005 at 09:44:05PM -0400, Bob Stockler may or may not have
proven themselves an utter git by pronouncing:
> A thread on the filePro Mailing List the other day encouraged
> me to write a filePro Processing Table that could substitute
> for the "Define Processing" choice on the filePro Main Menu.
> 
> It permits but one user at a time to edit a processing table,
> writing a lockfile of it's own to prevent such.
> 
> If a user editing a table exits inappropritely, or doesn't exit,
> the lockfile remains.
> 
> If on UNIX/Linux, or on Windows and filePro v5.0.13 or later,
> the name of the user LOCKing it is shown as editing it if
> another user trys to edit it.

Key words:  "filePro processing table"

How'd you handle the possibility of a race condition without flock() or
fcntl() access via the fP language?

Granted, in 99% of the contexts in which it would be used, nobody's going
to notice, and it shouldn't fail if you did only what you stated you
did.  I'm just wondering what you did to account for the possibility (if
anything), as this is something I wouldn't think would be suited at all to
fP table coding in order to be -100%- foolproof.

Not knocking it, just curious about the details.

mark->
-- 
          *****   Fairlight Consulting's Software Solutions   *****
OneGate Universal CGI Gateway:                  http://onegate.fairlite.com/
FairPay PayPal Integration Kit:                 http://fairpay.fairlite.com/
RawQuery B2B HTTP[S] Client & CGI Debugger:     http://rawquery.fairlite.com/
Lightmail Mail Sending Agent:                   http://lightmail.fairlite.com/
FairView Image Viewer for Integration:          http://fairview.fairlite.com/