This is absolutely untrue, the thin driver is the one that Oracle recommends
for large, high-traffic, java applications.  It is very fast, and totally
simple to set up.  On the other hand, the OCI driver requires far more
resources and is much harder to install.  It is also far less stable than
the thin driver.
    (*Chris*)

----- Original Message -----
From: Hogan, John <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 10, 1999 5:17 AM
Subject: Re: JRun/jsdk question


> Yes, but isn't this only true for the thin driver?  The thin driver will
> have much slower performance and isn't well suited for large web site use
>
> JohnH
>
> -----Original Message-----
> From: Chris Pratt [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 09, 1999 10:33 PM
> To: [EMAIL PROTECTED]
> Subject: Re: JRun/jsdk question
>
>
> That's true because of the change in security model, but you can download
> the 8.1.6 drivers that are compatible with Java2 from Oracle's Web Site.
>     (*Chris*)
>
> ----- Original Message -----
> From: Hogan, John <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, November 09, 1999 8:50 AM
> Subject: Re: JRun/jsdk question
>
>
> > Andy,
> >
> > I'd love to hear I'm wrong on this.  But as I interpert it, the
> > compatibility info on Oracle's technet site says that the oci8 driver
for
> > Oracle 8.1.5 is not compatible with jdk1.2
> >
> > John Hogan
> >
> > -----Original Message-----
> > From: Andy Bailey [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, November 09, 1999 11:12 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: JRun/jsdk question
> >
> >
> > > All,
> > >
> > > We needed to revert the version of the jdk we're using to jdk1.1.8 for
> > > compatibility with our database drivers.  I was was wondering if
anyone
> > can
> > > tell what versions of JRun and the jsdk we should be using?   Thank
you
> > >
> > > John Hogan
> > > iCast.Com
> > >
> > Why, your JDBC drivers should run ok under JDK1.2.x anyway. Mine
certainly
> > do.
> >
> > Andy Bailey
> >
> >
>
___________________________________________________________________________
> > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> > of the message "signoff SERVLET-INTEREST".
> >
> > Archives: http://archives.java.sun.com/archives/servlet-interest.html
> > Resources: http://java.sun.com/products/servlet/external-resources.html
> > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
> >
> >
>
___________________________________________________________________________
> > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> > of the message "signoff SERVLET-INTEREST".
> >
> > Archives: http://archives.java.sun.com/archives/servlet-interest.html
> > Resources: http://java.sun.com/products/servlet/external-resources.html
> > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
> >
>
>
___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
>
___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to