* Andrea Giammarchi wrote:
>not sure I understand those examples, but the moment a developer starts
>yelding everything, is the moment all non-blovking asynchronous advantages
>are gone 'cause you are waiting instead of keep doing the rest, isn't it?

A simple example would be an application running in a web browser. You
may want to draw three images on a canvas, but the images have to be
downloaded first, and while they are downloading, you still want to re-
spond to user input. With only a single thread of execution, you have
to yield control to the browser while awaiting the images to do so. In
other words, you may not be able to keep doing the rest, but rather
want to do all the other things meanwhile.
-- 
Björn Höhrmann · mailto:bjoern at hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

Andrea Giammarchi wrote:
>not sure I understand those examples, but the moment a developer starts
>yelding everything, is the moment all non-blovking asynchronous advantages
>are gone 'cause you are waiting instead of keep doing the rest, isn't it?

A simple example would be an application running in a web browser. You
may want to draw three images on a canvas, but the images have to be
downloaded first, and while they are downloading, you still want to re-
spond to user input. With only a single thread of execution, you have
to yield control to the browser while awaiting the images to do so. In
other words, you may not be able to keep doing the rest, but rather
want to do all the other things meanwhile.