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/SECURE_ACCESS_FABRIC_TARGET.md
+24 -8
View File
@@ -8,6 +8,12 @@ The current proven RDP lifecycle remains a preserved implementation baseline.
RDP work is currently paused by product decision. The active architecture focus
is the lower Fabric Core / cluster / node foundation.
Transport clarification: historical references in this document to direct
worker WSS or backend gateway fallback describe the earlier RDP service proof
path and migration context. They must not be read as the current inter-node
transport contract. The active fabric node-to-node runtime transport is
QUIC-only.
## 1. Project Vision
The project is a Secure Access Fabric: a distributed, multi-tenant platform for secure access to private resources across sites, networks, and organizations.
@@ -1702,7 +1708,7 @@ Channels must have independent priority, reliability, and backpressure behavior.
The current RDP MVP proves lifecycle and basic viewer behavior. It is not the target production performance model.
Target RDP realtime model:
Target RDP realtime model for the paused historical RDP service track:
- client connects to direct/relay data plane, not backend frame relay
- input/control channels are separate from render/video
@@ -2459,7 +2465,11 @@ This is an incremental migration plan. It must not be executed as a big-bang rew
### Current Fallback
Keep the current backend WebSocket gateway as fallback while the production data plane is introduced.
Historical migration note: the older RDP MVP kept the backend WebSocket
gateway as a temporary fallback while an earlier production data-plane design
was being introduced. This is not the active fabric transport plan. Current
fabric node-to-node runtime transport is QUIC-only, and old compatibility paths
are being removed rather than extended.
Current RDP MVP remains the preserved service-adapter baseline, but it is not
the active implementation focus while Fabric Core stages are underway.
@@ -2543,9 +2553,14 @@ These stages must be introduced only through explicit, narrow implementation
prompts. RDP/VNC/SSH/VPN/video/file services remain above the Fabric Core and
must not define the lower fabric foundation.
### Stage DP-1: Direct Worker WSS
### Historical Stage DP-1: Direct Worker WSS
Introduce a short-lived authorized direct WSS path from client to worker or worker-local live endpoint.
This stage records an earlier RDP service migration concept. It is paused and
retained for historical context only. It must not be read as the active fabric
transport roadmap.
Introduce a short-lived authorized direct WSS path from client to worker or
worker-local live endpoint.
Goals:
@@ -2554,7 +2569,7 @@ Goals:
- keep session broker lifecycle unchanged
- keep fallback gateway available
### Stage DP-2: Binary Frames
### Historical Stage DP-2: Binary Frames
Replace base64 JSON frame payloads with binary frame messages.
@@ -2565,7 +2580,7 @@ Goals:
- reduce JSON/base64 overhead
- preserve latest-frame-only behavior
### Stage DP-3: Adaptive Quality
### Historical Stage DP-3: Adaptive Quality
Implement adaptive RDP quality profiles.
@@ -2577,9 +2592,10 @@ Goals:
- bandwidth and latency feedback
- bounded frame queues
### Stage DP-4: Relay Nodes
### Historical Stage DP-4: Relay Nodes
Introduce `entry-node` and `relay-node` roles for data-plane routing.
Introduce `entry-node` and `relay-node` roles for the earlier service-specific
data-plane routing model.
Goals: