mirror of
https://github.com/matrix-org/dendrite.git
synced 2025-12-12 09:23:09 -06:00
Fix typo and clarify what mode internal APIs use HTTP
This commit is contained in:
parent
bd995882eb
commit
2b858684ef
12
WIRING.md
12
WIRING.md
|
|
@ -208,7 +208,7 @@ and forth between each other. There are two implementations of each API, one
|
|||
that uses HTTP requests and one that does not. The HTTP implementation is
|
||||
used in multi-process mode, so processes on separate computers may still
|
||||
communicate, whereas in single-process or Monolith mode, the direct
|
||||
implementation is used. HTTP is preferred here to kaffka streams as it allows
|
||||
implementation is used. HTTP is preferred here to kafka streams as it allows
|
||||
for request responses.
|
||||
|
||||
Running `dendrite-monolith-server` will set up direct connections between
|
||||
|
|
@ -222,8 +222,8 @@ name>/<name>/<name>.go`.
|
|||
|
||||
As an example, the `appservices` component allows other Dendrite components
|
||||
to query external application services via its internal API. A component
|
||||
would call the desired function in `/appservices/api/query.go`. This would
|
||||
send an internal HTTP request, which would be handled by a function in
|
||||
`/appservices/query/query.go`. In single-process mode, no internal HTTP
|
||||
request occurs, instead functions are simply called directly, thus requiring
|
||||
no changes on the calling component's end.
|
||||
would call the desired function in `/appservices/api/query.go`. In
|
||||
multi-process mode, this would send an internal HTTP request, which would
|
||||
be handled by a function in `/appservices/query/query.go`. In single-process
|
||||
mode, no internal HTTP request occurs, instead functions are simply called
|
||||
directly, thus requiring no changes on the calling component's end.
|
||||
|
|
|
|||
Loading…
Reference in a new issue