Is this planned at all? And if I was interested in implementing it myself, where would I start?
貢獻者指南
技術棧
go
領域
backendperformance
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
needs maintainer response
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Go programmingHTTP/2 protocol knowledgefasthttp API understanding
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
Review the 67 comments on this issue for prior discussion and potential implementation approaches. Examine the fasthttp codebase, focusing on the existing HTTP/1.x handling in files like server.go and client.go. Investigate how other Go HTTP libraries (e.g., net/http) implement HTTP/2 support, particularly the use of golang.org/x/net/http2. Propose a design that integrates HTTP/2 without compromising fasthttp's zero alloc high performance model. Since the issue is open and the maintainer has not committed to the feature, first clarify whether the maintainer would accept a PR and what design constraints exist.
