Struct WebRtcGate 

pub struct WebRtcGate { /* private fields */ }

WebRTC Gate - OutboundGate implementation

Responsibilities

• Implement OutboundGate trait
• Send messages using WebRtcCoordinator
• Serialize/deserialize RpcEnvelope (Protobuf)
• Track pending requests and match responses (by r equest_id)
• Route messages by PayloadType (RPC → Mailbox, DataStream → Registry)

Design Principles

• Response reuses Request’s request_id (standard RPC semantics)
• Use pending_requests to distinguish: exists = Response, doesn’t exist = Request
• Gateway layer doesn’t deserialize payloads, raw bytes go directly to Mailbox
• IMPORTANT: pending_requests should be shared with OutprocOutGate

Implementations

impl WebRtcGate

pub fn new( coordinator: Arc<WebRtcCoordinator>, pending_requests: Arc<RwLock<HashMap<String, (ActrId, Sender<ActorResult<Bytes>>)>>>, data_stream_registry: Arc<DataStreamRegistry>, ) -> Self

Create new WebRtcGate with shared pending_requests and DataStreamRegistry

Arguments

• coordinator: WebRtcCoordinator instance
• pending_requests: Shared pending requests (should be same as OutprocOutGate)
• data_stream_registry: DataStream registry for fast-path routing

pub async fn set_local_id(&self, actor_id: ActrId)

Set local Actor ID

pub async fn start_receive_loop( &self, mailbox: Arc<dyn Mailbox>, ) -> RuntimeResult<()>

Start message receive loop (called by ActrSystem/ActrNode)

Arguments

• mailbox: message queue for persisting inbound requests

Architecture

According to three-loop architecture design (framework-runtime-architecture.zh.md):

• WebRtcGate belongs to outer loop (Transport layer)
• Mailbox belongs to inner loop (state path)
• Message flow: WebRTC → WebRtcGate → Mailbox/DataStreamRegistry → Scheduler → ActrNode

Message Routing Logic

• Route based on PayloadType:
  • RpcReliable/RpcSignal: Deserialize RpcEnvelope, check pending_requests, enqueue to Mailbox
  • StreamReliable/StreamLatencyFirst: Deserialize DataStream, dispatch to DataStreamRegistry

pub async fn send_response( &self, target: &ActrId, response_envelope: RpcEnvelope, ) -> RuntimeResult<()>

Send response (called by Mailbox handler loop)

Arguments

• target: response target ActrId (original request sender)
• response_envelope: response RpcEnvelope (must reuse original request_id)

Design Principle

• Response reuses Request’s request_id (caller is responsible)
• Receiver matches to pending_requests by request_id and wakes up waiting caller