Extendable protocol needed.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 77
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
We really should have a protocol that is extendable, allowing new fields to be reported without breaking compatibility with older clients. Adding a new protocol version for every new item of data we want to add will be quite cumbersome.
A simple way to improve the current semi-colon separated fields would be to have a field count at the beginning of every group of fields. Then we could add new fields to the end of groups without breaking compatibility with older clients. Older clients wouldn't be able to display the new fields, of course, but all of the old info would still be valid.
Contributor guide
No contributing guide indexed for this repository
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
Locate and read the current semi-colon-separated protocol handling and trace how groups of fields are parsed by clients. Define a compatible field-count approach that permits new fields at the end of each group while preserving all existing information for older clients; completion requires an agreed protocol design and compatibility behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100