This is why they gave the presentation on Flux, which is architecturally how Facebook solves this problem. Basically the first principal you must learn is to f

This is why they gave the presentation on Flux, which is architecturally how Facebook solves this problem. Basically the first principal you must learn is to find the lowest common ancestor to store state. (http://facebook.github.io/react/blog/2013/11/05/thinking-in-react.html http://facebook.github.io/react/blog/2013/11/05/thinking-in-...) After realizing this the immediate thing people do is pass call backs through children so grandchildren's actions can communicate with where the state is. This leaks through all the components however, which is why Flux separates actions out into something that all the components have access to.