From: "Jay and Cathy Peterson" <JPeterson@PCBYTE.net>
Subject: Re: VAX Ada Tasks and VMS Lock Manager
Date: 1997/07/22
Date: 1997-07-22T00:00:00+00:00 [thread overview]
Message-ID: <01bc96ee$d38ac0c0$84ecced0@jpeterson> (raw)
In-Reply-To: 1997Jul22.070236.1@eisner
Larry Kilgallen <kilgallen@eisner.decus.org> wrote in article
<1997Jul22.070236.1@eisner>...
> In article <01bc965a$b5135f60$88ecced0@jpeterson>, "Jay and Cathy
Peterson" <JPeterson@PCBYTE.net> writes:
[snipped]
>
>
> But if you choose to manage your Lock Manager usage such that
> Tasks A, B, C and D each enqueue for their own Lock ID and do
> not share them (as is typical with most designs), the fact that
> subsequent Enqueue calls will not be granted until the exclusive
> holder Lock ID is demoted or dequeued effectively means that
> Tasks B, C, and D will not get the lock until Task A has
> demoted or dequeued its Lock ID. The affiliation between
> Tasks and Lock IDs, however, is totally under your control.
>
That answered my question; thank you for taking time to respond :)
Jay Peterson
prev parent reply other threads:[~1997-07-22 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01bc9579$39aaaf40$83ecced0@jpeterson>
1997-07-21 0:00 ` VAX Ada Tasks and VMS Lock Manager Larry Kilgallen
1997-07-22 0:00 ` Jay and Cathy Peterson
1997-07-22 0:00 ` Larry Kilgallen
1997-07-22 0:00 ` Jay and Cathy Peterson [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox