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

Move invite data to a note

Browse source 
Done in order to clarify that this API "should probably have something like this" rather than "will have this".
This commit is contained in:
Kegsay 2015-01-21 13:09:16 +00:00
parent e309db547a
commit bd48e4ab6d
1 changed files with 7 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

11
drafts/general_api.rst
View file

@ -106,6 +106,13 @@ Notes:
Global initial sync API ``[Draft]`` Global initial sync API ``[Draft]``
------------------------------------- -------------------------------------
.. NOTE:: .. NOTE::
- The output to this should also have something like:
For each room the user is invited to:
- The invite event
- Other state info (e.g. room name, topic, join_rules to know if pubilc)
- # members?
so clients know more information about the room other than the user_id of the
inviter, timestamp and the room ID.
v2.1: v2.1:
- Will need some form of state event pagination like we have for message - Will need some form of state event pagination like we have for message
@ -126,10 +133,6 @@ Outputs:
- # members - # members
- max of limit= message events - max of limit= message events
- room ID - room ID
- For each room the user is invited to:
- The invite event
- Other state info (e.g. room name, topic, join_rules to know if pubilc)
- # members?
Notes: Notes:
- If a chunk token is applied, you will get a delta relative to the last request - If a chunk token is applied, you will get a delta relative to the last request
performed with that streaming token rather than all the rooms. performed with that streaming token rather than all the rooms.