On 11/5/2014 8:54 AM, Kevin Passey wrote:
I've written some RCP based applications - and this is just off the
top of my head...would a lock file work...like OO does - create a
.~lock.filename-to-update in the same directory, if it does not exist
create it and go ahead and update - If the file does exist then it's
locked...when you've finished your updates remove the lock file so
that another workstation can get access to the file. The lock file
could also include the function name could it not?

This lock file needs to exist in the IFS, as it's specific to a system. And the mere existence of the file isn't sufficient because, if the application exits unexpectedly, the file might remain.

I needed to create a true lock on a file.

Another approach I was considering was to create a data area in QGPL and establish an exclusive lock on that, but I decided to go with the IFS file instead.

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.