Releases 2.2 and 2.3 provided the following new and updated features:
Thread Safety
OO4O release 2.2 and higher is thread-safe and can be used effectively in
multithreaded applications and environments.
Using the Connection Pool Management Facility
OO4O 2.3 introduces a new interface for pooling of database connections. The
pool may be created with zero or more OraDatabase objects and can grow to a maximum that is specified at the time the pool is
created. Connections in the pool are automatically closed if not used for a
specified time.
This facility is essentially a resource manager for OraDatabase objects containing database connections. This facility maintains the open
state on frequently used objects, and thereby eliminates the need to continuously
create and destroy connections. It is particularly useful in heavily used
mid-tier application server components such as ASP scripts in IIS that connect to
Oracle databases to execute queries on every invocation. New OraDatabase objects are created only if there are more objects required than are
available in the pool, thus, significantly improving performance and scalability.
For an example of this in IIS, please refer to the ASP sample directory
located in the ORACLE_BASE\ORACLE_HOME\oo4o\iis directory.
PL/SQL Multi-Cursor Return
Releases of OO4O from v2.2 can return multiple cursors to the client from a
single query. This is useful, for instance, if a user needs the result set of two
disjointed queries.
This feature improves performance by lowering network traffic. OO4O's PL/SQL
table return capability can send (or receive) an array of values with a single
network transaction. Only a single network round-trip is required for returning
data from multiple cursors.
Tips and Techniques for Performance Tuning
Field collection access in a dynaset is improved. If loops are not coded
properly, the system is optimized to create default field collection objects so that
these objects are not created and destroyed with each dynaset iteration.
The help file now contains a number of tips and techniques for improving
performance. Coding methods, such as early binding of OO4O objects and dynaset cache tuning, can significantly improve performance.
A number of bug fixes are included. The eradication of some bugs, such as very
small memory leaks, represent significant gains when OO4O is used in a 7-by-24
environment.
General
OO4O is available on Windows '95 and NT, and can run in an NT server
environment. There will not be any 16-bit version from OO4O 2.2 onwards, and the current
16-bit OO4O 2.1 has now entered maintenance mode.
