On Mon, Mar 06, 2017 at 13:24 -0500, you wrote:
> I'm playing with rewriting some of the scripts for 2.6 right now with
> events because I think that the broker api is too complicated and
> could potentially have too many side effects. (like overuse of "when"
> for instance).
Yeah, that makes
> On Mar 6, 2017, at 11:43 AM, Robin Sommer wrote:
>
> Whether we want to go further, like with Aashish's proposal, we
> can see then, I'm still a bit undecided there. Either way, a better
> Bro-side UI for Broker is coming, we just need to get the various
> pieces in place
On Sat, Mar 04, 2017 at 00:21 +, you wrote:
> Broker::exists(Cluster::cluster_store, Broker::data("known_hosts"))
> Broker::lookup(Cluster::cluster_store, Broker::data("known_hosts"))
> Broker::set_contains(res2$result, Broker::data(host))
> Broker::add_to_set(Cluster::cluster_store,
> On Mar 3, 2017, at 4:36 PM, Aashish Sharma wrote:
>
> SO I came across a sample of Broker-API usage:
Yeah.. there's a lot of things wrong with how that is being done. There are a
few things going on here.
One is that is no longer functions. I think we should bring this
SO I came across a sample of Broker-API usage:
when (local res = Broker::exists(Cluster::cluster_store,
Broker::data("known_hosts")))
{
local res_bool = Broker::refine_to_bool(res$result);
if(res_bool)
{
when ( local res2 =