[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
DynamicAttributeService
Hi,
Item 2
DynamicAttributeService get_dynamic_attributes()
This method takes a PolicyEvaluatorList as an input parameter... however
there are no methods on PolicyEvaluator that make sense for a
DynamicAttributeService to call. Since we agreed that PolicyEvaluators are
"replaceables" - they may be provided by different vendors and implement
different access policies, it isn't reasonable to expect that hidden
methods here would be very useful. :-) For this reason, I suggest we
remove this parameter for the initial submission and revisit the
performance considerations that were the catalyst for providing these refs
to the DynamicAttributeService there after the initial submission.
==
Item 3:
Also on DynamicAttributeService
We agreed that the dynamic attribute service would encapsulate any
"callbacks" to the application when necessary. This would be for the
purpose of determining how to create the new AttributeList that includes
the appropriate static and dynamic attributes to be passed to the other
HRAC evaluator objects. We also agreed - I think - that
DynamicAttributeService is a "singleton" object. I believe we need to
consider providing a standard way that a 3rd party application vendor can
register a dynamic attribute evaluator with the DynamicAttributeService for
a ResourceName.
_________________________________________________________
Carol Burt 2AB, Inc.
cburt@2ab.com Integration Architects
205-621-7455 www.2ab.com
Member, OMG Architecture Board OMG Domain Member
-- integrating yesterday's systems with today's technology --
----------------
Broadcast message to hrac-rfp from Carol Burt <cburt@2ab.com>.
Go to http://cadse.cs.fiu.edu/omg/hrac-rfp to browse the mail list archive.