NEW ISSUE: Clarify relationship of conversational interfaces and scope

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

Target: C++ and C specifications

Description:  The Java TC has approved some clarifications to the
relationship of Conversational interfaces and conversational scope.  Specifically
they added these words to the equivalent of section 2.3.4 of our specifications:
A conversational
scoped class MUST NOT expose a service using a non-conversational interface.
and these words to the section on conversational
services (equivalent of 5.2 for C++ and 4.2 for C)
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, typically through
routing each operation invocation associated with the conversation to the
same 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 ComponentContext.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.


Proposal: 
Add these same clarifications to our specifications with the obvious and
appropriate modifications to the C++ and C specifications.

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

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