[Bro-Dev] Plugins providing threads?

[Clark, Gilbert]

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: bro-dev-bounces at bro.org <bro-dev-bounces at bro.org> on behalf of Siwek, Jon <jsiwek at illinois.edu>
Sent: Wednesday, October 08, 2014 11:29 AM
To: Robin Sommer
Cc: bro-dev at bro.org
Subject: Re: [Bro-Dev] Plugins providing threads?

On Oct 7, 2014, at 5:43 PM, Robin Sommer <robin at icir.org> 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
bro-dev at bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev