eclipse-iceoryx / eclipse-iceoryx/iceoryx2
Async API
- Dominant language
- Rust
- Stars
- 2.5k
- Forks
- 185
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 47
Description
## Brief feature description
Iceoryx2 messaging patterns should support `async` API so they can be used in non blocking, reactive way in runtimes like `tokio` or `async_runtime`
Related:
- https://github.com/eclipse-iceoryx/iceoryx2/issues/627
- https://github.com/eclipse-iceoryx/iceoryx2/issues/246
- https://github.com/eclipse-iceoryx/iceoryx2/issues/47
Contributor guide
Research direction
Start by reading related issues #627, #246, and #47 to understand existing messaging patterns and the intended async scope. Define what support for non-blocking use in runtimes such as tokio or async_runtime must cover, and consider the work done when the relevant messaging patterns expose a usable async API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100