Additional feature request for "push-update-broad"
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.6k
- Forks
- 3.4k
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
First, many thanks for the push-update-broad feature.
I have the following feature request: As the "push-update-broad" feature only works on already connected client(s), it would be nice if the push-update-broad would make an entry too that clients connecting after the command has been send also get the update.
Thanks and BR
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 locating the implementation of the push-update-broad command and the client connection initialization path. Trace how the update is handled for connected clients, then determine how a pending update could reach clients that connect afterward; done means both existing and subsequently connected clients receive the update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100