× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 26-Jul-2016 11:48 -0500, dlclark wrote:
On 26-Jul-2016 11:37 -0500, CRPence wrote:
[…] Ignored, only from the perspective of "Will the
specific-program adopt authority of the owner of the
specific-program", for which the value for USEADPAUT is moot.

However the USEADPAUT still maintains meaning in the "general"
sense, for what the effect is on adoption being held\maintained
from prior invocation levels. […]

OK, I think it is becoming clearer to me. From all of the
discussion I'm also given to understand that the resulting authority
is always cumulative. So, is the following correct?

USRPRF | USEADPAUT | Resulting Authority
-------|-----------|----------------------------
*USER | *NO | Current User Profile
*OWNER | *NO | Current User + Object Owner
*USER | *YES | Current User + Caller's Authority
*OWNER | *YES | Current User + Object Owner + Caller's Authority


That reflects my understanding; where "Caller's Authority" refers to the adopted authority from the prior invocation levels.

P.S. That is a /simplified/ view, in a sense; referring only to methods not achieved via not-yet-resolved pointers. That is because any invocation can use a pointer into which the authority has already been established; authority that was set by any other [non]adopting program that may no longer be in the stack.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.