> Not sure I like that. The library is called Broker, so "broker" seems
> the natural namespace to me.
All right, let's keep it as is. This is also aligns with the sentiment
at our Gitter room.
> I think the better solution would be finding a different name for
> those things now called "broker"
On Wed, May 11, 2016 at 18:07 -0700, you wrote:
> I'm considering renaming the C++ broker namespace from "broker" to
> "bro". After all, it's *Bro's* communication library.
Not sure I like that. The library is called Broker, so "broker" seems
the natural namespace to me. And it's not really jus
Jan,
> I guess the function for initialization receives the index that should
> be initialized.
Thank you. This works!
For future reference:
I also needed to convert the following table to use opaque of cardinality for
this table grows reasonably big:
global distinct_backscatter_peers: ta
> how do I declare (3) so that I can avoid the "&default function type clash"
> error above.
I guess the function for initialization receives the index that should
be initialized. In this case the index consists of two values. I tried
the following and Bro did not complain:
global c_likely_scan
So I am trying to convert tables into using opaque of cardinality since thats
more memory efficient (or counting bloomfilters for that matter):
works: if table (0) converted to (1)
errors: if table (2) converted to (3)
Details: I am trying the following, original table (0) converted to (1):
