Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

3

This seems very limited to just the GUI context. In a webserver case, I'd say the main benefit is that it preventing request threads from being "useless" while they wait for blocking IO calls. I think it's a scalability issue as much as it is a responsiveness issue.

sara
– sara

2016-06-08 06:26:11 +00:00
Commented Jun 8, 2016 at 6:26
@kai: Yep, that's the whole point: keep the process as busy as possible to avoid context switch as much as possible.

slebetman
– slebetman

2016-06-08 06:31:38 +00:00
Commented Jun 8, 2016 at 6:31
in asynchronous mode most of the time events are pushed into a queue. because of this you can prioritise, split, filtering, doubling up according to your need.... which in turn makes you app smarter, and faster.

Junchen Liu
– Junchen Liu

2016-11-02 14:34:08 +00:00
Commented Nov 2, 2016 at 14:34

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »