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

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

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


Subject: [OASIS Issue Tracker] (ODATA-1484) Allow a client to query the status of an asynchronous request without returning the result if the request completed.


Hubert Heijkers created ODATA-1484:
--------------------------------------

             Summary: Allow a client to query the status of an asynchronous request without returning the result if the request completed.
                 Key: ODATA-1484
                 URL: https://issues.oasis-open.org/browse/ODATA-1484
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: Protocol
    Affects Versions: V4.01_OS
            Reporter: Hubert Heijkers


In some cases, the waiting for an asynchronous request to finish and actual processing of the result are separated even up to a point where the processing might [need to] be done in a different thread, process or even different [micro-]service. As it stands, querying the status monitor gives you the state of that process but if that state has been completed it also immediately includes the response of the completed asynchronous request.
I was wondering if it would it be possible to extend the existing protocol for asynchronous request handling in a way that this extra step could be injected.




--
This message was sent by Atlassian Jira
(v8.3.3#803004)


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