Drive SDK maintenance while receiving
ci / test (push) Canceled after 0s
ci / fuzz-smoke (push) Canceled after 0s
ci / windows-client (push) Canceled after 0s
ci / package-release (linux-x86_64, ubuntu-latest) (push) Canceled after 0s
ci / package-release (macos-aarch64, macos-14) (push) Canceled after 0s
ci / package-release (macos-x86_64, macos-13) (push) Canceled after 0s
ci / package-release (windows-x86_64, windows-latest) (push) Canceled after 0s
ci / remote-bench (push) Canceled after 0s
ci / publish-gitea-release (push) Canceled after 0s

This commit is contained in:
DuProcess
2026-07-13 00:58:54 -04:00
parent 8b33a5d20b
commit 0125966d2a
3 changed files with 250 additions and 74 deletions
+3 -1
View File
@@ -5,7 +5,9 @@
//! handle native authentication, host key checks, roaming, keepalives, reliable
//! streams, and service routing. Use [`transport::DoshTransport`] only when an
//! application already owns session establishment and wants direct access to the
//! encrypted stream transport.
//! encrypted stream transport. The SDK receive loops drive retransmission and
//! keepalives while waiting, so simple applications can call `recv().await`
//! without building their own maintenance loop.
pub mod auth;
pub mod build_info;