当协议越来越多时候如何分模块管理?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- api, backend-api-design
Research direction
No file, test, or entry point is named in the issue. Begin by locating the implementation and documentation for .package, get, and result, then verify each question against the protocol definitions. Done would require clear guidance on field behavior, naming and limits, key fields, and managing larger protocol sets.
Written by the indexing model from the issue text.
Description
1、.package的结构体是否固定需要?里面的type和session有何作用,是否可变?
2、如”get 1 {}",这里的1是否有上限?get命名标准是什么?
3、如“result 0 : *datastruct(id)",这里的key字段一定要是结构体datastruct里面的字段吗?
4、当协议越来越多,规模越来越大,如何分模块管理?有没有什么好的建议?
我以前没接触过protobuf这类型的协议,云大能给点小小建议吗?非常感谢!
- Dominant language
- C
- Stars
- 985
- Forks
- 254
- 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 cloudwu/sproto
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
proposal:去掉定点数Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
有dart版本的吗?Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenXiangShan/NEMU#1287 ·
Maintainers usually reply within 1 day
-
area: recompiler area: runtime kind: bug preview-effort: small priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day