Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

attorney pattern

8 views
Skip to first unread message

Nick Keighley

unread,
Nov 10, 2009, 4:57:47 AM11/10/09
to
Has anyone come across the "attorney pattern"? If remember aright it
gave controlled access to the private members of a class. The
"attorney" class was a friend, with privileged access (hence attorney)
which it then granted to a limited set of other classes. It could also
provide access to some members and not others. It probably goes by
other names. Googling for it was unproductive as it tended find stuff
about attourneys...

nick keighley

Daniel T.

unread,
Nov 10, 2009, 7:37:42 AM11/10/09
to
Nick Keighley <nick_keigh...@hotmail.com> wrote:

Proxy is used to "Provide a surrogate or placeholder for another object
to control access to it." Maybe Proxy is a generalization of your
"attorney pattern"?

johnza...@gmail.com

unread,
Nov 18, 2009, 2:49:45 PM11/18/09
to
On Nov 10, 7:37 am, "Daniel T." <danie...@earthlink.net> wrote:

No. He is referring to the C++ Attorney-Client Idiom, as published in
Dr. Dobb's C++ User Journal.

See: http://www.ddj.com/cpp/184402053

johnza...@gmail.com

unread,
Nov 18, 2009, 2:55:59 PM11/18/09
to
On Nov 18, 2:49 pm, "johnzabro...@gmail.com" <johnzabro...@gmail.com>
wrote:

Also, I forgot to mention that many people THINK they want to use an
Attorney-Client Idiom when really likely want David R. Redell's
Caretaker pattern. Since Attorney-Client Idiom strictly violates OO
semantics, Caretaker repositions the problem as an Object-Capability
one.

For an overview, see the papers:
* Paradigm Lost: Abstraction Mechanisms for Access Control by Mark S.
Miller and Jonathan Shapiro
* Paradigm Regained: Abstraction Mechanisms for Access Control by Mark
S. Miller and Jonathan Shapiro

0 new messages