Hogan, John wrote: > Hello Chris, > > I'm a tad puzzled here. What I'm hearing is that the thin driver is > actually an applet that gets downloaded to each client and then communicates > directly with oracle through sockets. Nope... The thin driver is not an applet, it is just java code that knows how to talkto the Oracle server... You can use it anywhere you can use Java code, but it will be subject to any network or security constraints of the environment it is run in. Those constraints would make it unsuitable for use as an applet, although if you went to extreme efforts you could do it... > If this is true, not only would the > thin driver be much slower, it would also be unsuitable for web apps that > have their databases behind a firewall. Also, if your using Oracle 8.1.5, > you're tied into using jdk1.1.8 becuase oci8 drivers for jdk1.2 are not > available yet. This is all proving true in testing, conversations with > Oracle tech support and Oracle's online documentation. Seems there's a > disconnect somewhere > I use the thin driver I downloaded from OTN every day on JDK1.2.x, works wonderful for me. It was a breeze to install and configure... Its the way JDBC should work.... And depending on how the connections between the c code are handled it is very possible for an all Java JDBC driver to outperform a java/native driver. The context switch from Java to native code is expensive, and unless handled perfectly can result in a Java/native combination being slower then an all Java version. -gabe
begin: vcard fn: Gabriel Lawrence n: Lawrence;Gabriel org: Kovair<br>The power to .wow your customers. adr: 2 North First Street ;;Suite 212;San Jose;Ca;95113-1202;USA email;internet: [EMAIL PROTECTED] title: Architect tel;work: (408) 491-9731 note: The power to .wow your customers. x-mozilla-cpt: ;0 x-mozilla-html: FALSE version: 2.1 end: vcard
