Flux design pattern - ambiguity about view concept

After reading many explanation about flux design pattern 1, I quite understood how it work.

The dispatcher is a lot like JINI 2 lookup service. And the advantage is clear, the dispatcher doesnt need to know how to perform action and who will perform it. It give you the flexibility to add any store at any time in a continuous integration.

The store is a straight encapsulation of the model and business logic. No problem here, it just have to notify itself to the dispatcher and he will receive action and payload, executing action if supported.

The view is a simple interpretation on data in the store. But the way to notify it, the callback require the view to know who is the store and were it is. Furthermost, the application need to who the view is and were to get it.

In my understanding, the view break the scalability, because while you dont need to know were the action go, you need to know were the result is and the view need to know were the store is. Unless we use another kind of dispatcher between view and store and between client and view.