Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-23 03:34:08 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Improve recommendation for how to form transaction IDs

Browse source 
Fixes: #1706
Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
This commit is contained in:
Johannes Marbach 2024-06-25 11:04:28 +02:00
parent 9f2891d95c
commit 17dc1a26ca
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
content/client-server-api/_index.md
View file

@ -251,9 +251,10 @@ the request idempotent.
The transaction ID should **only** be used for this purpose. The transaction ID should **only** be used for this purpose.
From the client perspective, after the request has finished, the `{txnId}` After the request has finished, clients should change the `{txnId}` value for
value should be changed by for the next request (how is not specified; a the next request. How this is achieved, is left as an implementation detail.
monotonically increasing integer is recommended). It is recommended that clients use either version 4 UUIDs or a concatenation
of the current timestamp and a monotonically increasing integer.
The homeserver should identify a request as a retransmission if the The homeserver should identify a request as a retransmission if the
transaction ID is the same as a previous request, and the path of the transaction ID is the same as a previous request, and the path of the