... maybe I shuoldn't name it getMutex, call it getLock, if you are more
familar with this... ...
the idea was to encapsulate the locking mechanism to avoid to have it 76
times, one for every dataarea (or whatever) to lock and reinventing the
wheel on and on. Once done this, you could invest some effort to enhance
functionality (more abstraction using names, instead hard coded synch
objects, creating the needed objects, as needed, enforce error handling by
sending escape message instead of return codes, flexibel wait times,
avoiding deadlocks).
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
