Would it make sense to replace the existing inter-thread communication code with the broker / porting the existing writers and readers to use the actor framework? This way, there would only be a single, shared message-passing mechanism inside of bro, instead of having one for core <-> threads, and another for core <-> external
-Gilbert ________________________________________ From: [email protected] <[email protected]> on behalf of Siwek, Jon <[email protected]> Sent: Wednesday, October 08, 2014 11:29 AM To: Robin Sommer Cc: [email protected] Subject: Re: [Bro-Dev] Plugins providing threads? On Oct 7, 2014, at 5:43 PM, Robin Sommer <[email protected]> wrote: > Jon, how are you planing to integrate Broker into Bro? Would this help > there as well if you could just follow a similar structure with Broker > running inside its own thread? Mostly planning to integrate as IOSource(s) in the main thread as I expect many of the messages either originate or terminate there due to script-land interactivity. Broker’s internal processing is to be scheduled to threads automatically by actor-framework. Wrapping all Broker-related messaging as a Bro-thread that does its own message passing seems like an unneeded indirection as Broker already facilitates its own message passing between endpoints (as it’s built on top of the more-generalized actor-framework message passing). - Jon _______________________________________________ bro-dev mailing list [email protected] http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev _______________________________________________ bro-dev mailing list [email protected] http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
