SDK Overview
The SDK view is separate from protocol design on purpose.
- Protocol pages define the wire contract, packet shapes, descriptors, state machines, and version boundaries.
- SDK pages define the frozen control-plane surface that applications call in Python, C#, Rust, and JavaScript/TypeScript.
- Language-specific deployment and packaging guidance stays here instead of leaking back into protocol pages.
Frozen scope
The Preview4 entry points expose one shared control-plane and host-route contract across the four current language SDKs.
- Carrier-neutral application endpoints, per-carrier route sets, and deterministic selection.
- Atomic server listener sets and accepted-session active transport identity.
- Connection bootstrap and capability negotiation.
- Session open, patch, close, and migration.
- Operation submit, cancel, and receive loops.
- Flow-control updates and backpressure handling.
- Runtime objects, cache references, schema operations, and lifecycle guarantees.