You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
matrix-spec/data/api/application-service
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
..
definitions Change RST code formatting markup to Markdown 3 years ago
protocols.yaml Fix the response for `GET /_matrix/app/v1/thirdparty/protocol/{protocol}` (#3675) 3 years ago
query_room.yaml Change RST code formatting markup to Markdown 3 years ago
query_user.yaml Change RST code formatting markup to Markdown 3 years ago
transactions.yaml Distinguish 'client' from 'federation' events (#3658) 3 years ago