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

More clarity

Browse source
This commit is contained in:
Travis Ralston 2019-06-07 09:01:14 -06:00
parent a0e8201816
commit e4339fd687
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
specification/client_server_api.rst
View file

@ -1276,12 +1276,12 @@ effort to reduce the number of resources used, clients can enable "lazy-loading"
for room members. By doing this, servers will only ever send membership events
which are relevant to the client.
In terms of filters, this means enabling ``lazy_load_members`` on a ``StateFilter``
or ``RoomEventFilter``. When enabled, lazy-loading aware endpoints (see below)
will only include membership events for the ``sender`` of events being included
in the response. For example, if a client makes a ``/sync`` request with lazy-loading
enabled, the server will only return membership events for the ``sender`` of events
in the timeline, not all members of a room.
In terms of filters, this means enabling ``lazy_load_members`` on a ``RoomEventFilter``
(or a ``StateFilter`` in the case of ``/sync`` only). When enabled, lazy-loading
aware endpoints (see below) will only include membership events for the ``sender``
of events being included in the response. For example, if a client makes a ``/sync``
request with lazy-loading enabled, the server will only return membership events
for the ``sender`` of events in the timeline, not all members of a room.
Repeated calls to lazy-loading aware endpoints will result in redundant membership
events being excluded by default. Clients often track which membership events they