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

deploy: 42f9d414c2

Browse source
This commit is contained in:
reivilibre 2022-11-07 13:52:31 +00:00
parent cc0c84570c
commit 20e8cfa2dd
4 changed files with 10 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
develop/print.html
View file

@ -10262,9 +10262,10 @@ have different characteristics and so admins
may wish to run multiple groups of workers handling different endpoints so that may wish to run multiple groups of workers handling different endpoints so that
load balancing can be done in different ways.</p> load balancing can be done in different ways.</p>
<p>For <code>/sync</code> and <code>/initialSync</code> requests it will be more efficient if all <p>For <code>/sync</code> and <code>/initialSync</code> requests it will be more efficient if all
requests from a particular user are routed to a single instance. Extracting a requests from a particular user are routed to a single instance. This can
user ID from the access token or <code>Authorization</code> header is currently left as an be done e.g. in nginx via IP <code>hash $http_x_forwarded_for;</code> or via
exercise for the reader. Admins may additionally wish to separate out <code>/sync</code> <code>hash $http_authorization consistent;</code> which contains the users access token.</p>
<p>Admins may additionally wish to separate out <code>/sync</code>
requests that have a <code>since</code> query parameter from those that don't (and requests that have a <code>since</code> query parameter from those that don't (and
<code>/initialSync</code>), as requests that don't are known as &quot;initial sync&quot; that happens <code>/initialSync</code>), as requests that don't are known as &quot;initial sync&quot; that happens
when a user logs in on a new device and can be <em>very</em> resource intensive, so when a user logs in on a new device and can be <em>very</em> resource intensive, so

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

7
develop/workers.html
View file

@ -419,9 +419,10 @@ have different characteristics and so admins
may wish to run multiple groups of workers handling different endpoints so that may wish to run multiple groups of workers handling different endpoints so that
load balancing can be done in different ways.</p> load balancing can be done in different ways.</p>
<p>For <code>/sync</code> and <code>/initialSync</code> requests it will be more efficient if all <p>For <code>/sync</code> and <code>/initialSync</code> requests it will be more efficient if all
requests from a particular user are routed to a single instance. Extracting a requests from a particular user are routed to a single instance. This can
user ID from the access token or <code>Authorization</code> header is currently left as an be done e.g. in nginx via IP <code>hash $http_x_forwarded_for;</code> or via
exercise for the reader. Admins may additionally wish to separate out <code>/sync</code> <code>hash $http_authorization consistent;</code> which contains the users access token.</p>
<p>Admins may additionally wish to separate out <code>/sync</code>
requests that have a <code>since</code> query parameter from those that don't (and requests that have a <code>since</code> query parameter from those that don't (and
<code>/initialSync</code>), as requests that don't are known as &quot;initial sync&quot; that happens <code>/initialSync</code>), as requests that don't are known as &quot;initial sync&quot; that happens
when a user logs in on a new device and can be <em>very</em> resource intensive, so when a user logs in on a new device and can be <em>very</em> resource intensive, so