public interface IAsyncBridgeTransport : IBridgeTransport A host that can acknowledge state delivery before the next dependent frame is sent.
Remarks
Desktop implements this because its IBridgeTransport.Publish coalesces snapshots per route, and awaiting script completion lets a slow WebView fall behind into a bounded recovery snapshot. CS-WebUI does not implement it: WebUI's only acknowledged script call answers from one client and blocks a native thread. Its IBridgeTransport.Publish instead writes to every client synchronously, under WebUI's process-wide send lock, and blocks until each socket write completes or times out. A slow client therefore applies TCP-level back-pressure: the blocked write holds the bridge's delivery queue, which falls back to a recovery snapshot once it is full, and it also delays sends to every other CS-WebUI window. This is not application-level acknowledgement; frames are written in order, not confirmed as applied.
Methods
PublishAsync
ValueTask PublishAsync(string name, string stateJson) Delivers one frame without coalescing it with other frames.
Remarks
Generated bridges await this outside the model context. Slow delivery is bounded by the bridge's recovery-snapshot queue.