| 1 |
Broker 1.4.0 |
| 2 |
============ |
| 3 |
|
| 4 |
- Adds a new ``broker::store_event`` API that can be used to observe |
| 5 |
data store modifications. |
| 6 |
|
| 7 |
- Adds support for Windows platform. |
| 8 |
|
| 9 |
- RocksDB support is now opt-in instead of automatically detected and used |
| 10 |
at configuration-time. Use the ``--enable-rocksdb`` and |
| 11 |
``--with-rocksdb=`` flags to opt-in. |
| 12 |
|
| 13 |
Broker 1.3.0 |
| 14 |
============ |
| 15 |
|
| 16 |
- A C++17-capable compiler and CMake 3.0+ are now required to compile Broker |
| 17 |
|
| 18 |
- Broker 1.3.0 depends on CAF 0.17.4. Broker 1.2.x had depended on CAF 0.16.x, |
| 19 |
whose wire format changed and is now incompatible with CAF 0.17.x. |
| 20 |
Zeek 3.0.x shipped with Broker 1.2.x, which means Broker 1.3.x cannot be |
| 21 |
used to communicate with Zeek 3.0.x, only 3.1.x (and possibly later, check |
| 22 |
for updated release notes for compatibility clarifications). |
| 23 |
|
| 24 |
Broker 1.2.0 |
| 25 |
============ |
| 26 |
|
| 27 |
This release contains breaking API changes (for C++ code, not Python) |
| 28 |
in order to increase messaging efficiency via reduction of data |
| 29 |
copying. Specifically: |
| 30 |
|
| 31 |
- ``broker::subscriber::get()`` now returns a different, copy-on-write |
| 32 |
type called ``broker::data_message`` rather than an |
| 33 |
``std::pair<topic, data>``. For example this old code:: |
| 34 |
|
| 35 |
auto sub = ep.make_subscriber({"/topic/test"}); |
| 36 |
auto msg = sub.get(); |
| 37 |
auto& topic = msg.first; |
| 38 |
auto& data = msg.second |
| 39 |
|
| 40 |
can be changed to:: |
| 41 |
|
| 42 |
auto sub = ep.make_subscriber({"/topic/test"}); |
| 43 |
auto msg = sub.get(); |
| 44 |
auto& topic = broker::get_topic(msg); |
| 45 |
auto& data = broker::get_data(msg); |
| 46 |
|
| 47 |
- ``broker::endpoint::publish(vector)`` now takes a vector of the new |
| 48 |
``broker::data_message`` type, not ``std::pair<topic, data>`` |
| 49 |
|
| 50 |
- Generally, all type aliases within classes, like |
| 51 |
``value_type = std::pair<topic, data>``, have been changed to use the |
| 52 |
new ``broker::data_message`` type. |
| 53 |
|
| 54 |
- The semantics of message forwarding have changed slightly: the |
| 55 |
first sender of the message is now the one that applies the initial |
| 56 |
TTL value. Previously, the first receiver would be the one to |
| 57 |
apply the initial TTL. |