Redux over the wire?

[sergey-lapin]

This is a great way of using flux on mobile, with web workers or whatever - splitting it on the client and server.
Could this be done in redux? This seems to me more magical as redux has stateless stores. Typically the simplest solution of this is to keep state in stores and stream stores changes to components which are located in other context.

[sergey-lapin]

As I understood from middleware docs it is pretty easy to intercept and even redirect actions.

So in this scheme direction from Component to Store Producer is manageable so I can log actions to some other context for example.

          +----------------> onChange ---------------+
          |                                          v
    Store Producer/Action Consumer          Store Consumer/Action Producer
       "SSoT" or "Dispatcher"                  "View" or "Component"
          ^                                          |
          +---------------- onDispatch --------------+

But is that possible to intercept store changes in the same way?

[sergey-lapin]

I am looking for such configuration:

client reponsibility:
generate actions
consume store changes

server reponsibility:
generate store changes
consume actions

As I comprehend redux API only action generation is interceptable for now.

[sergey-lapin]

Figured out solution, thanks to @raydeo.
redux has public methods to subscribe/get notified on new state (subscribe, getState),
(which allows to generate store changes)
and dispatch
(which allows to consume actions)

To consume store changes I need to create special store-reducer that set new state on some action, and
dispatch({type: SET_STATE, newState: stateFromServer})
(which allows to consume store changes)

middleware allows to intercept and generate actions.

[sergey-lapin]

Here is implemention of this approach and demo

[gaearon]

Let's continue this discussion in #313.