Duplicate API requests about flummox-isomorphic-demo

[acdlite]

Hmm, it's hard for me to know how to answer this without more specifics. One possible solution would be to pass a timestamp along with the payload so your store handler can determine how to deal with multiple actions:

// actions.js
async getThing() {
  let thing = await RESTUtils.fetchThing();
  return {
    thing,
    timestamp: Date.now()
  };
}

// store.js
handleGetThing({ thing, timestamp }) {
  if (timestamp > this.latestTimestamp) {
    this.latestTimestamp = timestamp;
    // do something
  } else {
    // do something else
  }
}

(This isn't something I've actually tried; just an idea.)

[simenbrekken]

On second thought these kinds of race conditions are probably best handled in the actual API module by aborting duplicate requests, that way the success/failure counterparts of an action will never get fired and thus don't need to be explicitly handled.

[ivan-kleshnin]

@simenbrekken as long as your backend is clustered this is not so easy.
I wouldn't rely on backend to implement debounce for you, because you waste you network traffic and processor ticks to perform useless work even if duplicate requests are thrown away.

@acdlite do we have any API to temporary unsubscribe from subsequent events on actionBegin and resubscribe on actionCompleted / actionFailed? Or somehow debounce events in other way. This should be at Action level.

This demoes again how custom event architectures loose against Rx beauty...