Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Zeek renaming: Broker topic names #387
We use "bro/" for several topic strings, but changing that to "zeek/" is technically a breaking change. Maintaining compatibility for subscriptions is something that's easy to do, but compatibility for publications is trickier, however I think the impact of the later is minimal and an entry in NEWS explaining the change in topic name is sufficient. More explanation follows:
Trivial to maintain compatibility (with minimal performance impact) if, for every topic subscription starting with "zeek/", we automatically also subscribe to the "bro/" version of the same topic.
It's trickier to maintain complete compatibility with the things we publish because publishing twice under both "zeek/" and "bro/" versions of a topic name may have performance impact: normally we move data into
However, I think it's fairly safe to just switch to using "zeek/" topics since everything we publish is not meant for external consumption: