Support to requests that are processed asynchronously
Issue
Another use case covered in JSON:API is the possibility for requests to be submitted to the server which will accept it and process it in a later moment. This feature frees the connection for operations that take a long time. As a response to these requests, the client receives a 202 - Accepted
status code response but is left without knowing, at the time, the success of the request.
Proposal
Since we are focusing at transaction-like operations at first (where the client always knows the result of the request), should we exclude 202 - Accepted
responses from the standard? This could be revisited once in-bulk operations are incorporated, for instance.
Edited by Claudenir M. Fonseca