client prioritization

[Bill Frantz]

At 1:22 PM -0800 5/5/98, Jonathan S. Shapiro wrote:
>I am finding that there are circumstances where I want to control
>which capability holders can call a domain.
>
>More specifically, I find that I am writing programs that have "helper
>processes", and that these programs get into states where it is
>desirable to allow ONLY the helper processes to call.
>
>For example, a process is temporarily unable to service more clients
>but still needs to be called by the timer tick helper process in order
>to get out of the "stuck" state.  The goal is to have the clients
>unaware that they were temporarily blocked.
>
>Was there a convention for how to do this in KeyKOS?

The closest I can think of was in the X.25 support.  The circuit key would
support only one "SendData" operation at a time.  If a second operation was
initiated, it was rejected with a specific return code.

One level of indirection would allow the inner guts of the system to
continue running while the external entry points remained busy.


-------------------------------------------------------------------------
Bill Frantz       | If hate must be my prison  | Periwinkle -- Consulting
(408)356-8506     | lock, then love must be    | 16345 Englewood Ave.
frantz@netcom.com | the key.     - Phil Ochs   | Los Gatos, CA 95032, USA