Mixing and Matching Messaging Architectures

[GregFreeman]

I'm wondering how people feel about mixing messaging architectures in an application. For instance, I have some reusable code that fits the actor framework nicely due to its dynamic launching of VIs that it already has built in. But there are other parts of my application with static loops for which it is much more intuitive to the average user to use LapDog. Is it in general bad practice to mix and match the two; better asked, would it be confusing if you picked up a project that used both?

[todd]

I'm playing with "zero-coupled" AF components that are used by message handlers. The difficult part so far is managing the top-level actor in the "root" diagram (main.vi). Specifically, creating events or queues in main and passing them both to the control actor and to the message handlers.