> dotNet has extensive tcp/ip sockets support, so there is no > reason that a > native driver can't be devised... other than not being able > to figure out > the MAXDB protocol!
There's always performance to consider. - local communication using shared memory is somewhat faster - at least Java doesn't allow to read integers from byte arrays directly. So to get at a four byte integer, you'll have to get 4 bytes (each with a check for array bounds) and combine them into an integer. When I compared early versions of the JDBC driver and the Python driver, the Python driver won by a wide margin. This gap has been narrowed, but only after several developer months. On the other hand, 100% managed code allows you to run unchanged on all the .NET platforms ;-). Daniel Dittmar -- Daniel Dittmar SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org/ -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
