Expand description
§Orb
Orb is an abstraction layer for writing runtime-agnostic async Rust code, allowing you to write code that works with different async runtimes, like tokio or smol.
We took the name Orb because it gets around :)
§Features
- Runtime Agnostic: Write code that works with multiple async runtimes
- The hehavior of this crate is more aligned to tokio, to prevent unnotice bugs (for example, dropping a task handle means detach by default)
- Extensible: Easy to implement support for new runtimes as plugin, without modification to the main crate.
- networking:
- Provide unify abstraction (tcp + unix) as
UnifyListener/UnifyStream - Non-blocking name resolving: via
ResolveAddrtrait
- Provide unify abstraction (tcp + unix) as
§The goal
The main goal is to decouple your application logic from specific async runtime implementations, allowing you to:
- Write portable async code that works at the same time in combination of multiple runtimes
- Switch to new runtimes without changing your core logic
- Test your code with different runtime characteristics
- Enhance async network programing experience
This is a side project during the development of razor-rpc. Because:
- There is no established standard for designing different runtimes, when developing shared libraries, developers often only target specific runtimes.
- Using too many
#[cfg(feature=xxx)]in code makes it hard to read. - Runtimes like
smolecology enable you to customize executors, but there’s high learning cost, and lack utility functions (for example, there’s notimeoutfunction inasync-ioorsmol). - Passing features through sub-projects through multiple layers of cargo dependencies is even more difficult. (that’s why we don’t use feature in this crate)
- If users want to customize a runtime for their own needs, they face the dilemma of incomplete ecosystem support.
- Some projects like Hyper define abstraction layers, having each project do this individually is a huge maintenance cost.
This is why this crate was written.
§Usage
To use Orb, you need to depend on both the core orb crate and a runtime adapter crate like orb-tokio or orb-smol.
In your Cargo.toml:
[dependencies]
# when you write runtime agnostic codes
orb = "0"
# when you setup as end-user
orb-tokio = "0"
# or
orb-smol = "0"There’s a global trait AsyncRuntime that combines all features at the crate level, and adding use orb::prelude::* will import all the traits you need.
There are some variants of the new() function, also refer to the documentation in the sub-crates:
§License
This project is licensed under the MIT License - see the LICENSE file for details.
§Modules
runtime- Traits for task spawn, join and block_on.io- Traits for asynchronous I/O operations, and buffered I/O wrapper.net- Wrapper types for networking, and a “unify” type for tcp + unix stream.time- Traits for time-related operations like sleeping and intervalsutils- Utility types and functions
At top level AsyncRuntime trait will combine all the capabilities, including
AsyncExec, AsyncIO, and AsyncTime.
§Runtime Varieties Note
§Task Detach
The drop behavior of task handle is unified to “detach”, task will not be cancel unless abort is called.
§Panic
- tokio will issolate panic between tasks, a task handle may return Err() on join.
- smol will not issolate panic. Although a panic hook will work, the program might panic if one
of the task panic. You may use feature
unwindto enable panic capturing.
§Cloning
Both TokioRT and SmolRT have impl Clone, but AsyncRuntime and AsyncExec does not
include Clone because not sure about other runtime. you may explicitly mark Clone with our
trait marker.
§Inherence
You can write your own trait by inheriting AsyncRuntime or any other trait, to provide extra
functions along with the runtime object.
There’s an blanket trait to auto impl AsyncRuntime on anything that is Deref<Target> to an AsyncRuntime.
pub trait AsyncRuntime: AsyncExec + AsyncIO + AsyncTime {}
impl<F: std::ops::Deref<Target = T> + Send + Sync + 'static, T: AsyncRuntime> AsyncRuntime for F {}Simimlar blanket trait can be found on other sub traits.
Modules§
- io
- Asynchronous I/O traits and utilities.
- net
- TCP and Unix domain socket listener implementations.
- prelude
- Re-export all the traits you need
- runtime
- Runtime execution traits for async task management.
- time
- Time-related traits and utilities for async operations.
- utils
- Utility types and functions for async operations.
Traits§
- Async
Runtime - A marker trait that combines all the core async runtime capabilities,
including
AsyncExec,AsyncIO, andAsyncTime. It serves as a convenient way to specify that a type provides all the core async runtime functionality.