These are chat archives for jdubray/sam
waitFor()? reflux has interesting semantics, though, and i think remains ahead of the game in some ways– actions can be joined in multiple ways! see https://github.com/reflux/refluxjs#joining-parallel-listeners-with-composed-listenables
// node.js env Reflux.nextTick(process.nextTick);
special action that is the join of two other actions, when one of those has fired but not the other, then i'm stuck in a hard-to-describe intermediary state.
The key is not to confound API call with action. An action can encapsulate multiple API calls, no problem, as long as the intermediary results / state of the orchestration have to bearing on the application state until the entire result set if presented to the model
really your actions are much more like *ux's action-creators.