This resource is somehow unique. The read operation overupdate is eventually consistent. Most of the time, it returns the previous state after an update. So the solution is to look for the header server-timing and keep reading until the one returned by the read handler is higher than the one from the update handler.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
This resource is somehow unique. The
readoperation overupdateis eventually consistent. Most of the time, it returns the previous state after an update. So the solution is to look for the headerserver-timingand keep reading until the one returned by thereadhandler is higher than the one from theupdatehandler.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.