, and
another for core - external
-Gilbert
From: bro-dev-boun...@bro.org bro-dev-boun...@bro.org on behalf of Siwek, Jon
jsi...@illinois.edu
Sent: Wednesday, October 08, 2014 11:29 AM
To: Robin Sommer
Cc: bro-dev@bro.org
Subject: Re: [Bro-Dev] Plugins
On Oct 8, 2014, at 12:47 PM, Clark, Gilbert gc355...@ohio.edu wrote:
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
I'm wondering if we should add another type of plugin component:
threads. This would be for functionality that's to run in parallel
with Bro's main thread, and communicate with it via message passing.
We have the structure for that in place already, logging and reading
are using it as already.
Very timely question, I've be mulling over this and I would like to vote for
adding thread component.
This may allow us to do a lot more processing of data in the script land.
Now my use case may not be likely an ideal one.
I am *experimenting* with a policy to flag very long sustained
On Tue, Oct 07, 2014 at 16:11 -0700, you wrote:
This may allow us to do a lot more processing of data in the script land.
Well, that's a different thing. I was talking about plugins in core
land, written in C++. Threading in script-land is nothing I see
happening soon unfortunately ...
Robin
