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=0.6 required=5.0 tests=BAYES_40,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,d8d74deccba7cf0b
X-Google-Attributes: gid103376,public
From: Barry and Jackie Schiff <schiff@netspace.net.au>
Subject: Re: Ada and Distributed Objects - Seeking Success Stories
Date: 1997/05/07
Message-ID: <3370531B.2B7E@netspace.net.au>#1/1
X-Deja-AN: 239941115
References: <336DC9E2.6350@netspace.net.au> <5kn91r$jio@top.mitre.org>
Organization: Netspace Online Systems
Newsgroups: comp.lang.ada
Date: 1997-05-07T00:00:00+00:00
List-Id: <comp.lang.ada>


Michael F Brenner wrote:

> This sounds like an interesting project, but I am curious why it is called
> real-time, which usually means that each transaction must be completed by
> a specific deadline. This description seems to have unlimited delays in
> each remote procedure call, each client server interaction, and each
> transaction, making it impossible to meet any particular deadline set in
> advance, for example, when the clients or servers are turned off or break
> for a few days?


I left out a lot details one of which is that an optimistic
async transaction model is used (post commit version check
not locking). No RPCs just async communication.