OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

kmip message

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


Subject: Re: Question about test case KMIP 2.1 TC-ASYNC-10-21


The third status is just after a Poll has occurred - which means the asynchronousÂcorrelation value is no longer valid.
Passing in values that don't match in QueryAsynchronousRequests simply don't appear in the output - like in Locate - if you search and find no matches you get no results.
The specification talks about doing things with values that match - it doesn't talk about returning errors if the client passes in a no longer valid asynchronousÂcorrelation value.

Now if the QueryAsynchronousRequests happened before the Poll had occurred it would have returned (assuming the timingÂwas right) a Completed status.
But in this test case the Poll shows the valid completion of the original request - so the asynchronousÂcorrelation value is no longer held by the server (as there is nothing to return).Â

Tim.
Â

On Sun, Dec 1, 2019 at 2:49 AM Mark Joseph <mark@p6r.com> wrote:

The KMIP 2.1 specification has the following enumerationÂ

// Processing Stage Enumeration
SUBMITTED     1
IN PROCESS    2        
COMPLETED     3
But in test case TC-ASYNC-10-21 calls to the QueryAsynchronousRequests operation produces the following 3 results
(1)
      <AsynchronousRequest>
        <AsynchronousCorrelationValue type="ByteString" value="$ASYNCHRONOUS_CORRELATION_VALUE"/>
        <Operation type="Enumeration" value="Create"/>
        <SubmissionDate type="DateTimeExtended" value="$NOW"/>
        <ProcessingStage type="Enumeration" value="Submitted"/>
      </AsynchronousRequest>

(2)
  Â<AsynchronousRequest>
    <AsynchronousCorrelationValue type="ByteString" value="$ASYNCHRONOUS_CORRELATION_VALUE"/>
    <Operation type="Enumeration" value="Create"/>
    <SubmissionDate type="DateTimeExtended" value="$NOW"/>
    <ProcessingStage type="Enumeration" value="InProcess"/>
   </AsynchronousRequest>


(3) This is the completed case but the server still knows that the provided Asynchronous Correlation Value was valid otherwise
    it would return an error.  
    So why does the server not return "Completed" enumeration value or why do we have the "Completed" value in the enumeration if it is not used?
  <BatchItem>
    <Operation type="Enumeration" value="QueryAsynchronousRequests"/>
    <ResultStatus type="Enumeration" value="Success"/>
    <ResponsePayload>
    </ResponsePayload>
  </BatchItem>

Best,
Mark Joseph
P6R, Inc
408-205-0361



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