Post by tophercantrell on Jul 9, 2018 14:57:13 GMT
Our Redfish implementation has no synchronization between callers. For example, one caller sends a POST action to clear the logs. This takes a second or two to clear. The caller doesn't get a response back until it is done.
But while the first caller is waiting, another request comes in for the same resource. The second caller gets the state of the logs halfway through being cleared.
Is there an agreed upon mechanism to have one caller wait on a resource that is being changed?
In many "race conditions", the Etag concepts are there to resolve these issues. In the particular case you mentioned, no, there is no mechanism. Regardless of when the log was cleared, the second caller will eventually get 404 errors and will have to handle that.