Matrix/synapse
Matrix/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse synced 2024-09-30 05:52:43 +00:00
Code Issues Projects Releases Packages Wiki Activity

deploy: 11db575218

Browse source
This commit is contained in:
MadLittleMods 2024-08-07 16:29:24 +00:00
parent 94ffa05d45
commit 60d2dc75f9
4 changed files with 10 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
develop/development/room-dag-concepts.html
View file

@ -174,8 +174,10 @@ messages are added to the DAG. Normally, <code>stream_ordering</code> is an auto
incrementing integer, but backfilled events start with <code>stream_ordering=-1</code> and decrement.</p> incrementing integer, but backfilled events start with <code>stream_ordering=-1</code> and decrement.</p>
<hr /> <hr />
<ul> <ul>
<li><code>/sync</code> returns things in the order they arrive at the server (<code>stream_ordering</code>).</li> <li>Incremental <code>/sync?since=xxx</code> returns things in the order they arrive at the server
<li><code>/messages</code> (and <code>/backfill</code> in the federation API) return them in the order determined by the event graph <code>(topological_ordering, stream_ordering)</code>.</li> (<code>stream_ordering</code>).</li>
<li>Initial <code>/sync</code>, <code>/messages</code> (and <code>/backfill</code> in the federation API) return them in
the order determined by the event graph <code>(topological_ordering, stream_ordering)</code>.</li>
</ul> </ul>
<p>The general idea is that, if you're following a room in real-time (i.e. <p>The general idea is that, if you're following a room in real-time (i.e.
<code>/sync</code>), you probably want to see the messages as they arrive at your server, <code>/sync</code>), you probably want to see the messages as they arrive at your server,

6
develop/print.html
View file

@ -19561,8 +19561,10 @@ messages are added to the DAG. Normally, <code>stream_ordering</code> is an auto
incrementing integer, but backfilled events start with <code>stream_ordering=-1</code> and decrement.</p> incrementing integer, but backfilled events start with <code>stream_ordering=-1</code> and decrement.</p>
<hr /> <hr />
<ul> <ul>
<li><code>/sync</code> returns things in the order they arrive at the server (<code>stream_ordering</code>).</li> <li>Incremental <code>/sync?since=xxx</code> returns things in the order they arrive at the server
<li><code>/messages</code> (and <code>/backfill</code> in the federation API) return them in the order determined by the event graph <code>(topological_ordering, stream_ordering)</code>.</li> (<code>stream_ordering</code>).</li>
<li>Initial <code>/sync</code>, <code>/messages</code> (and <code>/backfill</code> in the federation API) return them in
the order determined by the event graph <code>(topological_ordering, stream_ordering)</code>.</li>
</ul> </ul>
<p>The general idea is that, if you're following a room in real-time (i.e. <p>The general idea is that, if you're following a room in real-time (i.e.
<code>/sync</code>), you probably want to see the messages as they arrive at your server, <code>/sync</code>), you probably want to see the messages as they arrive at your server,

2
develop/searchindex.js
View file

File diff suppressed because one or more lines are too long

2
develop/searchindex.json
View file

File diff suppressed because one or more lines are too long