NEW ISSUE: Concurrency Model for each scope

[Bryan Aupperle <aupperle@us.ibm.com>]

Target:      
         SCA C++ and C C&I Specifications:
 sca-cppcni-1.1-spec-cd01-rev3.doc and sca-ccni-1.1-spec-cd01-rev3.doc
(section 2.3 of each spec).

Description: 
From (http://www.osoa.org/jira/browse/JAVA-61):
The spec needs language to describe
the concurrency model that a component developer needs to be prepared for
when using any of the scopes. For example, the spec never describes whether
or not a composite scoped implementation needs to be able to support concurrent
execution on the same runtime instance. 

The Java TC at a Nov. F2F adopted
the following:

1) Stateless Scope
Single threaded - the SCA runtime
MUST ensure that an implementation instance object is only ever dispatched
on ONE thread at any one time. In addition, within the SCA lifecycle of
an instance, the SCA runtime MUST only make a single invocation of one
business method.  (NB the SCA lifecycle might not correspond to the
Java object lifecycle due to runtime techniques such as pooling)
2) Composite Scope
Multi-threaded - the SCA runtime
MAY run multiple threads in a single implementation instance object and
it MUST NOT perform any synchronization
3) Conversation scope
Multi-threaded - the SCA runtime
MAY run multiple threads in a single implementation instance object and
it MUST NOT perform any synchronization

Proposal:

Awaiting final wording from Java

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