| |
Introduction to Eloquence
Eloquence initially started in 1989 as a porting environment to move
HP250/HP260
applications to HP-UX. Since then Eloquence has gone through continued
development.
The Eloquence product consists of the following four major components:
- The Eloquence programming language (based on HP Business Basic)
- The Eloquence database (based on IMAGE)
- Several user interfaces, ranging from terminals to GUI and Web.
- Development tools.
Eloquence is available on the HP-UX, Linux and Windows platform
and supports a wide range of installations: From a single user laptop
to a few hundred users, a terminal based to a distributed GUI
environment and data base sizes of 20+ GB.
The Eloquence TurboIMAGE compatibility API is relatively new to
Eloquence. It started as a low profile project back in 1999 and
has since then been fully integrated in the distribution.
It aims at providing almost 100% compatibility with existing HPe3000
applications.
The new Eloquence B.07.00 release provides substential improvements
regarding TurboIMAGE support.
-
Native support of TurboIMAGE item types (such as K, P and Z).
This makes sure the utility programs (eg. dbimport) know about
those types and index order is as expected.
-
Enhanced IMAGE limits. Eloquence implements or suceeds the
TurboIMAGE limits.
-
Improved TurboIMAGE compatibility.
-
Support for TurboIMAGE compatible TPI functionality.
-
Extended logging facilities (forward recovery)
-
Structural maintenence
The Eloquence data base architecture
The Eloquence data base is a client/server based architecture.
All data base access is performed by the data base server on behalf
of the applications. The application can use the Eloquence
native API or the
TurboIMAGE intrinsics (with the the TurboIMAGE compatibility
option) to access the data base.
The Eloquence database is based on IMAGE and the TurboIMAGE compatiblity
does not result in a performance impact.
Additional features of the Eloquence database include:
- Integrated indexing capabilities.
- We do not use hashing. So there are no "migrating secondaries"
and no set level locking is required in order to add or delete an
entry from a master set.
- Capacity is no longer relevant. The Eloquence database
grows dynamically when required (including master data sets).
- Additional locking capabilities.
- Comprehensive set of database utilities including structural maintenance.
- Multiplatform (HP-UX, Windows NT/2000, Linux).
- Network transparent.
- Dynamic, nested transactions, transaction isolation
(uncommitted changes are not visible to other processes).
- Deadlock detection and recovery.
- On-line backup.
- Enhanced security subsystem.
- The Eloquence data base does not reside in the file system
but uses volume files which reside in the file system
as a container for the data and structural information.
- We don't use a ROOT file. Structural information are kept in the
data base (in the system catalog).
Additional information:
|
|
