Re: PL/SQL Cartridge Stateless ?

Very stateless. But all processes run as one connection, ever since the CGI-mode was superceeded by the WRB architecture in OAS 2.0.

We have implemented what we call "database cookies" to retain data values across sessions. The trick is to create a database table which has a session number, a field descriptor, and a data value field. each new screen session generates a sequence number that is stored in the session number. The other two fields are paired values, like "p_invoice_number" for the field descriptor and the actual value of the invoice number. We wrote a nifty cookie manager to simplify usage of this table. It is very important that you don't delete records once you're done with them; truncate the table periodically instead, as deletes cause space reclamation, which enques blocks with catastrophic consequences in a very high volume environment (as in crashing Oracle once an hour, in our experience with 30 concurrent users).

This works much safer and easier than client-side browser cookies, and all the I/O's on the database, where the PL/SQL cartridge is running anyway.

Send me a mail if anyone's really interested. Also, we're looking for developers out in Santa Clara, California.

larry_xu_at_ibm.net wrote:

> Hi
>
> I'm looking for a forum for Oracle Application Server. Can anybody with
> hands-on experience on PL/SQL Cartridge to clarify some of the concept
> regarding the PL/SQL cartridge.
>
> 1. Is PL/SQL cartridge stateless by definition?
> Even you try to set min instance > 0 and you won't actually have a session.
>
> 2. If point 1 is correct then, Is following description of
> PL/SQL cartridge TRUE?
>
> Once WRB dispatched the request to PL/SQL Cartridge,
> Cartridge located the DAD and did :
>
> a. Connect the database
> b. Exec the procedure and generate the HTML
> c. DISCONNECT FROM DATABASE IMMEDIATELY
>
> That simply means every request need at least a pair of
> Connection/disconnection. Will this overload the server ?
>
> Two OAS books and Oracle document did not explain this clearly. some web sit
> even explain it in just opposite
> http://www.customdb.com/ora_cartridge_facts.html )
> "PL/SQL cartridge provides declarative transactions, persistent connections
> where packages can hold a state, cursors remain open"
>
> Any comment ?
>
> Larry

--
    Rick Banister <rick_at_sesame.com>
    http://www.sesame.com
-------------------------------------------