From be2eae9d228193320cd8a4fa696505c6efb6772c Mon Sep 17 00:00:00 2001 From: squahtx Date: Tue, 7 Dec 2021 16:19:22 +0000 Subject: deploy: 26b5d2320f62b5eb6262c7614fbdfc364a4dfc02 --- latest/development/room-dag-concepts.html | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) (limited to 'latest/development/room-dag-concepts.html') diff --git a/latest/development/room-dag-concepts.html b/latest/development/room-dag-concepts.html index 44f8fcd4ae..724ea1ea93 100644 --- a/latest/development/room-dag-concepts.html +++ b/latest/development/room-dag-concepts.html @@ -99,7 +99,7 @@ @@ -208,19 +208,18 @@ representation of the state of the room as others were seeing it at the time.

Forward extremity

Most-recent-in-time events in the DAG which are not referenced by any other events' prev_events yet.

The forward extremities of a room are used as the prev_events when the next event is sent.

-

Backwards extremity

+

Backward extremity

The current marker of where we have backfilled up to and will generally be the -oldest-in-time events we know of in the DAG.

-

This is an event where we haven't fetched all of the prev_events for.

-

Once we have fetched all of its prev_events, it's unmarked as a backwards -extremity (although we may have formed new backwards extremities from the prev -events during the backfilling process).

+prev_events of the oldest-in-time events we have in the DAG. This gives a starting point when +backfilling history.

+

When we persist a non-outlier event, we clear it as a backward extremity and set +all of its prev_events as the new backward extremities if they aren't already +persisted in the events table.

Outliers

We mark an event as an outlier when we haven't figured out the state for the room at that point in the DAG yet.

We won't necessarily have the prev_events of an outlier in the database, -but it's entirely possible that we might. The status of whether we have all of -the prev_events is marked as a backwards extremity.

+but it's entirely possible that we might.

For example, when we fetch the event auth chain or state for a given event, we mark all of those claimed auth events as outliers because we haven't done the state calculation ourself.

-- cgit 1.4.1