What would be a short, human name (so that support dude can spell it) for a concept where user action is non-blocking and state is synchronized in the background?

In my case I mark some clients as having really crap network and thus force them into such mode of operation.

Normal mode of operation is on-line, synchronous, blocking, live, soft real-time and ignores cached data.

Modern "offline html5" application do this, AJAX does it, Unix AIO does it, but what is it called?

Candidates so far

asynchronous (spelling)
offline (unclear)
batched (incorrect)
network-challenged (😼)
cached (Tomasz)

(cross-posted on stackoverflow)

(too bad lads decided to close this down, "human word for technical term asynchronous" is a valid question, and will continue to be pertinent until the whole world goes online)

closed as too localized by simchona, FumbleFingers, J.R., JeffSahol, waiwai933 Jun 13 '12 at 19:35

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    'in the background'? – Mitch Jun 13 '12 at 11:22

asynchronous is the correct term. It would probably be appropriate to shorten it to async, which should prove less troublesome from the spelling perspective - not that you wont get other versions, just that it is easier to interpret.

The other term that might work is "out-of-process", which is strictly correct, doesn't suffer the same spelling issues, but might not be comprehensible.

"Batched", thought strictly speaking wrong, may work, because the implications of a batched process are still present. As long as everyone technical understands what is meant.

  • Wonder how async could be 'correct' with the background sync. – Kris Jun 13 '12 at 11:39
  • 2
    As I understand it, the process are happening asynchronously to the user processing - i.e. non-blocking. That is async. – Schroedingers Cat Jun 13 '12 at 12:53

Not the answer you're looking for? Browse other questions tagged or ask your own question.