rotor
Event loop friendly C++ actor micro-framework, supervisable (by basiliscos)
Dasynq
Thread-safe cross-platform event loop library in C++ (by davmac314)
Our great sponsors
rotor | Dasynq | |
---|---|---|
8 | 0 | |
318 | 165 | |
- | - | |
8.7 | 5.4 | |
about 1 month ago | 5 days ago | |
C++ | C++ | |
MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rotor
Posts with mentions or reviews of rotor.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-02.
-
Multiplayer, multithreading, and an actor model in C++
What you achieved, is handlers decoupling, i.e. when one handler knows nothing about other handler, which leads to good application testability. However, with standard promise/future bases messaging, if performance matters (and it usually does, otherwise why use C++?), i doubt that your implementation overwhelms the performance of specialized actor libraries, like sobjectizer ("batteries included" actors toolbox) or rotor (DIY-like actor constructor set; disclaimer: I'm the author of it).
- C++ Show and Tell - July 2022
-
Embedded Linux libraries/frameworks
I have been reading the documents from Boost.fibre and Boost.Signals2 which I could use, maybe ASIO for async. I also checked ZeroMQ (this seems to be more or less "only" for networking), Copper and Rotor. If this were just a simple MCU project I would just take the FreeRTOS and would have everything I need. Now I'm just lost how to structure my code / how to realize my main loop.
-
What are some candidate libraries for inter-thread communication like message boxes or event systems?
rotor actor library (I'm the author) was designed to solve similar problem, which I named "actor intrusiveness", when almost every piece of code should be written in form of actor, and, the working threads, which spin actors, are out of your control.
-
Light Actor Concurrency Framework for C++
PS. I'm the author of rotor framework )
-
Sender and Receiver implementations
May be actor frameworks like caf, sobjectizer or rotor is something, that you are looking for.
Dasynq
Posts with mentions or reviews of Dasynq.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning Dasynq yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
When comparing rotor and Dasynq you can also consider the following projects:
C++ Actor Framework - An Open Source Implementation of the Actor Model in C++
libuv - Cross-platform asynchronous I/O
libevent - Event notification library
Boost.Asio - Asio C++ Library
libev - Full-featured high-performance event loop loosely modelled after libevent
uvw - Header-only, event based, tiny and easy to use libuv wrapper in modern C++ - now available as also shared/static library!
sobjectizer - An implementation of Actor, Publish-Subscribe, and CSP models in one rather small C++ framework. With performance, quality, and stability proved by years in the production.
lev - Lightweight C++ wrapper for LibEvent 2 API