Anguilla provides to different interdiction strategies the default strategy and the strategy, if you
don't change the default configuration, your components using the default strategy.
OK, how does it work?
Well, in the default strategy, state changes can be caused by events like click or submit communication
with external several weeks later and also time outs, time outs and in trouble.
So now let's think a little bit about the structure of the application we are working on right now.
We have a main component with three timeouts.
It's a them with a progress bar and a display component.
So with the full terms of strategy, when Angle detects a possible change on the application in this
case cost, by the time out of this timeout, the dirty tech cycle starts from the root of the application,
passing through all the notes until the further components.
So if we go back to the browser, that's what you see this output three times because this by using
one click look, this check cycle propagates to all of the components.
And because the timer have a binding to this function, it's timer calls the method to make sure the
content hasn't changed.
Every of those looks are also replicated, but this is a completely different thing.
The development Subba runs an extra cycle for every angle cycle.
There's something you don't have to worry about because on production this will not happen to you.
In the next video, you'll see how to optimize Jane's Addiction to avoid these pitfalls.