David Logan wrote:
No, I didn't think you were arguing that WAIT/POST didn't work, and you do
definitely have some valid points. It would be *quite* difficult to use for
more advanced locking requirements, such as multiple tasks.
Task synchronization and locking only are tangentially related concepts.
(Of course, the suspension and un-suspension of the work unit, due to
lock contention/resolution, will usually require WAIT/POST buried in the
"guts" of the lock manager somewhere.) Maybe that's where the confusion
comes from. Just remember, a WAITing task is not necessarily (or even
usually) locked.
We can start a separate thread on locking if you like.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
