OASIS Web Services Interactive Applications TC

RE: [wsrp][wsia][wsrp-wsia joint interfaces][Draft Spec 0.44]

  • 1.  RE: [wsrp][wsia][wsrp-wsia joint interfaces][Draft Spec 0.44]

    Posted 06-03-2002 14:40
     MHonArc v2.5.2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    wsia message

    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


    Subject: RE: [wsrp][wsia][wsrp-wsia joint interfaces][Draft Spec 0.44]


    Title: Message
    I agree to both points.
     
    To your point #1: The two operations don't even necessarily have the same signature, you can imagine the persistent one being something like createPersistentThingy(persistentThingyHandle, boolean indicating clone/copy), etc.
     
    To your point #2: The question of how to describe optional operations (portTypes or pre-defined responses or other means) is there across other operations as well (e.g., setProperties). It also needs to be resolved, although probably under a different group (and I have the same preference as you). However, one way or another - using a separate operation for semantically distinct functions provides a much clearer way to document and understand the "optionality" of the operation.
     
    Per one of the questions raised in the draft that you circulated, below is an attempt to describe the Transient Thingies in a way that captures both transient instance and sessions. I wonder if people have comments about the text below:
     
    Transient Thingies
     
    Transient Thingies allow Producers to associate multiple requests with the same user interaction. At any point within the user interaction, Producers MAY return a Transient Thingy, which the Consumer MUST pass on subsequent request that belong to the same user interaction.
     
    For example, the operation
     
    getFragment (...)
     
    returns, among other things, a Transient Thingy. It is possible for Producers to include in the Transient Thingy a token identifying a Session object created in the underlying application server.
     
    Consumers MAY also explicitly request Producers to create a Transient Thingy in the beginning of the user interaction using the operation
     
    createTransientThingy (...)
     
    This function is provided for convenience and completeness only, and the Producer MAY change the Transient Thingy by returning a different value in subsequent calls.
     
    Eilon