matrix-spec

Commit Graph

Author	SHA1	Message	Date
Travis Ralston	6c6c602845	Clarify that refreshed access tokens don't invalidate the scope of txnid (#1236 )	2 years ago
Travis Ralston	a91030f27b	Re-add paragraph about how some state keys are reserved (#1100 ) * Re-add paragraph about how some state keys are reserved Fixes https://github.com/matrix-org/matrix-spec/issues/1013 * changelog	2 years ago
Richard van der Hoff	36b02edfc2	Distinguish 'client' from 'federation' events (#3658 ) Fixes #3305 Fixes #3380 The idea here is to better distinguish between a 'raw' event (as we send over the wire), and the 'serialised' format, as sent in responses to the C-S api and in `PUT /_matrix/app/v1/transactions/{txnId}`. It's made more complicated by the fact that there are _two_ serialisation formats, one used by `/sync` and `/notifications`, and one by everything else (the difference being whether `room_id` is included). In an ideal world, we wouldn't repeat `SerialisedEvent` every time it's used, and instead just link to the first reference, but that's a job for another day. Another job for another day is to get rid of things like `sync_state_event.yaml` (which is now used only in one place, so should be inlined.)	3 years ago

Author

SHA1

Message

Date

Travis Ralston

6c6c602845

Clarify that refreshed access tokens don't invalidate the scope of txnid (#1236 )

Travis Ralston

a91030f27b

Re-add paragraph about how some state keys are reserved (#1100 )

* Re-add paragraph about how some state keys are reserved

Fixes https://github.com/matrix-org/matrix-spec/issues/1013

* changelog

Richard van der Hoff

36b02edfc2

Distinguish 'client' from 'federation' events (#3658 )

Fixes #3305 
Fixes #3380
 
The idea here is to better distinguish between a 'raw' event (as we send over the wire), and the 
'serialised' format, as sent in responses to the C-S api and in `PUT /_matrix/app/v1/transactions/{txnId}`.

It's made more complicated by the fact that there are _two_ serialisation formats, one used by `/sync`
and `/notifications`, and one by everything else (the difference being whether `room_id` is included).

In an ideal world, we wouldn't repeat `SerialisedEvent` every time it's used, and instead just link to the
first reference, but that's a job for another day.

Another job for another day is to get rid of things like `sync_state_event.yaml` (which is now used
only in one place, so should be inlined.)

3 Commits (1cdfbd3cd8e01d04b3875f297bc0ab27822f7ea2)