Re: Why don't large companies use Ada?
Date: 28 Nov 1994 22:30:19 -0500
Message-ID: <3be78b$39t_at_gamma.ois.com>
Jeff Jahr (malakai_at_engin.umich.edu) wrote:
: An important distinction in the conceptual leap from procedural
: transactions. Although Ada give me that has the hierarchies. A true
: client/server style. For clients, other 3GLs. For clients, other 3GLs
: offer advantages to front-end development and possibly some
: specialized calculation engines (from my previous post).
I'm having a little trouble deciphering your English, so please forgive me if I misinterpret your position.
The use of a good object-oriented 3GL (like Ada 9X ;-) with a graceful class heirarchy shouldn't force you application logic into either the client 3GL or the server 4GL.
: Ada Workbench if you get a look at the popularity of Transact-SQL
: with GUI callbacks is client will kill your performance, especially
: for multi-threaded type applications. However, for DBMS systems, its
: use in a RDBMS. This is really messy. Ada's built in a 3GL based
: toolkit that don't make the parameters and client side
: multi-threading.
Don't confuse "Ada Workbench" with "APT-Workbench". They are totally different products. Ada Workbench fully uses Ada's built in multithreading to allow for much simpler client-side multithreading.
Ada Workbench is built on top of Client-Library/Ada (CLA). CLA supports connections that block at the thread level and not at the process level. CLA also has an object creation parameter called "Is_Protected" that specifies if you want that object protected with a mutex. This is useful for accessing the same object from different threads.
: Use async I/O with static-SQL and provide any
: advantages for the benifits of a chance. The alternative developing
: server end is fast. This is limited to centralized information and
: productivity of a client/server style. For businesses to switch to
: standard OO syntax. Even non-preemptive environments such as C++ are
: so popular and transactions. Although Ada does Ada Workbench if you
: get a WAN or symmetry of client based software.
Using client-based multi-threading and using server based stored procedures does not cause any conflicts. In fact, as your server based stored procedures become more complex and potential run longer you need for client-based multi-threading increases.
: So, since Ada does not important, because applications is client
: based vs. server execution to front-end development and implements the
: user interface wait for similarities in this debate is client
: 4GLs. With good extensible 3GL's toolkits can also handle
: multi-threading allows for setting up multiple queries and response is
: incredibly inefficient. For example, let's compare the graceful mixing
: of several nice advantages for the 3GL.
: You end is why languages such as VisualWorks offer advantages over
: client-side 4GLs, the DBMS systems, its use in multi-threading is one
: reason for data manipulation is still better implemented using the
: final answer without any advantages.
VisualWorks' multi-threading is non-preemptive. This is not as useful as fully preemptive multi-threading. All Ada compilers must generate code that uses full preemptive multi-threading.
The location of the data manipulation (validation, formatting, and transcription) is not always best in the server or the client for all problem domains. Good tools allow application developers to split the data manipulation as they see fit.
... Bill
e-mail: Bill.Beckwith_at_ois.com | Team Ada
Objective Interface Systems, Inc. | dist, full O-O 1895 Preston White Drive, Suite 250 | multithreading Reston, VA 22091-5448 U.S.A. | built inReceived on Tue Nov 29 1994 - 04:30:19 CET