Re: Oracle Webserver Experiences

From: Thomas Dunbar <tdunbar_at_gserver.grads.vt.edu>
Date: 1996/04/15
Message-ID: <31724BDF.2E67_at_gserver.grads.vt.edu>#1/1


Lane Sharman wrote:
>
> summersd_at_teleport.com (David Summers) wrote:
>
> >I am interested hearing from anyone actually using the Oracle Webserver
> >(preferablythe new 2.0 version).If we buy it, will we wish we had come up with
> >another solution? We are being led to believe that a major advantage is the
> >ability to call PL/SQL directly and avoid overhead. Is this reality or
> >'market-speak'?
> In my view, this is largely market-speak. The PL implementation from
> Oracle does not support streamed I/O; rather there is a function call
> for nearly every HTML operation. In summary, your processor and pages
> are going to show poor performance characteristics. Consider Oraperl.
> I have developed some fabulous private networks using this tool.

nonsense.

  1. you need not use the encapsulations of html (e.g. htp.para)..you're welcome to put tags in directly (ex: htp.p('first para <p> second <hr>')
  2. but that's really beside the point since the calls incur next to no cost since they're sitting (in compiled format) in the SGA after they get called the first time.
  3. Even back with WOW (the precursor to WebServer 1), it (ie WOW) was faster than using oraperl, not to mention a more convenient development env for experienced oracle users.
  4. with webserver 2.0, both startup time and ram usage is reduced since a new process neednt be started every time there is a cgi call.
  5. Oracle and various third parties have posted demo code that one can test to ensure performance is adequate.

the above is just wrt performance. development time is another matter but again, the WebServer solutions are superior, i think. For the parts of an application that require db interaction, robust enterprise-level, maintainable applications are easier to create in PL/SQL. Until WebServer 2.0, i will grant you that there was a gaping hole wrt pattern-matching support but that's now been taken care of (see privpat.sql package in OWS2).

   There are still places where Perl in general is the most suitable tool for WWW-Oracle development (generally where one needs to tie application in with other OS tools), but Oraperl is another matter.

  thomas   

>
> >We intend to use the web access for low to medium volume use (10-200 clients
> >with casual access) on an intranet datamart. This will probably be a secondary
> >access point: we expect the primary access to be SQL*Net/ODBC to PC based
> >spread sheet/database/other tools.
 

-- 
Thomas Dunbar    540 231-3938 (fax 3714)   http://gserver.grads.vt.edu/
Received on Mon Apr 15 1996 - 00:00:00 CEST

Original text of this message