mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2024-09-11 05:25:32 +03:00
Documentation: Change references to uid based sockets to sids
This commit is contained in:
parent
7af5eef0dd
commit
37f527be9c
Notes:
sideshowbarker
2024-07-17 06:24:17 +09:00
Author: https://github.com/petelliott Commit: https://github.com/SerenityOS/serenity/commit/37f527be9c Pull-request: https://github.com/SerenityOS/serenity/pull/15142 Reviewed-by: https://github.com/ADKaster Reviewed-by: https://github.com/bgianfo
@ -1,6 +1,6 @@
|
||||
## Name
|
||||
|
||||
Overview of the SerenityOS audio subsystem, including a brief description of [`/dev/audio`](help://man/4/audio), the AudioServer and their interfaces.
|
||||
Overview of the SerenityOS audio subsystem, including a brief description of [`/dev/audio`](help://man/4/audio), the AudioServer and their interfaces.
|
||||
|
||||
## Description
|
||||
|
||||
@ -18,9 +18,8 @@ AudioServer is responsible for handling userland audio clients and talking to th
|
||||
application should ever need to write to a device in `/dev/audio` directly, except for special cases in which
|
||||
AudioServer is not present.
|
||||
|
||||
As with all system servers, AudioServer provides an IPC interface on `/tmp/user/%uid/portal/audio`, with `%uid` being
|
||||
the uid
|
||||
of the current user. For specifics on how to talk to AudioServer, the IPC interface specifications are the best source
|
||||
As with all system servers, AudioServer provides an IPC interface on `/tmp/session/%sid/portal/audio`, with `%sid` being
|
||||
the current login session id. For specifics on how to talk to AudioServer, the IPC interface specifications are the best source
|
||||
of information. For controlling mixer functionality, clients have the ability to obtain and change their own volume, or
|
||||
the main volume and mute state.
|
||||
|
||||
|
@ -31,7 +31,7 @@ This process can decode images (PNG, JPEG, BMP, ICO, PBM, etc.) into bitmaps. Ea
|
||||
### How processes are spawned
|
||||
|
||||
To get a fresh **WebContent** process, anyone with the suitable file system permissions can spawn one by connecting to
|
||||
the socket at `/tmp/user/%uid/portal/webcontent`, with `%uid` being the uid of the current user. This socket is managed
|
||||
the socket at `/tmp/user/%sid/portal/webcontent`, with `%sid` being the current login session id. This socket is managed
|
||||
by **
|
||||
SystemServer** and will spawn a new instance of **WebContent** for every connection.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user