› Async::Actor

Async::Actor

Provides a simple actor model for asynchronous programming.

Development Status

Motivation

Async provides a strongly opinionated model for asynchronous programming while trying to be transparent to the user. However, in cases where the scope (life time) of the asynchronous work does not align with the scope of the application code, it can be tricky to combine the two. For example, you may want to introduce a background message queue or job processing system, which takes advantage of async, without changing the execution model of the calling code. The jobs or message queue will almost certainly outlive the scope of the calling code, so it can be advantageous to separate the two.

This is where Async::Actor comes in. It provides a simple actor model, which uses an event driven message queue running inside an Async event loop. This separates the life cycle of the calling code and the actor and can be used to introduce asynchronous processing into existing code with minimal changes.

Usage

Please browse the source code index or refer to the guides below.

Getting Started

This guide explains how to use async-actor for asynchronous programming.

Releases

Please browse the releases for more details.

v0.2.0

v0.1.1

  • Fix dependency on async gem to use >= 1 instead of ~> 1 for better compatibility.
  • Update guide links in documentation.

v0.1.0

  • Initial release of async-actor gem.
  • Core actor model implementation with Async::Actor class.
  • Proxy class for safe cross-actor communication.
  • Variable class for thread-safe value storage and updates.

Contributing

We welcome contributions to this project.

  1. Fork it.
  2. Create your feature branch (git checkout -b my-new-feature).
  3. Commit your changes (git commit -am 'Add some feature').
  4. Push to the branch (git push origin my-new-feature).
  5. Create new Pull Request.

Developer Certificate of Origin

In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.

Community Guidelines

This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.