[Bro-Dev] script loading changes

Jonathan Siwek jsiwek at ncsa.illinois.edu
Wed Jul 13 19:37:54 PDT 2011

> example, I'd like packages to offer the ability to do something with
> the software framework if it's available, but if it's not available to
> just not load the functionality.

It seems like that approach is well-intended at making packages appear
more modular, but weren't the solutions we came up with taking away 
from a user's ability to control what scripts get loaded?

For example, what if a user wants the ssh package's software-related
scripts to load, but not the http package's software-related scripts?

> I'm starting to recognize that I'm looking to do something like
> dependency injection

Dependency injection patterns are more for object-oriented languages, no?

> but perhaps we're still a bit early on in the
> modularization of Bro scripts for us to figure out how to do this
> well. If everyone's onboard we can just table this discussion for now

Yeah, we might wait.  I'm not fully convinced that the way you currently
organized things actually has a modularity problem that significantly
hinders a user's ability to use bro.

> I would still really like the relative path based loading though

Yeah, I didn't have any problems with that new feature.

- Jon

More information about the bro-dev mailing list