Improve support for ping / pong.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 382
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 9
Description
Being able to send pings w/ a custom payload can be useful at a higher level (for example gRPC).
There should be APIs for:
- Sending a PING w/ a custom payload
- Getting the payload for received pings.
Relates to #134
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's existing PING and PONG handling, then read the related discussion in issue #134. Identify the public API boundaries for sending custom PING payloads and exposing payloads from received pings; done means both capabilities are supported without breaking existing HTTP/2 behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100