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

make intro match order of sections as per max g-j feedback

Browse source
This commit is contained in:
Matthew Hodgson 2015-03-28 21:40:12 -04:00
parent 07c4d6cd21
commit c0e55bb99e
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
specification/10_client_server_api.rst
View file

@ -190,16 +190,16 @@ Events in a room
Room events are split into two categories:
:Message events:
These are events which describe transient "once-off" activity in a room:
typically communication such as sending an instant messaage or setting up a
VoIP call. These used to be called 'non-state' events.
:State Events:
These are events which update the metadata state of the room (e.g. room topic,
room membership etc). State is keyed by a tuple of event ``type`` and a
``state_key``. State in the room with the same key-tuple will be overwritten.
:Message events:
These are events which describe transient "once-off" activity in a room:
typically communication such as sending an instant messaage or setting up a
VoIP call. These used to be called 'non-state' events.
This specification outlines several events, all with the event type prefix
``m.``. However, applications may wish to add their own type of event, and this
can be achieved using the REST API detailed in the following sections. If new