From 3fecfcd5e056a57ebc04ee51be38e89a60ce2d76 Mon Sep 17 00:00:00 2001 From: David Robertson Date: Mon, 13 Nov 2023 16:34:05 +0000 Subject: [PATCH] Rename M_DIRTY_WRITE -> M_CONCURRENT_WRITE "Dirty write" refers to a specific SQL phenomenon regarding transaction isolation, see e.g. https://blog.acolyer.org/2016/02/24/a-critique-of-ansi-sql-isolation-levels/ Instead, prefer the word "concurrent". --- proposals/3886-simple-rendezvous-capability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/3886-simple-rendezvous-capability.md b/proposals/3886-simple-rendezvous-capability.md index 90d2a70e7b4..57dfdde40be 100644 --- a/proposals/3886-simple-rendezvous-capability.md +++ b/proposals/3886-simple-rendezvous-capability.md @@ -165,7 +165,7 @@ HTTP response codes, and Matrix error codes: - `202 Accepted` - payload updated - `400 Bad Request` (`M_MISSING_PARAM`) - a required header was not provided. - `404 Not Found` (`M_NOT_FOUND`) - rendezvous URI is not valid (it could have expired) -- `412 Precondition Failed` (`M_DIRTY_WRITE`, **a new error code**) - when the ETag does not match +- `412 Precondition Failed` (`M_CONCURRENT_WRITE`, **a new error code**) - when the ETag does not match - `413 Payload Too Large` (`M_TOO_LARGE`) - the supplied payload is too large - `429 Too Many Requests` (`M_UNKNOWN`) - the request has been rate limited