Issue 2395: Clarification on whether stateID manages session or state access (currency-rtf) Source: (, ) Nature: Revision Severity: Summary: Summary: In general the decision needs to be made as to whether a given stateIdentifier is used to indicate the boundaries of a session or a simple configuration, as it currently seems to attempt to support both. Whichever direction is chosen, all of the interfaces that accept a stateIdentifier as an argument should be revisited to ensure that the intent of the interface is still properly supported. e.g. Should the currency component still offer a “connectionless” interface to its consumers? Resolution: closed, no action taken Revised Text: Actions taken: January 11, 1999: received issue May 4, 2000: closed issue Discussion: Discussion: It is only there to support state access. A client can use the currency service in a separate session and use the same stateId in order to get the equivalent state applied. It will still be a connectionless interface. End of Annotations:===== Return-Path: From: Robert_Mickley@CYBORG.COM X-Lotus-FromDomain: CYBORG@CYBORG_NET To: issues@omg.org cc: Robert_Mickley@CYBORG.COM, Amy_Griffis@CYBORG.COM Date: Mon, 11 Jan 1999 21:28:52 -0700 Subject: Currency RTF Issues Content-Disposition: inline Today is the deadline for comments for the Currency RTF. Below is an itemized list of additions to that list. Issue Title: Clarification on whether stateID manages session or state access Issue Type: Text Revision Issue Description: In general the decision needs to be made as to whether a given stateIdentifier is used to indicate the boundaries of a session or a simple configuration, as it currently seems to attempt to support both. Whichever direction is chosen, all of the interfaces that accept a stateIdentifier as an argument should be revisited to ensure that the intent of the interface is still properly supported. e.g. Should the currency component still offer a interface to its consumers?