Re: [Bro-Dev] [Bro-Commits] [git/broker] topic/actor-system: Add broker::bro::RelayEvent message type. (ce86016)

On Fri, Dec 15, 2017 at 10:29 AM, Robin Sommer wrote: > Yeah, though then I'd actually say it's worth keeping multi-hop > topologies in mind at least. We don't need to fully solve this right > now; nobody really knows yet how topologies may end up looking in the > future. But a

Re: [Bro-Dev] [Bro-Commits] [git/broker] topic/actor-system: Add broker::bro::RelayEvent message type. (ce86016)

On Thu, Dec 14, 2017 at 15:27 -0600, you wrote: > or proxy/data to all other proxy/data nodes (within these classes, > nodes aren't connected with each other) was frequent enough to warrant > putting in a single, simple function call like this. Yeah, though then I'd actually say it's worth

Re: [Bro-Dev] [Bro-Commits] [git/broker] topic/actor-system: Add broker::bro::RelayEvent message type. (ce86016)

On Thu, Dec 14, 2017 at 2:07 PM, Robin Sommer wrote: > I'm curious what's the use case for this? >From last month's thread regarding cluster API/topology changes, the message pattern of sending an event from a worker to all other workers or proxy/data to all other proxy/data

Re: [Bro-Dev] [Bro-Commits] [git/broker] topic/actor-system: Add broker::bro::RelayEvent message type. (ce86016)

Hi Jon, I'm curious what's the use case for this? Generally I think it's best to use a combination of Broker-internal forwarding and topics to control where messages get propagated too, as that will better generalize to larger topologies later. The less of the routing we control manually at the