mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-08-04 15:07:47 +02:00
Compare commits
2 commits
61f7a6765f
...
5cffbf6552
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
5cffbf6552 | ||
|
|
4d310046a1 |
|
|
@ -0,0 +1 @@
|
|||
Add further normative language in mutual rooms server behaviour.
|
||||
|
|
@ -6,9 +6,9 @@
|
|||
|
||||
#### Server behaviour
|
||||
|
||||
The server may decide that the response to this endpoint is too large, and only return a
|
||||
subset of the results. In this case, the server should populate the optional field `next_batch`
|
||||
with an [opaque identifier](/appendices/#opaque-identifiers). The client may then supply
|
||||
The server MAY decide that the response to this endpoint is too large, and only return a
|
||||
subset of the results. In this case, the server MUST populate the optional field `next_batch`
|
||||
with an [opaque identifier](/appendices/#opaque-identifiers). The client can then supply
|
||||
the identifier as the `from` query parameter in a subsequent request, along with the original
|
||||
`user_id`, to fetch the next batch of responses. This will continue until the server no longer
|
||||
inserts `next_batch`, meaning there are no further results.
|
||||
|
|
|
|||
Loading…
Reference in a new issue