From 6fc4975c52ec3ed72b9234aa01c81551850c840d Mon Sep 17 00:00:00 2001 From: Hugh Nimmo-Smith Date: Fri, 14 Apr 2023 10:02:00 -0400 Subject: [PATCH] Make it clearer in the intro section what the problem is --- proposals/3970-device-scope-txnid.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/proposals/3970-device-scope-txnid.md b/proposals/3970-device-scope-txnid.md index 88eda966..33c6024f 100644 --- a/proposals/3970-device-scope-txnid.md +++ b/proposals/3970-device-scope-txnid.md @@ -14,6 +14,11 @@ The spec [reads](https://spec.matrix.org/v1.6/client-server-api/#transaction-ide > client logs out and back in between the `A` and `B` tokens, `TXN1` could be used > once for each. +The "client session" scope concept described can be complicated to implement. + +This MSC proposes that the scope of a transaction identifier is changed to something +that is easier to implement whilst maintaining required transaction semantics. + The transaction IDs appear in two parts of the Client-Server API spec: 1. As a identifier to allow the homeserver to make some `PUT` endpoints