nspcc-dev / nspcc-dev/neofs-api
Stream `EOF` support
Open
Nobody has claimed this yet.
discussion
I3
S2
U4
- Dominant language
- Makefile
- Stars
- 11
- Forks
- 15
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
Currently we don't have any mention of a graceful end to the stream. Go gRPC implementation returns EOF on client/server side if server/client closed the stream via corresponding library functionality.
Do we want to unify this behavior on protocol definition level? Possible solutions:
- Require to finish stream with empty request|response body: this will support the completion of the stream at a purely protocol level, and not be tied to the implementation;
- Require to finish stream with
EOF-like status code: alternative way of 2.
Contributor guide
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
The issue names no files, tests, or protocol entry points. Start by locating the stream definitions in the repository and reviewing how the Go gRPC implementation reports stream closure. Done means reaching a decided protocol-level behavior for graceful stream completion and documenting or declaring that behavior consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100