Open Merge Requests
===
IDComponentReporter Assignee Updated For
VersionPrioritySummary
--- --- --
- --
> On Dec 15, 2015, at 10:18 AM, Vlad Grigorescu wrote:
>
> The other question I was wondering about is: should this be a BIF?
> Software::parse is a rather lengthy function, with a lot of string
> manipulation, which gets called rather frequently. I suspect there'd be some
> performance impro
The other question I was wondering about is: should this be a BIF?
Software::parse is a rather lengthy function, with a lot of string
manipulation, which gets called rather frequently. I suspect there'd be
some performance improvements for implementing this directly as a BIF.
On Mon, Dec 14, 2015
On Tue, Dec 15, 2015 at 10:23 -0500, you wrote:
> It probably would make sense to measure that first somehow.
Agree. Would be good to keep it in script-land unless it indeed has a
substantial impact (and if so, maybe there are some optimizations to
short-cut common cases or so).
Robin
--
Rob
> On Dec 15, 2015, at 11:23 AM, Robin Sommer wrote:
>
> Agree. Would be good to keep it in script-land unless it indeed has a
> substantial impact (and if so, maybe there are some optimizations to
> short-cut common cases or so).
Yep, something along these lines was/is implemented in the core,
On Mon, Dec 14, 2015 at 17:54 +0100, you wrote:
> I was wondering if is it possible to make an analyzer of OSPF with Binpac.
Anything that's not on top of TCP/UDP remains problematic to support
in Bro currently, unfortunately. It's less a limitation of BinPAC; the
problem is that Bro's lower laye
> ... (and if so, maybe there are some optimizations to
> short-cut common cases or so)
(... and/or: a few key BiFs to add that don't bite off the whole task
but accelerate some particular processing)
___
bro-dev mailing list
bro-dev@bro.org
http://mail
