objects which encapsulate state and behavior, they communicate
exclusively by exchanging messages. Actix actors are implemented
on top of Tokio. Multiple actors can run in
same thread. Actors can run in multiple threads using the
Arbiter API. Actors exchange typed
- User Guide
- Chat on gitter
- GitHub repository
- Cargo package
- Minimum supported Rust version: 1.26 or later
- Async/Sync actors.
- Actor communication in a local/thread context.
- Using Futures for asynchronous message handling.
- HTTP1/HTTP2 support (actix-web)
- Actor supervision.
- Typed messages (No
Anytype). Generic messages are allowed.
resolver- enables dns resolver actor,
signal- enables signals handling actor
At the moment actix uses
While it provides minimum overhead, it has its own limits:
- You cannot use tokio's async file I/O, as it relies on blocking calls that are not available
tokio::ioare the same as file I/O in that regard and cannot be used in asynchronous manner in actix.
A configurable source of time.
Actix system messages
Sync actors support
A helper type for representing different types of message responses.
The address of an actor.
An event loop controller.
A builder to create a customized arbiter.
An actor execution context.
A helper type that implements the
Helper type for representing different type of message responses
A handle to a spawned future.
System is an actor which manages runtime.
Helper object that runs System's event loop
A weakly referenced counterpart to
Actor execution state
The errors that can occur during the message delivery process.
Actors are objects which encapsulate state and behavior.
Actor execution context.
Asynchronous execution context.
Describes how to handle messages of a specific type.
Represent message that can be handled by an actor.
Actors with the ability to restart after failure.
Starts the system and executes the supplied future.
Spawns a future on the current arbiter.
A specialized actor future for asynchronous message handling.
A specialized future for asynchronous message handling.