I'd recommend on stored procs if your application's gonna be
database-intensive. You may also eliminate the need for 3rd
layer (application server or a separate server pages processor)
by using Oracle PSP (for small and rather static design projects)
or our Dynamic PSP (for anything bigger than some 10-20 screens).
Both run within Oracle itself and interface with the HTTP servers
taking requests from them and feeding back complete HTML in
response. Oracle includes Apache-based HTTP server and mod_plsql
module for calling stored procedures and feed results to web client and
we have created an IIS4/5 filter for the very same purpose (though it's
designed specifically for Dynamic PSP and may not be compatible with
Oracle PSP).
--
Vladimir Zakharychev (bob@dpsp-yes.com) http://www.dpsp-yes.com
Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications.
All opinions are mine and do not necessarily go in line with those of my employer.
"Rusty Wright" <rusty_at_socrates.Berkeley.EDU> wrote in message
news:uie66aupqhv.fsf_at_socrates.Berkeley.EDU...
> Can anyone recommend a book, web page, etc. that explains the pros and
> cons of using stored procedures, as opposed to putting the code in
> your front-end code? The background info is that a group of us are
> designing a database and we'll be using Oracle, and for the front-end
> we'll be using a web interface probably with the PHP scripting
> language as the glue.
>
> One of the people on the team is a proponent of using stored
> procedures and another is against it. Obviously, none of us are
> database experts and I'd like to be able to read up on stored
> procedures so that we can argue the issue intelligently.
>
> Thanks
Received on Sat Sep 08 2001 - 10:42:41 CDT
