This is a PR following up the discussion in #50 about zthread/zactor.
This PR adds the following:
A zmqpp::actor class, that aims to be similar to CZMQ zactor.
A zmqpp::signal enumeration that regroup different signal code.
zmqpp::socket and zmqpp::message have new methods to deal with zmqpp::signal.
There is however a few differences between zmqpp::actor and zactor:
The user-defined routine that runs in actor thread can notify its parent it failed to initialize, thus causing the actor constructor to throw.
The actor is allowed to fail its shutdown process. There is no difference between a failed shutdown (ie the thread must stop anyway), but the state of the shutdown can be retrieved by the parent (using a blocking call to stop().
This is a PR following up the discussion in #50 about zthread/zactor.
This PR adds the following:
zmqpp::actor
class, that aims to be similar to CZMQ zactor.zmqpp::signal
enumeration that regroup different signal code.zmqpp::socket
andzmqpp::message
have new methods to deal withzmqpp::signal
.There is however a few differences between
zmqpp::actor
and zactor:stop()
.