##Thoughts on flux, actions, and doing work in a Flux app
Reference for what I am considering to be "conventional" https://github.com/facebook/flux/tree/master/examples/flux-chat/js
###Many Files This the conventional scheme uses an action flow that goes from Component -> ActionCreator -> APIClient -> ServerActionCreator Problems
- Implementing request/response API call requires edits on 5 files Constants, ActionCreator, APIClient, ServerActionCreator, Store
- ServerActionCreator methods are almost always passthrough boilerplate