Re: PL/SQL Cartridge Stateless ?

It is my understanding that it is indeed stateless, even though connections to the DB are supposedly maintained in a pool either by the cartridge or the WRB. For our needs I created a number of tables and packages on the back end to handle session mgmt., user mgmt., authentication and authorization, emailing out of Oracle, etc. When the user logs in I store a session row for them and update it with every request. That combined with cookies allows me to keep track of what they are doing, restore a session after a browser crash, etc. If there's a better way to manage state with a system based on the PL/SQL cartridge, I'd be glad to hear about it.
- bill c.

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
Received on Tue Jun 08 1999 - 21:01:27 CEST