OpenCloud
/
MatrixSynapse
mirror of https://github.com/matrix-org/synapse
1
0
Fork 0
Code Issues Releases Wiki Activity

Add todo notes

pull/4/head
Erik Johnston 2014-10-02 14:38:53 +01:00
parent 82e278029c
commit 036333412d
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/specification.rst
View File

@ -849,6 +849,7 @@ Joining rooms
------------- -------------
.. TODO-doc kegan .. TODO-doc kegan
- TODO: What does the home server have to do to join a user to a room? - TODO: What does the home server have to do to join a user to a room?
See SPEC-30.
Users need to join a room in order to send and receive events in that room. A Users need to join a room in order to send and receive events in that room. A
user can join a room by making a request to |/join/<room_alias_or_id>|_ with:: user can join a room by making a request to |/join/<room_alias_or_id>|_ with::
@ -1389,6 +1390,10 @@ prefixed with ``m.``
m.room.message msgtypes m.room.message msgtypes
----------------------- -----------------------
.. TODO-spec
How a client should handle unknown message types.
Each ``m.room.message`` MUST have a ``msgtype`` key which identifies the type Each ``m.room.message`` MUST have a ``msgtype`` key which identifies the type
of message being sent. Each type has their own required and optional keys, as of message being sent. Each type has their own required and optional keys, as
outlined below: outlined below: