doc: Some clarifications in Overview

Correct `context.spa-libs` as being pointing to the right SPA libs
(rather than loading them), and some other minor fixups.
This commit is contained in:
Arun Raghavan 2024-04-25 17:26:22 -04:00
parent 1b6a94db36
commit be97d1f766

View file

@ -54,10 +54,10 @@ it using the PipeWire native protocol.
## Clients ## Clients
PipeWire look quite similar to the PipeWire server: they also load a number of PipeWire clients look quite similar to the PipeWire server: they also load a
the entities below, but they do not act as a server of the native protocol. number of the entities below, but they do not act as a server of the native
Instead, they "export" some their entities to the server, which in turn is able protocol. Instead, they "export" some their entities to the server, which in
to use them like it would its own local entities. turn is able to use them like it would its own local entities.
## Context ## Context
@ -70,9 +70,10 @@ and clients. The server and clients follow a similar structure, where they:
- Load a bunch of support libraries - Load a bunch of support libraries
- Using configuration, to - Using configuration, to
- Set some global properties (`context.properties`) - Set some global properties (`context.properties`)
- Load SPA libraries (PipeWire-s low-level plugin API) (`context.spa-libs`) - Identify what SPA libraries to load (PipeWire-s low-level plugin API)
(`context.spa-libs`)
- Load PipeWire modules (`context.modules`) - Load PipeWire modules (`context.modules`)
- Creates objects (`context.objects`) - Create objects (`context.objects`)
- Execs misc commands (`context.exec`) - Execs misc commands (`context.exec`)
- If necessary, start a real time loop for data processing - If necessary, start a real time loop for data processing