Re: [provision] Suggested text for version 3.1.1

[Gary P Cole <Gary.P.Cole@Sun.COM>]

Jeff,

Could you take a look at the Conversational flow section and see whether 
it is now okay?  I remember that you raised this issue with draft 4, and 
I tried to address it in draft 5.  I reworded to avoid the word 
"blocking".  I also removed a paragraph or two that suggested order 
inappropriate to a connectionless protocol.

However, I still like the diagrams and the explanation of the simple 
case (now called "orderly alternation") and the more complex case (now 
called "multiple outstanding requests").  We found that we needed 
diagrams like these in order to understand one another when we discussed 
this at the Austin Face-to-Face.

I admire the brevity of your suggested text. It also seems very 
accurate.  However, in the case where a provider chooses asynchronous 
execution for an operation that omitted requestID, wouldn't the provider 
still need to return a requestID (even if the transport mehanism is a 
synchronous request-response mechanism)?

Bohren, Jeffrey wrote:

> This is my suggested verbiage for section 3.1.1 Conversational Flow:
>
>  
>
>  
>
> The SPML conversational flow will have a response for every request. 
> Each SPML request SHOULD contain a reasonably unique request ID. If 
> the transport mechanism used for the conversion is a synchronous 
> request response mechanism (such as SOAP/HTTP) the SPML request ID MAY 
> be omitted.
>
>  
>
> SPML responses must be responses to exactly one SPML Request. All SPML 
> responses SHOULD contain the ID of the SPML request they are in 
> response to. If the transport mechanism used for the conversion is a 
> synchronous request response mechanism (such as SOAP/HTTP) the SPML 
> request ID MAY be omitted from the response.
>
>  
>
>
>
> ------------------------------------------------------------------------
>
> *Jeff Bohren*
>
> 13577 Feather Sound Drive, Suite 200, Clearwater, FL 33762
>
> tel: 727.561.9500 x219
>
> fax: 727.374.0171
>
> Jeffrey_Bohren@bmc.com <mailto:Jeffrey_Bohren@bmc.com>
>
> www.bmc.com <http://www.bmc.com/>
>
>  
>