m/rdp-proxy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

3

Browse Source
This commit is contained in:
Mikhail
2026-05-18 21:33:39 +03:00
parent 5096155d83
commit 469fa0e860
94 changed files with 8761 additions and 8003 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture/SERVICE_ADAPTER_PROTOCOL.md
+20 -2
View File
@@ -1,7 +1,21 @@
# Service Adapter Protocol
Scope note: this document remains the common adapter-model reference, but it is
not the current source of truth for transport/runtime topology between fabric
nodes. Fabric transport is now QUIC-only between nodes; for active transport,
routing, and recovery behavior see
`docs/architecture/DISTRIBUTED_FABRIC_NODE_PROTOCOL_PLAN.md`,
`docs/architecture/FABRIC_FIRST_TRANSPORT_AND_STRESS_PLAN.md`, and
`docs/architecture/SECURE_ACCESS_FABRIC_TARGET.md`.
Status: target contract and compile-safe foundation. This document defines the common adapter model for RDP, SSH, VNC, and future services. It does not replace the current backend control plane or current RDP runtime by itself.
Transport clarification: historical references in this document to direct
worker WSS, backend gateway fallback, or DP-1 channel shape belong to the
earlier RDP service baseline. They are not the active inter-node transport
contract. Current fabric node-to-node transport is QUIC-only; service adapters
consume fabric routes rather than define transport fallback behavior.
## 1. Purpose
The platform client must not implement third-party protocols directly.
@@ -94,12 +108,16 @@ adapter runtime.
- Service Adapter does not know UI implementation details.
- Control Plane remains authoritative for session lifecycle and policy.
- PostgreSQL remains source of truth; Redis remains live coordination only.
- Direct worker WSS and backend gateway fallback remain valid transports.
- Fabric transport remains QUIC-only between nodes; any historical direct
worker or backend fallback paths belong to paused service-specific baselines,
not to the active fabric transport contract.
- Adapter runtime must not create sessions outside broker/assignment control.
## 4. Logical Channels
The session protocol is channel-oriented even when DP-1 uses one WSS connection.
The session protocol is channel-oriented regardless of the concrete carrier. A
historical DP-1 single-WSS shape may still appear in paused RDP notes, but it
is not the current fabric transport contract.
| Channel | Direction | Reliability | Priority | Purpose |
| --- | --- | --- | --- | --- |