I wanted to weigh in on this issue. I think any new driver really needs to be 100% managed code. C# seems to be the way people go with drivers and such (as opposed to VB.net or other language syntax).
Unmanaged code can sometimes hang a system in ways that managed code can not. That to me is the true benefit of a native driver. 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! Stephen Gutknecht -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, October 20, 2003 12:18 PM To: Dittmar, Daniel; [EMAIL PROTECTED] Subject: Re: RE: .NET data provider > > Does a .NET driver has to be 100% CLR/C# or could you use > C++ libraries? No, it doesn't have to be 100% managed code but that's my approach. My MySql driver is 100% managed and I have received many comments from folks appreciative of not being tied to a particular version of a client lib. [snip] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
