Hi Udara, On Fri, Nov 14, 2014 at 12:15 PM, Udara Liyanage <ud...@wso2.com> wrote:
> Hi Reka, > > Then CC does not publish complete topology periodically? > Reducing event publish timeout adds overhead to the MQTT broker. It > depends on the network, for fast networks it is ok. > Is timeout is configurable? if not we can make it configurable and let the > user decide it depending on their network. > We have a cron job scheduled to send the Complete Topology. So, not sure whether we can make it to send in seconds..Also, since Complete Topology is considerably large one, sending it frequently may affect the broker as we are using matt which is to send small events. Thanks, Reka > > On Fri, Nov 14, 2014 at 11:56 AM, Reka Thirunavukkarasu <r...@wso2.com> > wrote: > >> Hi >> >> Since we have CA also listening to Topology now, CA is taking ~1 minute >> to receive the complete Topology as we send the Complete Topology in every >> 1 min. Can we reduce this by introducing a new topic where CA can publish >> an event by stating that it is up? So, CC can listen on that topic and >> immediately send the complete Topology. This topic can be used by all other >> subscribers of Topology who require Complete Topology. >> >> Would this be a feasible approach to reduce the waiting time to get the >> Complete Topology? or Is it better to send the Complete Topology in every >> 30s/15s? >> >> Thanks, >> Reka >> >> >> -- >> Reka Thirunavukkarasu >> Senior Software Engineer, >> WSO2, Inc.:http://wso2.com, >> Mobile: +94776442007 >> >> >> > > > -- > > Udara Liyanage > Software Engineer > WSO2, Inc.: http://wso2.com > lean. enterprise. middleware > > web: http://udaraliyanage.wordpress.com > phone: +94 71 443 6897 > -- Reka Thirunavukkarasu Senior Software Engineer, WSO2, Inc.:http://wso2.com, Mobile: +94776442007
