Replace s2s join sequence diagram for legibility (#3603)
Without the vertical lines it's a bit difficult to parse. A different tool was used to generate the graph this time.
This commit is contained in:
parent
48d8f7202d
commit
afc5298f11
1 changed files with 42 additions and 15 deletions
|
@ -678,22 +678,49 @@ candidate may be used at each time. Thus, any join handshake can
|
||||||
potentially involve anywhere from two to four homeservers, though most
|
potentially involve anywhere from two to four homeservers, though most
|
||||||
in practice will use just two.
|
in practice will use just two.
|
||||||
|
|
||||||
```
|
<!--
|
||||||
Client Joining Directory Resident
|
https://textart.io/sequence
|
||||||
Server Server Server
|
|
||||||
|
|
||||||
join request -->
|
object Client JoiningServer DirectoryServer ResidentServer
|
||||||
|
|
Client->JoiningServer: join request
|
||||||
directory request ------->
|
JoiningServer->DirectoryServer: directory request
|
||||||
<---------- directory response
|
DirectoryServer->JoiningServer: directory response
|
||||||
|
|
JoiningServer->ResidentServer: make_join request
|
||||||
make_join request ----------------------->
|
ResidentServer->JoiningServer: make_join response
|
||||||
<------------------------------- make_join response
|
JoiningServer->ResidentServer: send_join request
|
||||||
|
|
ResidentServer->JoiningServer: send_join response
|
||||||
send_join request ----------------------->
|
JoiningServer->Client: join response
|
||||||
<------------------------------- send_join response
|
-->
|
||||||
|
|
|
||||||
<---------- join response
|
```
|
||||||
|
+---------+ +---------------+ +-----------------+ +-----------------+
|
||||||
|
| Client | | JoiningServer | | DirectoryServer | | ResidentServer |
|
||||||
|
+---------+ +---------------+ +-----------------+ +-----------------+
|
||||||
|
| | | |
|
||||||
|
| join request | | |
|
||||||
|
|---------------------->| | |
|
||||||
|
| | | |
|
||||||
|
| | directory request | |
|
||||||
|
| |---------------------------->| |
|
||||||
|
| | | |
|
||||||
|
| | directory response | |
|
||||||
|
| |<----------------------------| |
|
||||||
|
| | | |
|
||||||
|
| | make_join request | |
|
||||||
|
| |------------------------------------------------>|
|
||||||
|
| | | |
|
||||||
|
| | |make_join response |
|
||||||
|
| |<------------------------------------------------|
|
||||||
|
| | | |
|
||||||
|
| | send_join request | |
|
||||||
|
| |------------------------------------------------>|
|
||||||
|
| | | |
|
||||||
|
| | |send_join response |
|
||||||
|
| |<------------------------------------------------|
|
||||||
|
| | | |
|
||||||
|
| join response | | |
|
||||||
|
|<----------------------| | |
|
||||||
|
| | | |
|
||||||
```
|
```
|
||||||
|
|
||||||
The first part of the handshake usually involves using the directory
|
The first part of the handshake usually involves using the directory
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue