Re: DynamicAttributeService

[Carol Burt <cburt@2ab.com>]

Hi,

I wrote:

>> 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.    
>
Konstantin replied
>
>I agree with your suggestion to remove the parameter. I believe it was a
typo.
>According to what I understood in the meeting the get_dynamic_attributes
should
>take only resource name, operation name, and static attributes.
>
I may be wrong, but I think it was John who wanted this parameter... the
context was the ability to provide some shortcuts for performance
enhancements in the implementation.  Anyway, I am planning to remove it for
now. 
>
>>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.    
>
>
>It should be a part of admin interface on DynamicAttributeService. I think we
>agreed to postpone specification of that interface until the revised
>submission.
>
Well I was never sure if we agreed to standardize this or not... :-)  Our
encapsulation line kept moving ;-)   I would like to put text in the
submission that states this administrative interface will be provided in
the final submission.

Carol

_________________________________________________________
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.