Hi Udara, Yes, that is how it is done. When the first CompleteTopologyEvent is received, the topology is updated and a flag is set to stop further processing of the event.
Regards, Chamila de Alwis Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Sat, Nov 22, 2014 at 7:24 AM, Udara Liyanage <[email protected]> wrote: > Hi Chamila, > > Component first wait for complete topology to build its in memory model. > Later individual events update the in memory model. That's the current > model. I am not sure whether components update its in memory upon each > Complete topology event receiving, I guess it need not to. > > > > Touched, not typed. Erroneous words are a feature, not a typo. > On Nov 22, 2014 3:16 AM, "Chamila De Alwis" <[email protected]> wrote: > >> Hi, >> >> Is the $subject reasonable at a point when there is no event to represent >> a specific change done to a particular member? >> >> The scenario is a component whose topology information is outdated >> because when a particular state change is done a corresponding event is not >> being fired. >> >> Or is the idea to use Member{Status}Event to broadcast a member status >> change among the listeners? >> >> >> Regards, >> Chamila de Alwis >> Software Engineer | WSO2 | +94772207163 >> Blog: code.chamiladealwis.com >> >> >>
