SCA C and C++ Telecon (Conference Call) | |
Name | SCA C and C++ Telecon (Conference Call) |
Time | Thursday, 14 February 2008, 11:00am to 12:00pm EST
(Thursday, 14 February 2008, 04:00pm to 05:00pm UTC) |
Description | Chat Room http://webconf.soaphub.org/conf/room/sca-c-cpp-TC |
Minutes | 0. Role Bryan Aupperle Andrew Borley David Haney Pete Robbins 1. Agenda bashing 2. Accept minutes from SCA-C-C++ TC meeting of 31 January Minutes approved 3. Action Items a. AI-2 (Pete): C++ header files 4. New Issues a. http://www.osoa.org/jira/browse/CCPP-33 Use of Dependency injection Issue Accepted b. http://www.osoa.org/jira/browse/CCPP-34 Clarify relationship of Conversational interfaces and scope Issue Accepted c. http://www.osoa.org/jira/browse/CCPP-35 Replace ##any with ##other Issue Accepted 5. Issue Discussion a. http://www.osoa.org/jira/browse/CCPP-34 Clarify relationship of Conversational interfaces and scope (if accepted) Revised resolution accepted: To section 2.3.4 of our specifications add: A conversational scoped class MUST NOT expose a service using a non-conversational interface. To the section on conversational services (5.2 for C++ and 4.2 for C) add: A class which provides a service with a conversational interface can have any scope. In particular, it is not necessary for the class to have conversation scope. If the class has conversation scope, the class benefits from the runtime maintaining state associated with the conversation, by routing each operation invocation associated with the conversation to the same logical instance of the class, with state data held in instance variables within the class. However, for classes of any scope, when an operation of a conversational interface is executing, the ServiceReference::getConversationID() returns the conversation ID of the conversation. The conversation ID can be used by the class as an index to store and to look up state data associated with the conversation, using some suitable storage mechanism. [With appropriate changes for C] b. http://www.osoa.org/jira/browse/CCPP-35 Replace ##any with ##other (if accepted) Resolution in JIRA Accepted c. http://www.osoa.org/jira/browse/CCPP-33 Use of Dependency injection (if accepted) Discussion concluded that we want to not use dependency injection. This implies that when complex types are used as parameters or return values an external data binding is needed. SDO will be a required data binding, but others may be used. How the data binding to be used will be specified is TBD. 6. Potential Committee Draft Agreed it is appropriate to have Committee Drafts one the Assembly TC has one. 7. AOB |
Agenda | 0. Role 1. Agenda bashing 2. Accept minutes from SCA-C-C++ TC meeting of 31 January 3. Action Items a. AI-2 (Pete): C++ header files 4. New Issues a. http://www.osoa.org/jira/browse/CCPP-33 Use of Dependency injection b. http://www.osoa.org/jira/browse/CCPP-34 Clarify relationship of Conversational interfaces and scope c. http://www.osoa.org/jira/browse/CCPP-35 Replace ##any with ##other 5. Issue Discussion a. http://www.osoa.org/jira/browse/CCPP-34 Clarify relationship of Conversational interfaces and scope (if accepted) b. http://www.osoa.org/jira/browse/CCPP-35 Replace ##any with ##other (if accepted) c. http://www.osoa.org/jira/browse/CCPP-33 Use of Dependency injection (if accepted) 6. Potential Committee Draft 7. AOB |
Submitter | Dr. Bryan Aupperle |
Group | OASIS Service Component Architecture / C and C++ (SCA-C-C++) TC |
Access | This event is visible to OASIS Service Component Architecture / C and C++ (SCA-C-C++) TC and shared with
|