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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.107.16.9 with SMTP id y9mr7333835ioi.7.1445444292846; Wed, 21 Oct 2015 09:18:12 -0700 (PDT) X-Received: by 10.182.72.132 with SMTP id d4mr149167obv.18.1445444292786; Wed, 21 Oct 2015 09:18:12 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!kq10no24794227igb.0!news-out.google.com!z4ni27768ign.0!nntp.google.com!kq10no20789832igb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 21 Oct 2015 09:18:12 -0700 (PDT) In-Reply-To: <1wvo1b25eaa4o$.1y03vu1to6vux$.dlg@40tude.net> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=147.173.50.100; posting-account=21X1fwoAAABfSGdxRzzAXr3Ux_KE3tHr NNTP-Posting-Host: 147.173.50.100 References: <75f38e30-42ba-4e98-8f36-2218b5167209@googlegroups.com> <1wvo1b25eaa4o$.1y03vu1to6vux$.dlg@40tude.net> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Musings on RxAda From: Hadrien Grasland Injection-Date: Wed, 21 Oct 2015 16:18:12 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: news.eternal-september.org comp.lang.ada:28013 Date: 2015-10-21T09:18:12-07:00 List-Id: Yes, thinking about it some more, this implementation of Observer is REALLY wrong. It actually is blocking in two different places where it shouldn't block : before the accept, and within the accept. I do believe, however, that a task which blocks or performs CPU work after the rendezvous is acceptable, and could be used to achieve some parallelism in the context of a true data pipeline (i.e. more than 1 input).