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.3 required=5.0 tests=BAYES_00,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: mfb@mbunix.mitre.org (Michael F Brenner)
Subject: Re: Ada and Distributed Objects - Seeking Success Stories
Date: 1997/05/06
Message-ID: <5kn91r$jio@top.mitre.org>#1/1
X-Deja-AN: 239743268
References: <336DC9E2.6350@netspace.net.au>
Organization: The MITRE Corporation, Bedford Mass.
Newsgroups: comp.lang.ada
Summary: How is this realtime?
Date: 1997-05-06T00:00:00+00:00
List-Id: <comp.lang.ada>


    > I am currently involved in a large real-time Ada project (1,000,000
    > SLOC) ... Distributed Object Manager ... client/server model ...
    > clients subscribe/register for passive objects that they are 
    > interested in and object managers at the servers automatically
    > distribute applicable updates to clients. All updates are
    > based on transactions. When a commit is performed at the server it
    > ... updates the object-space at the impacted clients. 

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?