containerd / containerd/ttrpc-rust
Can the asynchronous client connect operation support asynchronous mode to avoid connect blocking?
- Dominant language
- Rust
- Stars
- 369
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
**Which feature do you think can be improved?**
Can the asynchronous client connect operation support asynchronous mode to avoid connect blocking?
**How can it be improved?**
make socket O_NONBLOCK before connect
**Additional Information**
Anything else to add?
**Before raising this feature request**
Have you looked at the [limitations document](https://github.com/kata-containers/documentation/blob/master/Limitations.md)?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Rust asynchronous client connect operation and the socket setup it uses. Review how the socket is configured before connect, then verify that enabling nonblocking mode avoids connect blocking while preserving the client's connection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100