Post by puwen on May 25, 2022 12:25:53 GMT
Hi all,
I found this description in [12.2 Asynchronous operations] of the Redfish Spec.
HTTP GET, PUT, and PATCH operations should always be synchronous.
Clients shall be prepared to handle both synchronous and asynchronous responses for HTTP GET, PUT, PATCH, POST, and DELETE requests.
So my understanding is that HTTP GET/PUT and PATCH must be synchronous.
HTTP POST/DELETE follows the project design, asynchronous/synchronous is acceptable.
And I can put it another way:
The result of HTTP PATCH (GET/PUT) operation cannot be represented by [Task Resource].
Or the HTTP PATCH response cannot contain a "Location" header.
If there is any misunderstanding, please correct me, thank you.
BR,
Puwen
I found this description in [12.2 Asynchronous operations] of the Redfish Spec.
HTTP GET, PUT, and PATCH operations should always be synchronous.
Clients shall be prepared to handle both synchronous and asynchronous responses for HTTP GET, PUT, PATCH, POST, and DELETE requests.
So my understanding is that HTTP GET/PUT and PATCH must be synchronous.
HTTP POST/DELETE follows the project design, asynchronous/synchronous is acceptable.
And I can put it another way:
The result of HTTP PATCH (GET/PUT) operation cannot be represented by [Task Resource].
Or the HTTP PATCH response cannot contain a "Location" header.
If there is any misunderstanding, please correct me, thank you.
BR,
Puwen
