> On Jul 27, 2018, at 6:10 PM, Jon Siwek wrote:
>
> On Fri, Jul 27, 2018 at 3:55 PM Azoff, Justin S wrote:
>
>> I do agree that there's room for a lot of simplification, for example a
>> worker broadcasting a message efficiently to all
>> other workers needs to do something like this from
On Fri, Jul 27, 2018 at 3:55 PM Azoff, Justin S wrote:
> I do agree that there's room for a lot of simplification, for example a
> worker broadcasting a message efficiently to all
> other workers needs to do something like this from the docs:
>
> Cluster::relay_rr(Cluster::proxy_pool,
> On Jul 27, 2018, at 1:39 PM, Robin Sommer wrote:
>
> I'm wondering if we should give it another try to simply this API
> while we still can (i.e., before 2.6 goes out). To me, the most
> intuitive publish operation is "send to topic T and propagate to
> everybody subscribed to that topic".
On Fri, Jul 27, 2018 at 12:40 PM Robin Sommer wrote:
> I'm wondering if we should give it another try to simply this API
> while we still can (i.e., before 2.6 goes out). To me, the most
> intuitive publish operation is "send to topic T and propagate to
> everybody subscribed to that topic". I'd
The other day when merging Johanna's code to clusterize the
configuration framework, I noticed this code in there:
# [Send id=val to everyone else]
Broker::publish(change_topic, Config::cluster_set_option, ID, val,
location);
if ( Cluster::local_node_type() != Cluster::MANAGER )
