RxCpp VS sobjectizer

And, prior to that https://github.com/ReactiveX/RxCpp

Yeah, I know this problem with operators =), original RxCpp implementation also has this problem with implementing all functions into base class and calling dependent functions internally.

Also you can check rxcpp with documentation about reactive approach there. It is functional version of observer/publisher-subscriber patterns with ability to be multithreaded. You can send events from one side, subscribe from another and modify events in meanwhile

+1 for Rx, specifically RxCpp. I've used it in concert with Qt with great results.

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.

An alternative way is using SObjectizer’s timers.

Those who came looking for actor model examples should check out sobjectizer

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).

Hi! I'm a maintainer of SObjectizer project and would like to answer any SObjectizer-related questions. However, I don't know is it the right place to speak about SObjectizer or it could be considered as an advertisement. Anyway, if you want to ask anything about SObjectizer you can do it via GitHub issues.

In sobjectizer the ownership is held by "environment" , while in rotor each thread must held appropriate context, when actor environment is running.

I was looking at SObjectizer as a message box provider, and it seems well designed and the API is nice, but I'm not sure how to go about retro-fitting it into an existing application, since all my threads already exist and I don't really want to change them all into SO "Agents", and I also don't see how to integrate the Dispatcher. I think it's worth a look though, if anyone with experiecne can confirm it is appropriate.

May be actor frameworks like caf, sobjectizer or rotor is something, that you are looking for.

SObjectizer on GitHub