Separating network layer from protocol/processing
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 41
- Forks
- 56
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Description
I would recommend creating a separate protocol/processing layer from network layer which will allow for use in different languages and application stacks.
e.g. I would like to use TiKV in OpenResty (Nginx + Lua) stack where Nginx async socket needs to be used for network communication.
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
Review the existing client-c network and protocol/processing responsibilities first, then trace how network communication is currently wired. Done should mean those layers are separated enough to support an alternate async socket implementation for OpenResty/Nginx and Lua, with the design agreed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, lua, nginx
- Domain
- backend-api-design, networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100