actioncreator

Can even be split, one for the view specifically another for the more pure actioncreator...

If you prefer, you can ignore this practice and pass the whole dispatch function to the component, and then call `dispatch(actionCreator(params))` directly.

One benefit of this approach is that, you don't need to deal with Dispatcher, ActionCreator, Constant, blablahh.

The todos usually make it seem like you have to to have this flow of information: ActionCreator -> ApiUtil -> ActionCreator -> Store...but if you use the same action creator, you end up with a circular dependency.

Yes, you don't absolutely need the ActionCreator helper methods.

So if we did merge the Flux idea with Cursors, I assume we would keep a single Cursor as the underlying state inside a Store, and then use the traditional Action/ActionCreator model to allow React components/server updates to mutate this Store?