# Glossary

## Content

| @cols=1:**Noun** | @cols=1:**Description** |
| ---- | ----------- |
| @cols=1:@rows=1:apply | @cols=1:@rows=1:**Applying** refers to the process of executing or implementing a change or operation to update the shared data, ensuring that the modifications are reflected across all participants. |
| @cols=1:@rows=1:auto connection | @cols=1:@rows=1:**Auto connection** refers to the automatic establishment or re-establishment of a connection between the client and server to ensure seamless real-time interaction, even after disruptions. |
| @cols=1:@rows=1:bidirectional communication | @cols=1:@rows=1:**Bidirectional communication** refers to the exchange of information where both parties can send and receive data, enabling real-time, two-way interaction. |
| @cols=1:@rows=1:broadcasting | @cols=1:@rows=1:**Broadcasting** is the process of sending a user's changes or actions to all other participants in real-time to ensure shared updates and consistency. |
| @cols=1:@rows=1:connection | @cols=1:@rows=1:**Connection** refers to the active link between clients and the server that enables real-time communication, data synchronization, and the sharing of updates. |
| @cols=1:@rows=1:crdt | @cols=1:@rows=1:**CRDT** (Conflict-free Replicated Data Type) is a data structure that allows for conflict-free, distributed updates to be made concurrently across multiple devices, ensuring eventual consistency without conflicts. |
| @cols=1:@rows=1:data consistency | @cols=1:@rows=1:In collaborative scenarios, **data consistency** ensures that all participants see the same, accurate, and up-to-date version of the shared data, despite concurrent edits or changes. |
| @cols=1:@rows=1:doc | @cols=1:@rows=1:In collaboration, a **doc** (Document) represents the shared data model or document that synchronizes real-time changes among users, ensuring consistency across all participants. |
| @cols=1:@rows=1:heartbeat | @cols=1:@rows=1:**Heartbeat** is a periodic signal sent between the client and server to indicate active connections and monitor the system's real-time health. |
| @cols=1:@rows=1:hook | @cols=1:@rows=1:**Hook** is a customizable function or callback that allows developers to execute specific actions or extend functionality during key events in the collaborative process. |
| @cols=1:@rows=1:message | @cols=1:@rows=1:**Message** refers to the data or information exchanged between participants, typically containing updates, actions, or commands to synchronize and coordinate changes in real time. |
| @cols=1:@rows=1:middleware | @cols=1:@rows=1:**Middleware** is a layer that manages data processing, synchronization, and communication between the client and server, ensuring smooth real-time interactions. |
| @cols=1:@rows=1:op | @cols=1:@rows=1:**Op** (Operation) describes the atomic operation on the model, such as edit or update, performed on shared data that needs to be synchronized across all participants. |
| @cols=1:@rows=1:ot | @cols=1:@rows=1:**OT** (Operational Transformation) is a technique used to resolve conflicts and synchronize concurrent changes made by multiple users, ensuring data consistency in real-time collaborative environments. |
| @cols=1:@rows=1:permission | @cols=1:@rows=1:**Permission** refers to the access control settings that define what actions or changes a user is allowed to perform on shared documents or resources. |
| @cols=1:@rows=1:postgre | @cols=1:@rows=1:**PostgreSQL** is an open-source, object-relational database management system known for its robustness, extensibility, and support for advanced SQL features like transactions, concurrency, and complex queries. |
| @cols=1:@rows=1:presence | @cols=1:@rows=1:**Presence** in collaboration refers to the real-time visibility of users' online status, actions, and editing locations in a shared environment. It helps identify who is active, where they are working, and their current activity, enhancing transparency and coordination. |
| @cols=1:@rows=1:room | @cols=1:@rows=1:In collaboration, a **room** is a virtual space that groups users together to enable real-time data sharing, synchronization, and interaction within a specific context or task. |
| @cols=1:@rows=1:snapshot | @cols=1:@rows=1:**Snapshot** refers to a saved state of the shared data at a specific point in time, which can be used to restore or compare changes made during the collaborative process. |
| @cols=1:@rows=1:sqlite | @cols=1:@rows=1:**SQLite** is a lightweight, self-contained, serverless database engine designed for embedded systems, providing reliable, zero-configuration storage using a single file. |
| @cols=1:@rows=1:transform | @cols=1:@rows=1:**Transform** refers to the process of modifying or adapting an operation or change to maintain consistency when multiple users concurrently edit shared data. |
| @cols=1:@rows=1:transmission | @cols=1:@rows=1:**Transmission** refers to the process of sending data, updates, or messages between clients and servers to ensure real-time synchronization and communication. |