Preference for Skipping Status Monitor Resource Creation

[jinling-github]

An OData client may choose not to query the result of an async job. For example, for a DELETE request, the client might simply not wait for completion and assume that the operation is performed by the service on a best-effort basis. Currently, the client can only send a Prefer: respond-async header to avoid waiting. However, the request still creates a status monitor resource and allocates the service's resources to handle its lifespan.

We are wondering if a new preference, e.g., non-retrieval, could be added to express the intent of not querying the status monitor resource, so that no such resource needs to be created on the service side.

[mikepizzo]

New preference to fire-and-forget; can still return 202 with no location header and no async preference applied.
Also need a preference-applied to be unambiguous on what happened.

You should be able to combine prefer:respond-async and fire-and-forget, meaning the service should do one or the other. Service would typically do fire and forget if it can. What happens if combined with wait? Can wait=0 do the same thing?

Wait=0 seems clear that they want it to happen (or wouldn't have made the request) but don't care about the response.

But Wait=10 is ambiguous; does it mean that the client wants to cancel if the response is not available after 10 seconds, or that the client wants the request still to happen (i.e., the create/delete executed) they just don't care about the response?

Wait and respond-async are orthogonal to fire-and-forget.