Re: [wsrp-wsia] Issue #85: sessionID expires MUST/MAY

[Rich Thompson <richt2@us.ibm.com>]

While exceptional processing should be accounted for, not having strong
semantics here causes problems for entities managing an interaction with an
End-User. Does the current language (below) address your concerns about
exceptional processing at the Consumer?


  newRefHandle: A new transient and opaque handle the Producer is supplying
  for use on future invocations for this use of the entity. The Consumer
  MUST use this new value as the refHandle on subsequent invocations until
  either the Producer supplies another newRefHandle or the refHandle is
  becomes invalid by either the refHandleExpires duration expiring or a
  fault message from the Producer [A206]. Note that failures to use this
  handle on subsequent invocations (e.g. something exceptional caused the
  Consumer to lose track of it) will result in a loss of state and likely
  unexpected behavior for the End-User.



                                                                                                                  
                      Michael Freedman                                                                            
                      <Michael.Freedman@        To:       wsrp-wsia <wsrp-wsia@lists.oasis-open.org>              
                      oracle.com>               cc:                                                               
                                                Subject:  [wsrp-wsia] re: Issues for 10/7                         
                      10/15/2002 06:53                                                                            
                      PM                                                                                          
                                                                                                                  
                                                                                                                  



There are few issues this week that have been marked to move from
tentative to resolved that I don't think are ready yet.  Here are the
comments for those issues:

Issue #85: sessionID expires MUST/MAY
   I disagree with the proposed resolution.  MUST is too strong as a
consumer needs to be free to manage its resources. Also, why can a a
producer throw a fault indicating the entity session has expired?  I
thought that is only for initEnvironment?  I suggest the following
wording that excludes both the MUST and MAY words:
"The Consumer uses this new value as the
refHandle on subsequent invocations until either the Producer supplies
another newRefHandle or the
refHandleExpires duration indicates that the refHandle is no longer
valid.
Failure to pass this refHandle is analogous to prematurely terminating
the session.  Doing so may lead to unexpected or undefined user
interactions.  Consumers should only violate the above semantics  under
exceptional circumstances.  Producers, however need to protect
themselves and expect that an entity session may be "reset" on every
request."

    -Mike-







----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>