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.31.110.203 with SMTP id j194mr1346048vkc.15.1485495342060; Thu, 26 Jan 2017 21:35:42 -0800 (PST) X-Received: by 10.157.43.215 with SMTP id u81mr481939ota.15.1485495341868; Thu, 26 Jan 2017 21:35:41 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!i7no382630qta.1!news-out.google.com!15ni11822itm.0!nntp.google.com!r185no554458ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 26 Jan 2017 21:35:41 -0800 (PST) In-Reply-To: <8706d548-a9d5-48e5-aa6f-fd33013a2fd1@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=85.167.236.133; posting-account=bPTmZAoAAAC_6HP9XLKB9aAAxBa6BuOR NNTP-Posting-Host: 85.167.236.133 References: <65f79e53-a468-4b77-8ee1-440c26a09371@googlegroups.com> <8706d548-a9d5-48e5-aa6f-fd33013a2fd1@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Question on type invariants From: reinkor Injection-Date: Fri, 27 Jan 2017 05:35:41 +0000 Content-Type: text/plain; charset=UTF-8 X-Received-Bytes: 1494 X-Received-Body-CRC: 1025122769 Xref: news.eternal-september.org comp.lang.ada:33184 Date: 2017-01-26T21:35:41-08:00 List-Id: > The potential problem here is that the timestamps may not be of sufficient granularity. What about to use "wait" statements to ensure S is up-to-date? I.e. make a request to wait for update of A. Then wait for confirmation that waiting time has started and then go ahead to update? A (kind of) "collaborative approach" ? :-)