| Reference | Help | Introduction | Slide Show | Class Hierarchy | InterClient | ||
| PREV | NEXT | FRAMES | NO FRAMES | ||
Similar to class 1 except we're bridging directly to the database's native C client library rather than to odbc. So the closer the client library is to cli, the more amenable it is for the driver.
DBMS client library provides client/server
We're still a language driver, because we're still bridging from java to c. The jdbc driver is in java, and the dbms client library is in C.
This is the most common architecture for language drivers, eg. IBPerl, written by our very own Bill Karwin, has this architecture.
Although interclient, which is a class 3 driver, is faster than class 2 drivers. In general, class 2 drivers are the the fastest class of drivers because they use the native C libraries and protocols which have been around a while and have been finely tuned. So why is a class 2 driver architecture not the best architecture for java drivers? Well, it turns out there's a problem with this architecture on the Java platform...
| Reference | Help | Introduction | Slide Show | Class Hierarchy | InterClient | ||
| PREV | NEXT | FRAMES | NO FRAMES | ||