If you open Task Manager or profile memory while io.Connect Desktop is running, you will see a number of separate OS processes rather than a single one.
Because io.Connect Desktop is built on Electron and Chromium, Task Manager shows the main platform process together with renderer/helper processes and Chromium infrastructure services (graphics, networking, audio). This is the same model any Chromium-based application uses, including Google Chrome. The exact number and type of processes depend on the io.Connect Desktop version, the enabled platform features, the apps you are running, and your deployment configuration.
Platform processes and components you may see
The table below describes the roles of processes and components that belong to the platform.
| Process | What it does |
|---|---|
| Main | This is the main process where the code is executed. It is basically an Electron application; everything else is a helper process to this one. |
| glue42-gateway | The Glue Gateway is a transport with domain-specific protocols. It enables communication between apps running in Glue Desktop. By default, it uses WebSockets for delivering messages to apps. Other options are also available upon request. The Glue Gateway is written in Clojure and can be transpiled to Java and JavaScript. |
| workspaces | This is the application enabling workspaces and workspace layouts. A Workspace is a container for one or more apps (windows) arranged in columns, rows or groups of tabbed windows. Each app acts as a building block of a Workspace and can be resized, maximized and restored within a Workspace. Apps can be added to a Workspace (by drag and drop or programmatically) and can also be ejected from a Workspace as floating windows. The arrangement of each Workspace can be uniquely suited to provide the necessary layout and functionalities for performing tasks quickly and intuitively. Instead of wasting time and effort in finding, opening and arranging the relevant apps, restore the respective Workspace with a single click. |
| bbg42mdfbridge | This is the BBG Market Data Bridge. It uses the Glue BBG Market Data API to provide access to the Bloomberg Market Data service. Real-time and delayed streaming market data and static reference data for securities and security fields can be retrieved via subscription or request/response mechanisms. |
| Applications | Memory profiling application |
| glue42-web-group-application | This is an instance of a Web group container The glue web groups are based on web technologies and allow for complete customization of the containing group frame and all elements of the different glue Window types (flat, tab and HTML) that may be a part of it. |
| Restore Layout | This is the splash that appears while restoring a layout. |
| glue42-notifications-application | This is a notification application that provides a notification service that normalizes and consolidates notifications from different apps and delivers them directly to the user on the desktop in a customizable UI as both toasts and ordered lists in a Notification Panel. |
| glue42-channel-selector | This is as the glue channel selector The glue Channels are globally accessed named contexts that allow users to dynamically group apps via the UI, instructing them to work over the same shared data object. |
| BBGBridgeV3 | This is the V3 of the Bloomberg Bridge. It is an adapter that brings various Bloomberg services to your interop-enabled apps. |
| GssDesktopManager | This is the implementation behind the Glue Desktop Global search service |
| GPU | This is the Electron GPU service. It is a component that manages graphics processing tasks for apps built using the Electron framework. It is responsible for handling GPU-accelerated rendering and other graphics-related functions |
| WebGroup Placeholder Layer | A window we are using as decoration for our Web groups |
| Network Service | This is the Electron Network Service. It is a component responsible for managing network-related tasks in applications built with the Electron framework. It is commonly used for creating cross-platform desktop apps using web technologies. |
| Audio Service | This is the Electron audio service. It is a component that handles audio-related operations in apps built with the Electron framework. This service is responsible for managing and processing audio to ensure that it is handled efficiently and separately from the main processes |
The GPU, Network Service and Audio Service processes are Chromium infrastructure. These specific services (GPU, networking and audio) also exist when you run Google Chrome, under different names.
Not every process is baseline platform overhead
The process list you see may also include:
- your organization’s own apps;
- optional adapters (for example, market-data or messaging connectors);
- custom platform services you have added;