Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-04-20 18:04:10 +02:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Minor rewording/grammar

Browse source
This commit is contained in:
Paul "LeoNerd" Evans 2016-04-20 14:59:38 +01:00
parent 54624f397a
commit 8f22cf6cb8
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
supporting-docs/howtos/client-server-migrating-from-v1.rst
View file

@ -51,11 +51,11 @@ following summary may be useful to compare with ``v1``:
* In ``/events`` if more events occurred since the ``since`` token than the * In ``/events`` if more events occurred since the ``since`` token than the
``limit`` parameter allowed, then events from the start of this range were ``limit`` parameter allowed, then events from the start of this range were
returned and the client must perform another fetch to incrementally obtain returned and the client had to perform another fetch to incrementally obtain
more of them. In the ``/sync`` API the result always contains up to the most more of them. In the ``/sync`` API the result always contains the most
recent event; creating a gap if this would be more events than the requested recent events, creating a gap if this would be more events than the
limit. If this occurs then the client can use the ``prev_batch`` token as a requested limit. If this occurs then the client can use the ``prev_batch``
reference to obtaining more. token as a reference to obtaining more.
There is no direct replacement for the per-room ``/rooms/:roomId/initialSync`` There is no direct replacement for the per-room ``/rooms/:roomId/initialSync``
endpoint, but the behaviour can be recreated by applying an ad-hoc filter using endpoint, but the behaviour can be recreated by applying an ad-hoc filter using