A server process runs in the background and run sessions, commands, and manages connections. There is normally one server process for a given user and host (computer), though you can override that if you use the --socket-name option. The server listens for requests on the command socket.

A session is that actuall application that the user care about. Typically, it is a shell process running under a pty.

A window is a top-level window or a sub-window (tile or tab) managed by DomTerm. A session window is one that interacts with a session. A non-session window is created by a domterm commands that do not create or connect to seesions, such as domterm browse or domterm view-saved.

A browser engine is the core part of a web browser that loads and displays web pages, and process JavaScript. A full web browser adds menus, location bar, history, and bookmarks. Numerous frameworks exist that can use to write an application and use the browser engine for the user interface: Electron, Qt, JavaFX, and others. DomTerm can make use of multiple browser engine frameworks, as well as full web browsers.

A connection communicates between a window and the server process, and thence usualy to a specific session. Most commonly a connection uses the WebSockets protocol.

A setting is a pair of a setting name and setting value that controls how DomTerm behaves. The global settings are defined in a configuration file normally named settings.ini. The local settings can be specified on the domterm command line, and apply to the current command, current session, or current window. The local settings take priority over the global setings.