Expand description
In-process OWP server and a WebSocket client for it.
start_owp binds an ephemeral port and serves
oa_gateway_owp::OwpAdapter with the UCI fixture schema
(oa_gateway_uci::slice::v25), not a compiled XSD. That is
enough for the messages in crate::fixtures. Helpers panic on
timeout or a surprising frame; they are not a public client API.
Functions§
- Opens a WebSocket to
urlwithSec-WebSocket-Protocol: owp. - As
connect, for awss://URL fromstart_owp_tls_with, trusting the peer’s certificate perclient_tls. - INIT 1.0 / schema
002.5.0/verbose, then expects+OKandINFO. - Next text frame, answering WebSocket pings.
- Sends one OWP text frame. Panics if the socket is closed.
- Starts an OWP adapter on an ephemeral port, wired to the fixture schema.
- As
start_owp_tls_with, but the listener also requires and verifies a client certificate issued byclient_ca. - As
start_owp_with, but the listener terminates TLS withcerts. - As
start_owp, with the config open for editing first. - As
start_owp_with, with the UCI schema open for editing too.
Type Aliases§
- Client WebSocket after the
owpsubprotocol handshake.