• Subject: RE: Performance Question - Authority check rate exceeded gui
  • From: "Cotes, Steven" <cotess@xxxxxxxxxxx>
  • Date: Sat, 22 Nov 1997 11:54:51 -0800

thanks for looking up the order, off the top of my head
I couldn't remember and wasn't near my books.
The significant point for I meant for John Cirocco was
that if most of your object access is via public authority
and you have even one profile with less than public,
it causes extra checking for everyone else using

You ask about adopting authority impacting performance.
I'd like confirmation on this also, maybe someone else can

My understanding has been that, adopting adds overhead
but that since authority is usually granted sooner in the
check order it becomes a wash or slight net gain.

Has anyone on the list tested this ?

 -Steve Cotes


> Hi
> Checking order;
> 1. Individual User Profile
>       All object special authority?
>       Object Authority to object?
>       Authorization List with object?
> 2. Group Profile
>       All object special authority?
>       Object authority to object?
>       Authorization List with Object?
> 3. Public Authority
>       Object Authority(public authority>)
>       Authorization list with object?
> Soltis's book says that;
> "The first authority that is found is used, unless there is a program
> adoption.  In this case, the adopted authority is added to the first
> authority found in the search."
> (BTW Sys/38 was accumulative.  Big change when we moved to AS/400)
> My question if you program adopts, does it sloooow down the
> checking???
> John Carr
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].