Hi Mukul,
Note that Thin drivers usually use direct socket connections to
their
databases and work in that manner. In many cases they are slower than
the Thick drivers which used the local client of the database which
communicates
with the database in several proprietery protocols which make them
faster.
Thin drivers do not need any database related native code other than the
driver
at the client side but as mentioned above Thick driver require a
Database client version
on the client.
Bye
Venkatesh
>As far I know, thin drivers are provided by database vendors that
>interfaces the application with database directly, and so are fast.
Thick
>drivers use for eg jdbc-odbc bridge.
>-mukul
>>
>>can any one explain the Thin and Thick driver concept.......
>>
>>Thanx in advance..
>>
>>Kumar
___________________________________________________________________________
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
