67 comments (67 comments)84 reactions (84 reactions)0 assignees (0 assignees)Go21,741 stars (21,741 stars)1,755 forks (1,755 forks)batch import
enhancementhelp wanted
Description
Is this planned at all? And if I was interested in implementing it myself, where would I start?
Contributor guide
- Tech stack
- go
- Domain
- backendperformance
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 5
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- over 1 week
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- needs maintainer response
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- mostly clear
- Prerequisites
- Go programmingHTTP/2 protocol knowledgefasthttp API understanding
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 15
- Research direction
- 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.