Review comments

pull/977/head
Kegan Dougal 9 years ago
parent 6a0595bc46
commit c82c07ddd2

@ -23,9 +23,8 @@ restrictions on sizes per key:
- ``state_key`` MUST NOT exceed 255 bytes. - ``state_key`` MUST NOT exceed 255 bytes.
- ``type`` MUST NOT exceed 255 bytes. - ``type`` MUST NOT exceed 255 bytes.
- ``event_id`` MUST NOT exceed 255 bytes. - ``event_id`` MUST NOT exceed 255 bytes.
- ``user_id`` MUST NOT exceed 255 bytes.
Some event types have additional sizes restrictions which are specified in Some event types have additional size restrictions which are specified in
the description of the event. Additional keys have no limit other than that the description of the event. Additional keys have no limit other than that
implied by the total 65 KB limit on events. implied by the total 65 KB limit on events.

@ -296,7 +296,7 @@ be obtained by visiting the domain specified. They are case-insensitive. Note
that the mapping from a room alias to a room ID is not fixed, and may change that the mapping from a room alias to a room ID is not fixed, and may change
over time to point to a different room ID. For this reason, Clients SHOULD over time to point to a different room ID. For this reason, Clients SHOULD
resolve the room alias to a room ID once and then use that ID on subsequent resolve the room alias to a room ID once and then use that ID on subsequent
requests. Room aliases MUST NOT exceed 255 bytes. requests. Room aliases MUST NOT exceed 255 bytes (including the domain).
When resolving a room alias the server will also respond with a list of servers When resolving a room alias the server will also respond with a list of servers
that are in the room that can be used to join via. that are in the room that can be used to join via.

Loading…
Cancel
Save