2 added 178 characters in body
source | link

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)
non-blocking
offline (unclear)
batched (incorrect)
network-challenged (😼)
cached (Tomasz)
delayed
...
...
...

(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)

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)
non-blocking
offline (unclear)
batched (incorrect)
network-challenged (😼)
cached (Tomasz)
delayed
...
...
...

(cross-posted on stackoverflow)

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)
non-blocking
offline (unclear)
batched (incorrect)
network-challenged (😼)
cached (Tomasz)
delayed
...
...
...

(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)

    Post Closed as "too localized" by simchona, FumbleFingers, J.R., JeffSahol, waiwai933
1
source | link

Shorter name for “non-blocking with background synchronization?”

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)
non-blocking
offline (unclear)
batched (incorrect)
network-challenged (😼)
cached (Tomasz)
delayed
...
...
...

(cross-posted on stackoverflow)