How can we turn a DQMH module into a DQMH Actor? What could that bringing-to-life of a DQMH module actually look like? Any queued message handler already comes with everything we need to bring it to life, you might say. This blog post is not about the Actor Framework. We want DQMH Actors!ĭQMH Actor: Self-Messaging or Helper Loop?Ĭaveat: When I say actor, I really mean a DQMH module that executes code by itself, without its’ request events being called. Modules shall actively poll for information, acquire data from hardware, manage network connections, and more. We want them to do more than merely sit there, waiting for work to be thrown at them. Sometimes (actually more often than not), we want our modules to be more than passive libraries.
0 Comments
Leave a Reply. |