- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Sun, 14 Apr 2019 19:31:43 +0000
- To: public-hydra-logs@w3.org
Hmm. I though that HTTP 409 conflict and ETag are are enough, or am I wrong? Each new version of the resource should generate a new ETag value, thus both client and servers can detect changed resource and decide on what to do. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/190#issuecomment-483047080 using your GitHub account
Received on Sunday, 14 April 2019 19:31:44 UTC