[Bro-Dev] [JIRA] (BIT-1319) topic/jsiwek/broker

Jon Siwek (JIRA) jira at bro-tracker.atlassian.net
Mon Feb 23 08:46:00 PST 2015


     [ https://bro-tracker.atlassian.net/browse/BIT-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon Siwek updated BIT-1319:
---------------------------
    Status: Merge Request  (was: Open)

> topic/jsiwek/broker
> -------------------
>
>                 Key: BIT-1319
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-1319
>             Project: Bro Issue Tracker
>          Issue Type: New Feature
>          Components: Bro
>            Reporter: Jon Siwek
>             Fix For: 2.4
>
>
> The "topic/jsiwek/broker" branch is in the bro and cmake repos to add the initial support for Broker.
> Notes/Disclaimers/Caveats:
> - Bro has a --enable-broker configure flag.
> - requires actor-framework "develop" branch.  When version 0.13 is out, I will put that as a requirement in the README and have CMake check for that.
> - no C bindings yet
> - no Python bindings yet
> - other than checking compilation that the new unit tests pass on Linux/FreeBSD/Mac, I've not done must extensive of testing, profiling, optimization etc.
> - the serialization format for persistent data stores is currently unversioned, so backwards compatibility is pretty sketchy for most data types if they're ever changed in the future.  Should be easy to add a version tag for each C++ class/struct that needs to be persisted.  Do we also need to assume persistent data may be transferred to different hosts (i.e. be mindful of endianness) ?  I guess that could even be an option left to user to select if they're certain they'd rather have a bit better performance than portability.



--
This message was sent by Atlassian JIRA
(v6.4-OD-15-055#64014)


More information about the bro-dev mailing list