archive
/
matrix-spec-proposals
mirror of https://github.com/matrix-org/matrix-spec-proposals
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

minor edits

Browse Source
rav/proposal/dead_device_key_claims
Richard van der Hoff 7 months ago
parent 3273f436a3
commit e56c635533
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File

4
proposals/4072-exhausted_devices_in_key_claim_response.md
Unescape Escape View File

@ -7,7 +7,7 @@ handled. It is however explicit that unknown devices be omitted
from the response, and in practice Synapse (at least) treats both scenarios the from the response, and in practice Synapse (at least) treats both scenarios the
same. same.
This requires clients to keeo a record of which devices were included in the This requires clients to keep a record of which devices were included in the
request. This MSC proposes that such devices be included in the response. request. This MSC proposes that such devices be included in the response.
## Background ## Background
@ -113,7 +113,7 @@ HTTP request fails for any reason, there will be no such call.
So it would be easy to introduce a memory leak in this way. A correct So it would be easy to introduce a memory leak in this way. A correct
implementation might involve some sort of expiring map, or more substantial implementation might involve some sort of expiring map, or more substantial
changes to the API of `matrix-sdk-crypto`. In any case it is likely to be changes to the API of `matrix-sdk-crypto`. In any case it is likely to be
non-trivial compared with changing the behaviour on the client side. non-trivial compared with changing the behaviour on the server side.
### Variations in response shape ### Variations in response shape

Write Preview
Loading…
Cancel
Save