From bd48e4ab6dc21d2c595243a6f61e7f88587a51d2 Mon Sep 17 00:00:00 2001 From: Kegsay Date: Wed, 21 Jan 2015 13:09:16 +0000 Subject: [PATCH] Move invite data to a note Done in order to clarify that this API "should probably have something like this" rather than "will have this". --- drafts/general_api.rst | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/drafts/general_api.rst b/drafts/general_api.rst index 626b3750..5a027d15 100644 --- a/drafts/general_api.rst +++ b/drafts/general_api.rst @@ -106,6 +106,13 @@ Notes: Global initial sync API ``[Draft]`` ------------------------------------- .. 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: - Will need some form of state event pagination like we have for message @@ -126,10 +133,6 @@ Outputs: - # members - max of limit= message events - 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: - 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.