Re: process blocking

["P Hull" <p.hull@msw.com>]

> > Hi, I know this is possible, but how does one go about having a process
(p1)
> > siezing control of another process (pMain) such that no other process
(p2,
> > p3, .. pn) is able to access pMain? I am guessing you define one channel
and
> > maintain access to this channel? I have no idea how to implement such
> > blocking.
>
> If you can use an Ada task for your "process", and by "access" you
> mean "rendezvous with", then this is a matter of visibility; make sure
> task pMain is only visible to task p1. Declaring pMain in a private
> child of the package that declares p1 is one way to do this.
>
> However, that is a static solution. If you need to change which tasks
> are able to rendezvous with pMain at run time, you'll need a different
> mechanism.
>
> If you explain more about why you think you need to do this, there is
> probably another way to accomplish it.

Hi thanks for the reply.

Oh i was not looking for a static solution. pMain is visible to all tasks
p1..pn. The first task (i.e. one of p1..pn based upon some timing mechanism)
will rendezvous with pMain and seizes pMain. And once pi has finished
whatever it wants to do with pMain, some other task within p1..pn will then
next rendezvous with pMain and seize it, and once finished .. etc etc

I know this should be simple to implement. Thanks for any help

Peter