Hi Gabe,
Your comment on the expense of a Java to native code switch doesn't match up
with what I've seen using JNI. It's definitely more expensive than a direct
method call, but not as expensive as even a simple object allocation, for
instance (at least on Win32). Has your experience been different?
- Dennis
Gabriel Lawrence wrote:
>
> 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
___________________________________________________________________________
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
