Notes on RPC and message type harmonization
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- compilers
Research direction
Start with the linked forum RFC and the current DSDL specification’s definitions of message and RPC types. Determine whether RPC request and response forms should be unified as message definitions with an optional response type, and document an agreed syntax and compatibility implications.
Written by the indexing model from the issue text.
Description
If the named topic development continues roughly along the lines outlined in this post: https://forum.opencyphal.org/t/rfc-zero-configuration-cyphal-with-named-topics/2376/7?u=pavel.kirienko, then it would be desirable to reflect the unification of topics with RPCs in the DSDL language design. Specifically, right now we have two distinct categories of types: message types and RPC types. The former will stay as-is, while the latter may need to be made a subset of message types, where the request part becomes just an ordinary message definition, and the response part becomes the optional response type of the message.
For example, an ordinary message definition implies that no response type is defined for it:
# Message.1.0
float16 value
@sealed
While messages that prescribe a response (whether mandatory or optional) will contain the additional section at the end:
# Message.1.0
float16 value
@sealed
---
# Message.Response.1.0
float16 response_value
@sealed
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- 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 OpenCyphal/dsdl_specification
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Explicit structuringOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
OpenCyphal/dsdl_specification#6 · 1 comment ·
All issues in OpenCyphal/dsdl_specification
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 82/100
supercollider/supercollider#7872 · 1 comment ·
Maintainers usually reply within 1 day
-
bug I/O low priority semantics
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cisco/ChezScheme#1110 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
pocket-stack/pocketjs#729 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day