wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Improve recommendation for how to form transaction IDs (#1888)

Browse source 
Fixes: #1706
Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
This commit is contained in:
Johannes Marbach 2024-06-25 16:55:46 +02:00 • committed by GitHub
parent 7820771fdd
commit 7eda6ad299
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

1
changelogs/client_server/newsfragments/1888.clarification Normal file
View file

@ -0,0 +1 @@
Improve recommendation for how to form transaction IDs.

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.
From the client perspective, after the request has finished, the `{txnId}`
value should be changed by for the next request (how is not specified; a
monotonically increasing integer is recommended).
After the request has finished, clients should change the `{txnId}` value for
the next request. How this is achieved, is left as an implementation detail.
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
transaction ID is the same as a previous request, and the path of the