Reys, Ellen wrote:
Fred,
You are right about the Type 2 Driver, however:
Correct me if I am wrong, but I thought that a Type 3 Driver is a pure Java
driver that translates JDBC calls into a database-independent network
protocol, and this protocol is implemented using a middleware server (third
party vendor).
This is the correct definition of a type 3 driver. This is what IBM provides with DB2 UDB v7.x and earlier: the db2jd daemon acts as the middleware server.
You can also get 3rd party Type 3 drivers (Merant sells one). The primary difference between Type 2 and Type 3 drivers is the location of the native client code (e.g. the DB2 Runtime Client). Type 2 drivers use the client code on each client machine; Type 3 drivers only require client code on the middleware server.
A Type 4 is a pure Java driver that uses a native protocol to convert JDBC calls into the database server network protocol. Using this type of driver, the application can make direct calls from a Java client to the database. A type 4 driver, is what typically offered by the database vendor.
The Type 4 driver was released as part of DB2 UDB v8.1. IBM was a little slow in bringing this driver to market, probably related to the fact that they completely redesigned the client in V8. Good luck, - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
