Update diagram

travis/msc/ietf-mimi-transport
Travis Ralston 2 years ago
parent e2127c8aa5
commit 6ecbb9b112

@ -198,10 +198,10 @@ Table of Contents
Practically, this looks like:
Room on server A sent message A1, The same room on server B has received
then sent A2, and received C1 from A1 and A2, but not C1, e.g. due to
server C which raced with A2 and so network connectivity problems.
follows A1.
Room on server A sent message A1, The same room on server B has
then sent A2, and received C1 from received A1 and A2, but not C1,
server C which raced with A2 and so e.g. due to network connectivity
follows A1. problems.
__________ __________
' ' ' '
' A1 ' ' A1 '
@ -209,7 +209,7 @@ follows A1.
' A2 C1 ' ' A2 '
'__________' '__________'
Server A sends another message, A3:
Server A sends another message, A3:
__________ __________
' ' ' '
@ -220,7 +220,7 @@ Server A sends another message, A3:
' A3 ' /_matrix/federation/v1/send/{txnId} ' A3 '
'__________' A3 '__________'
Server B sees that A3 refers to the missing event C1, and pulls it from A:
Server B sees that A3 refers to missing event C1, and pulls it from A:
__________ __________
' ' ' '
@ -231,8 +231,8 @@ Server B sees that A3 refers to the missing event C1, and pulls it from A:
' A3 ' /_matrix/federation/v1/get_missing_events ' A3 '
'__________' C1 '__________'
Typically, get_missing_events isn't needed, given servers push all events
to all participating servers by default.
Typically, get_missing_events isn't needed, given servers push all
events to all participating servers by default.
Figure 1

Loading…
Cancel
Save