Forms runtime as cartridge?

Question

In a document from July 1997 from Oracle called "Developer/2000
and the NCA: An Architectural Overview", authors Mark Doran et
al, the future direction of the Forms Runtime was stated to be:
In a release after 2.0, the Forms Runtime will be implemented
as a cartridge. The Web Application Server will invoke a
Forms cartrige directly to run a Forms application, elim-
inating the ned for a separate Listener process and Runtime
processes. In this configuration, the Forms cartridge will
be able to exploit all of the functionality of the Web
Application Server, including Inter-Cartridge Exchange
(ICX) and dynamic load balancing.
Initially, each instance of the Cartridge will handle a single
connected user, just as the Forms Runtime does today, but
in later versions a single cartridge will be able to serve
multiple simultaneous users for even greater scalability.
I have two questions:
a) is this still the intended direction of the Forms Runtime?
(I couldn't find this repeated in later documents)
b) if so, which release will/does have this feature?
I have scoured all the promotional documentation for OAS 4.0
and Developer 6.0 looking for an answer, but could not find
any.
The reasons I care are that 1) our client will continue to grow,
and the scalability improvement is interesting, and 2) if
you can use Inter-Cartridge Exchange to (I think) access
real CORBA objects which live in a custom-built application
cartridge that lives in OAS 4.0. From Forms, you have to
use Forms-specific syntax to access functions, and you
can't access objects directly.
null

Answer 1

I agree.
I've tested my application using Dev2.1 to find out that each
user was going to take up around 10M.
We have a user base of about 300, but usually theres only about
80 users on during our busiest time. 80Users * 10M = 800M.
Thats not even counting the memeory needed for the reports
server.
But to be fair OAS load balancing did cut down on apps which
were inactive.
But this still leaves me with the prospect of at least a 512M
apps server. Which might be incredibly slow during peak times.
So I started looking towards the OAS4.0 release which had this
promised shared cartridge architecture. But it looks as if we
are going to have to upgrade to Dev6.0 to use this cartridge
architecture.
What happened to Dev2.1?
I received the Dev6.0 beta CD, and was imressed by OAS4.0.
Should we just skip the Dev2.1 / OAS3.0 or are there going to be
further releases of Dev2.x supporting OAS4.0?
null