Yes exactly, the complete topology event publisher might need to wait for certain time period (may be few seconds) for complete topology request messages before publishing. Otherwise it may publish the same message number of times unnecessarily.
On Fri, Nov 14, 2014 at 11:37 PM, Udara Liyanage <ud...@wso2.com> wrote: > Hi, > > When a message is sent it is received by all subscribers. So we don't need > to send multiple times for multiple requests, isn't it Imesh? > > > > Touched, not typed. Erroneous words are a feature, not a typo. > On Nov 14, 2014 11:15 PM, "Imesh Gunaratne" <im...@apache.org> wrote: > >> Hi Reka, >> >> On Fri, Nov 14, 2014 at 11:56 AM, Reka Thirunavukkarasu <r...@wso2.com> >> wrote: >> >> 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. >> >> +1 I like this idea! We might need to analyze this solution in detail. >> What if multiple topology subscribers send this request message at the same >> time? >> >> >> -- >> Imesh Gunaratne >> >> Technical Lead, WSO2 >> Committer & PMC Member, Apache Stratos >> > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
