Expand description
onlyne-wire — the wire seam: length-prefixed JSON frames, and the local
socket one daemon binds and every other process reaches.
frame moves opaque serialisable values and holds no protocol semantics,
so onlyne-proto stays free of tokio. socket owns the owner-tree
endpoint: the machine-level runtime directory (/tmp/onlyne-<uid>/), the
<digest>.sock a daemon binds there, the <digest>.json registration that
names the surface serving it, and the owner-only modes around both.
The frame API is re-exported at the crate root, because a caller that wants
frames wants nothing else from this crate; the socket API stays behind its
module, since SocketEndpoint and bind_socket read better named.
Re-exports§
pub use frame::FrameReader;pub use frame::MAX_FRAME_BYTES;pub use frame::MAX_PARTIAL_FRAME_BYTES;pub use frame::TooLarge;pub use frame::UnexpectedEof;pub use frame::is_bad_frame;pub use frame::is_too_large;pub use frame::read_frame;pub use frame::write_frame;