sobjectizer
copper
sobjectizer | copper | |
---|---|---|
15 | 6 | |
456 | 167 | |
1.3% | - | |
9.1 | 0.0 | |
about 1 month ago | 10 months ago | |
C++ | C++ | |
GNU General Public License v3.0 or later | MIT License |
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.
sobjectizer
-
SObjectizer Tales - Epilogue
Message Delivery Tracing aims to debug an application built on top of SObjectizer. In essence, it logs the primary stages of the message delivery process, allowing visibility into whether there is a suitable subscriber with the corresponding event handler.
-
SObjectizer Tales - 27. Design ideas
An additional rationale for structuring cooperations in hierarchies is to facilitate the sharing and propagation of dispatchers. A recent update of SObjectizer includes new functionalities that allow access to both agent and cooperation dispatchers. This enhancement was prompted by feedback provided by a user and myself.
-
SObjectizer Tales - 26. Dispatcher selection
If a stop signal arrives, it will be enqueued at the end as a demand for image_producer_callback. This means, it will be processed after the other 6 demands currently in the queue. Maybe this is not an issue but in some cases it might be. At this point, another feature of SObjectizer is to consider: agent priorities. Essentially, this feature allows for the demands to be handled in different orders based on the priorities of agents. In this context, if we assign image_producer_callback a higher priority than others, the “stop signal” would be processed before the rest of the requests.
-
SObjectizer Tales - 23. Mutable messages
The real solution consists in using another slick feature of SObjectizer: mutable messages.
-
SObjectizer Tales - 8. Representing errors
However, this kind of filtering is inefficient and might result in a significant run-time cost. Indeed, every empty cv::Mat follows all the message handling workflow, only to be thrown out. Although we expect that empty images will be sporadic, a more idiomatic approach exists: delivery filters.
-
SObjectizer Tales – 6. Is the stream still in progress?
SObjectizer’s agent states are quite sophisticated and provide some utilities that might be useful for developing a working solution. First of all, image_viewer can be modeled as a two-state agent:
-
SObjectizer Tales - 5. Sending commands
An alternative way is using SObjectizer’s timers.
-
Multiplayer, multithreading, and an actor model in C++
Those who came looking for actor model examples should check out sobjectizer
-
What are some candidate libraries for inter-thread communication like message boxes or event systems?
In sobjectizer the ownership is held by "environment" , while in rotor each thread must held appropriate context, when actor environment is running.
-
Sender and Receiver implementations
May be actor frameworks like caf, sobjectizer or rotor is something, that you are looking for.
copper
-
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?
In the meantime, are you aware of any projects that are similar? Have you come across copper? It looks nicely designed - is this the kind of thing you imagine would be similar?
-
Richard’s May 2021 Update - Go channels in C++ - part 1
You might be interested in having a look at my recent library with a similar goal: https://github.com/atollk/copper
-
Copper: Powerful and convenient communication between threads
Looking at the reference docs, and just wow. This is a very well documented project, great work!
What are some alternatives?
concurrencpp - Modern concurrency for C++. Tasks, executors, timers and C++20 coroutines to rule them all
RxCpp - Reactive Extensions for C++
eCAL - Please visit the new repository: https://github.com/eclipse-ecal/ecal
Aeron - Efficient reliable UDP unicast, UDP multicast, and IPC message transport
rotor - Event loop friendly C++ actor micro-framework, supervisable
iceoryx - Eclipse iceoryx™ - true zero-copy inter-process-communication
so5-dining-philosophers - Several implementations of solutions for "Dining Philosophers" problem built by using Actor and CSP models on top of SObjectizer framework
BlockingCollection - C++11 thread safe, multi-producer, multi-consumer blocking queue, stack & priority queue class
Disruptor-cpp - Port of LMAX Disruptor to C++