[OASIS Issue Tracker] (ODATA-1610) Clarify use of 'wait' preference without 'respond-async' preference

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Hubert Heijkers created ODATA-1610:
--------------------------------------

             Summary: Clarify use of 'wait' preference without 'respond-async' preference
                 Key: ODATA-1610
                 URL: https://issues.oasis-open.org/browse/ODATA-1610
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: Protocol
    Affects Versions: V4.01_OS
            Reporter: Hubert Heijkers
             Fix For: V4.01_ERRATA01


The specification as is is a bit unclear around the behavior/expectation that a client might have from a server when a client is specifying a {{wait}} preference in case there is not also a {{respond-async}} preference.

8.2.8.10 describing this behavior in our specification, whilst referencing [RFC7240|https://datatracker.ietf.org/doc/html/rfc7240], states that if the respond-async preference has not been specified, the service MAY interpret the wait as a request to timeout after the specified period of time.

The referenced [Prefer Header for HTTP specification in section 4.3|https://datatracker.ietf.org/doc/html/rfc7240#section-4.3] pertaining to the "wait" preference states however that a service can choose to utilize an asynchronous processing model in that case and return a 202 Accepted.

Looking at 9.1.3 in the OData protocol specification pertaining to the 202 Accepted Response Code, whilst stating that is returned when an asynchronous request hasn't been completed yet, refers to the sections on asynchronous requests.

Whilst one doesn't preclude the other it has caused confusion in our interpretation/implementations so I thought some clarification might be in order.



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