@samitouri / QOS-React-2 / commits / 9f5403b18c

Include image

Vjeux committed Jul 30, 2014 at 19:31 UTC 9f5403b18cc22c1b75ef100dc1a2c56071326d7b
2 files changed +2
docs/_posts/2014-07-30-flux-actions-and-the-dispatcher.md
+2
@@ -24,6 +24,8 @@ Different actions are identified by a type attribute. When all of the stores rec
24
25 Letting the stores update themselves eliminates many entanglements typically found in MVC applications, where cascading updates between models can lead to unstable state and make accurate testing very difficult. The objects within a Flux application are highly decoupled, and adhere very strongly to the [Law of Demeter](http://en.wikipedia.org/wiki/Law_of_Demeter), the principle that each object within a system should know as little as possible about the other objects in the system. This results in software that is more maintainable, adaptable, testable, and easier for new engineering team members to understand.
26
27 +<img src="/react/img/blog/flux-diagram.png" style="width: 100%;" />
28 +
29
30 Why We Need a Dispatcher
31 ------------------------
docs/img/blog/flux-diagram.png
Binary files /dev/null and b/docs/img/blog/flux-diagram.png differ