You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Neverlord pointed out that the zeek.hh could move into Zeek to fully decouple Zeek and broker. As far as I can tell, this would require the python bindings as well as some testing to move as well.
The text was updated successfully, but these errors were encountered:
As far as I can tell, this would require the python bindings as well as some testing to move as well.
I wouldn't move the bindings. I'd say this ticket is simply blocked by #303. Once the bindings are gone, there's no technical reason anymore for the zeek.hh header to stay in the Broker code base and we can instead move to over to the Zeek side.
@Neverlord pointed out that the
zeek.hh
could move into Zeek to fully decouple Zeek and broker. As far as I can tell, this would require the python bindings as well as some testing to move as well.The text was updated successfully, but these errors were encountered: