Extendable protocol needed.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- networking
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.
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.
- Dominant language
- C
- Stars
- 78
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from llnl/lmt
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
fix single key commands consistency and documentationMay be free again @defaziogiancarlo claimed this 1673 days ago, and no pull request is open. Open
-
remove legacy codeMay be free again @defaziogiancarlo claimed this 1673 days ago, and no pull request is open. Open
Similar issues
-
ai-driven-fuzzing bug claude Minor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linagora/open-bastion#425 ·
Maintainers usually reply within 1 day
-
question
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
examples/dnsdoctor: cleanup.sh stops at the first missing piece of a setup.sh that did not finishOpenseverity: low
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
luainkernel/lunatik#2263 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
vercel-labs/scriptc#2910 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
darktable-org/darktable#22939 ·
Maintainers usually reply within 1 day