Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Fast CGI or ODBC/JDBC
Guna Govind wrote:
>
> Hi
> we're running Oracle7.3.2. and Appache web server on Sun Solaris
> 2.5.1 on Ultra 1.
>
> Our clients needs to access the database through web browsers.
> Some of the applications want to monitor the database and they
> just keep querying every minute.
>
> Obviously, i don't want to do "CONNECT" and "EXIT" for every
> query, every minute. I'd like to keep the connection alive
> across the net. Is FastCGI the approach i should take or should i
> use ODBC/JDBC for this purpose (to keep the DB connection alive
> till i complete all my transactions.) ?
>
> What are the advantages and disadvantages ? I'm new to both
> FastCGI and the ODBC/JDBC.
>
> I really appreciate any information on this..
>
You can make a fastcgi process out of a java application which uses JDBC ( I tried this, worked,but no intensive testing). Advantages are: the JDBC classes don't need to load over the network, you could refresh the web page the fastcgi generates by with META EQUIV etc. (Of course you could do the fastcgi process in C, Perl, whatever)
Or you could write an applet (using Oracle's native jdbc driver), but
the jdbc classes are quite big (700 KB I think). The applet connects
directly
to the database.
ODBC is just for Intel platforms I think...? From Oracle there is a pure
java
jdbc driver (look on their web pages).
regards
Matthias
PGP Key available on request
![]() |
![]() |