Clarification on RELP spec with regard to reply ordering
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 32
- Forks
- 39
- Avg merge
- 2h 27m
- Merged PRs (30d)
- 7
Description
in reference to: https://github.com/rsyslog/librelp/blob/master/doc/relp.html
I may be reading it incorrectly, but it seems like the first couple of sentences are in conflict with each-other.
The server may reply in any order
Responses must be sent by the server in the exact same order as commands where received
I'm a bit confused by what this means practically...
Can syslog commands from the client be responded to out of order?, or is the next rsp command always going to be the lowest transaction for which there has not been an rsp seen?
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
Read doc/relp.html and compare the two quoted statements about reply ordering. Determine the intended practical behavior for server responses, then clarify the conflicting wording in the RELP specification so the ordering rule is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100