the-binding-of-dsh

In the DSH ecosystem, bidirectional communication between Host and Client often depends on ad-hoc bridges or parallel transports, leaving request correlation, cancellation, and connection lifecycle without unified governance. The Binding of DSH solves this directly: it introduces no parallel carrier, instead routing targeted Host-to-Client calls and symmetric Client-to-Host calls over the same native WebSocket channel, keeping two-way RPC lightweight and controllable.

The architecture maintains a clean separation of concerns. Connection continues to own peer addressing and lifecycle management; Typert Gateway continues to own service descriptors, codecs, invocation dispatch, and error propagation. All RPC requests, results, and cancellation signals travel over the events.host WebSocket, while native mux events and bulk HTTP APIs retain their original transport paths, so the two responsibilities never interfere.

This plugin is well suited for developers building DSH browser extensions that need structured, correlation-tagged two-way calls between the Host and a connected Node or browser peer. No extra message queue or WebSocket intermediary is required. On Harmony 0.8.6 or newer, the browser module dependency introduced by the Connection patch is derived automatically and the Binding module is ordered without manual configuration.