[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: WSIA 5/7/2002: [wsia][wsia-requirements][E904]
This is better. We had originally been asked to preclude from using "lifecycle" as the timeframe is indeterminate. Perhaps we should define the fact that we are transending different states of a service execution (that are under discussion in WSRP-WSIA interface subcommittee), as well as possibly different phases of an aggregate series of service executions (collaboration)?? E904 This specification SHOULD include operations and semantics related to persisting and using stateful information by AND ACROSS instances of the Producer's service. Thoughts welcome. Monica J. Martin Program Manager Drake Certivo, Inc. 208.585.5946 -----Original Message----- From: Rich Thompson Sent: Mon 5/6/2002 8:33 AM To: 'wsia@lists.oasis-open.org' Cc: Subject: RE: [wsia][wsia-requirements][E904] Even Lifecycle has been used in ways that confuse this (Lifecycle discussion includes the discovery of the existence of a service) ... I think we are trying to capture the persistence between different instances of a Producer's service. How about: E904 This specification SHOULD include operations and semantics related to persisting and using stateful information by instances of the Producer's service. Gil Tayar <Gil.Tayar@webcol To: Rich Thompson/Watson/IBM@IBMUS, lage.com> "'wsia@lists.oasis-open.org'" <wsia@lists.oasis-open.org> cc: 05/06/2002 08:44 Subject: RE: [wsia][wsia-requirements][E904] AM I agree - we have been evading this terminology issue for two long. How about rewording to use a consensual word - "Lifecycle": E904 This specification should include operations and semantics related to persisting stateful information between *Producer lifecycles*. This also pertains to E902. -----Original Message----- From: Rich Thompson [ mailto:richt2@us.ibm.com] Sent: Monday, May 06, 2002 15:19 To: 'wsia@lists.oasis-open.org' Subject: RE: [wsia][wsia-requirements][E904] I agree that the intent is to cover the need for an operation to indicate the persisting of information and the semantics of how that can be referenced in the lifecycle of a later 'session' between the Consumer and Producer. I'm gussing the confusing word here is 'interactions', but have no suggestions for a replacement. Gil Tayar <Gil.Tayar@webcol To: "'wsia@lists.oasis-open.org'" lage.com> <wsia@lists.oasis-open.org> cc: 05/05/2002 02:16 Subject: RE: [wsia][wsia-requirements][E904] AM The idea is that there be a mechanism in which the producer can persist information per user so that when it is invoked again, in another session/instance, it can retrieve the information again. For example, if the user enters their name, it can remember that name and prefill it next time. -----Original Message----- From: Alan Kropp [ mailto:akropp@epicentric.com] Sent: Saturday, May 04, 2002 04:49 To: 'wsia@lists.oasis-open.org' Subject: [wsia][wsia-requirements][E904] E904 This specification should include operations and semantics related to persisting stateful information for use in later interactions between the Consumer and Producer. Not sure what this one is trying to express. Is it the Handle? ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: < http://lists.oasis-open.org/ob/adm.pl> ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: < http://lists.oasis-open.org/ob/adm.pl> ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: < http://lists.oasis-open.org/ob/adm.pl> ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: < http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC