From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.107.170.133 with SMTP id g5mr10364131ioj.35.1521670576441; Wed, 21 Mar 2018 15:16:16 -0700 (PDT) X-Received: by 2002:a9d:29d2:: with SMTP id g18-v6mr1335006otd.5.1521670576284; Wed, 21 Mar 2018 15:16:16 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.uzoreto.com!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!199-v6no126706itl.0!news-out.google.com!d3-v6ni146itf.0!nntp.google.com!199-v6no126697itl.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 21 Mar 2018 15:16:15 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2600:387:1:805:0:0:0:65; posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo NNTP-Posting-Host: 2600:387:1:805:0:0:0:65 References: <9ed9edb1-3342-4644-89e8-9bcf404970ee@googlegroups.com> <26a1fe54-750c-45d7-9006-b6fecaa41176@googlegroups.com> <858fbe8b-43a2-4ee3-ad51-1d100123a1a3@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Ada-Oriented GUI From: "Dan'l Miller" Injection-Date: Wed, 21 Mar 2018 22:16:16 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader02.eternal-september.org comp.lang.ada:51113 Date: 2018-03-21T15:16:15-07:00 List-Id: Dmitry wrote:=20 > This is not how asynchronous I/O works in > many cases. The I/O request is=20 > queued in one thread, initiated in another, > processed in third, completed in fourth. (Other than message-queue-based software architectures,) please name even o= ne async =E2=80=A2=E2=80=A2system call=E2=80=A2=E2=80=A2 on any OS or OS-fr= amework thereof that requires traversal of those 4 =E2=80=A2=E2=80=A2app-do= main=E2=80=A2=E2=80=A2 threads to produce results (e.g., filesystem read) a= synchronously. I=E2=80=99ll bet that you cannot name even one actually ext= ant async system call in any OS in the past 50 years to requires such a con= voluted 4 (!) app-domain thread opportunity for reordering via differently-= interleaved queuing at each/any of those 4 threads. What you describe can be a hallmark of message-queue-based software archite= ctures, message-queue software architectures are synonymous with async I/O.