OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-c-cpp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ISSUE 85: Proposed response



I propose that we respond to this comment with the following  (this would part of a e-mail that is a response to all of his comments):

The SCA C & C++ TC recommends reading and understanding the Assembly specification before trying to read and understand the C++ client and implementation specification.  The Assembly specification defines the core concepts, architecture and constructs for SCA.  There are some additional concepts defined in the Policy Framework that are also needed to understand parts of the C++ client and implementation specification.  The C++ client and implementation specification defines how the concepts, architecture and constructs  of the Assembly specification and Policy Framework are to be implemented by a SCA runtime that supports C++ component implementations and how C++ component implementations use the concepts, architecture and constructs.

A discussion of the architectural choices for SCA as a whole would need to be done by the Assembly TC as these choices are intentionally implementation technology/language independent.  If there are architectural choices specific to the to the implementation of SCA in either C++ or C that you believe would benefit from further discussion, the SCA C & C++ TC would welcome that input.

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]