[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue-93 Proposal for External Attachment of Intents
The detailed proposal in both PDF and Word Formats is attached. The motivation behind this change is to enable complete separation of Policy from executable code and allow Policy requirements to be changed independently of the executables. This would happen, for example, if corporate policy requirements changed or if new intents with new or modified functionality were introduced. A we have argued in the past, policy and executables are often managed independently by different departments and follow different lifecycles. Consider a situation in which a module imported from another source has to be integrated with separately developed applications. This can occur, for example, in Cloud Computing. In such a case, it would be best if the intents on the imported module were attached externally as this would allow them to be changed easily to conform to the policy requirements of the larger application. The proposal for external attachment of intents parallels the mechanism for policySets in that it uses a new @attachTo attribute which works in exactly the same way as the @attachTo attribute on policySets. The rules for precedence among directly attached and externally attached intents parallel the rules for directly attached and externally attached policySets. When redeploying due to changes in policy requirements -- this is the killer app for this facility -- external attachment of intents precedes the external attachment of policySets. Please take a look. We can discuss on Monday's call. -- All the best, Ashok
SCA Policy Framework CD02-Rev6-Issue93.docx
SCA Policy Framework CD02-Rev6-Issue93.pdf
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]