Roadmap

路线图

这里只记方向。支持范围见 能力边界。

当前主路径（已落地）

• 内核客户端：HTTP/1.1、HTTP/2、HTTP/3（QUIC v1 + QPACK）、WebSocket（含 RFC 8441 可选路径）、SSE（WHATWG event-stream 客户端）。
• 传输 WSK + 密码学 CNG；TLS 1.2/1.3 自实现；信任锚调用方提供。
• H3 默认 Auto：从通过校验的 Alt-Svc 学习后，后续 HTTPS 可优先 QUIC。代理、明文 HTTP、WebSocket 与 NoVerify 等仍使用 TCP 路径。
• Session 拥有池、重定向（默认 10 跳）、安全方法 stale 重试一次、异步 4 线程队列。

刻意边界

• 客户端 only；无 server / 入站 parser。
• 无 WinHTTP / SChannel 主路径；无独立 client 层。
• 在线 OCSP/CRL 抓取、磁盘 HTTP cache、H2 本地 priority 调度、其它 WS 扩展，以及 QUIC v2 / 迁移 / 多路径 / WebTransport / WS-over-H3 等，当前不支持（见账本第 4 节）。
• 默认关的能力（pipeline、h2c、0-RTT、兼容 TLS、PING 保活等）见账本「默认关闭」一节；代码已有，只是默认不打开。

后续方向（摘要）

• 继续收紧超时、取消、帧/控制信令与恶意输入的有界防护；普通 buffered 响应默认不设过低的库级总量硬顶。
• 热路径减少重复分配（Workspace / lookaside / 连接常驻缓冲）。
• 代理路径：保持明文 absolute-form 与 HTTPS CONNECT 分离，审计 opaque 鉴权透传边界。
• H3/QUIC：互操作、性能与诊断增强；不以回退兼容层替代协议设计。

评估集成适用性时：先读 架构、会话与连接池、TLS 与信任，再以 能力边界 核对边界。

---

English

Roadmap

Direction only. Full capability classification is in the Capability Matrix.

Current main path (landed)

• Kernel client: HTTP/1.1, HTTP/2, HTTP/3 (QUIC v1 + QPACK), WebSocket (including optional RFC 8441), SSE (WHATWG event-stream client).
• Transport WSK + crypto CNG; self-implemented TLS 1.2/1.3; caller-supplied trust anchors.
• H3 default Auto: after learning validated Alt-Svc, later HTTPS may prefer QUIC. Proxies, cleartext HTTP, WebSocket, and NoVerify stay on TCP paths.
• Session owns the pool, redirects (default 10 hops), one stale retry for safe methods, and a 4-thread async queue.

Deliberate boundaries

• Client only; no server / inbound parser.
• No WinHTTP / SChannel main path; no separate client layer.
• Online OCSP/CRL fetch, on-disk HTTP cache, local H2 priority scheduling, other WS extensions, and QUIC v2 / migration / multipath / WebTransport / WS-over-H3 are not supported today (see matrix section 4).
• Default-off features (pipelining, h2c, 0-RTT, legacy TLS, PING keepalive, …) are listed under “Default-off” in the matrix; they exist in code and stay off until enabled.

Forward directions (summary)

• Keep tightening bounded defenses for timeouts, cancellation, frame/control signals, and malicious input; normal buffered responses stay without an overly low library-wide byte hard cap by default.
• Reduce repeated hot-path allocation (Workspace / lookaside / connection-resident buffers).
• Proxy paths: keep cleartext absolute-form separate from HTTPS CONNECT; audit opaque auth forwarding.
• H3/QUIC: interoperability, performance, and diagnostics. Avoid compatibility fallback layers that replace protocol design.

When assessing fit: read Architecture, Session & Pool, and TLS & Trust, then verify boundaries against the Capability Matrix.