CVS Account Request: cleong

As far as I know, and I might be wrong, ASP.NET uses a managed runtime .NET
interface which does not use COM (It's the actual TDS protocol implemented
in managed code). COM is viewed as poor way to run such interfaces both for
performance reasons and resource reference counting resources.

Andi

-----Original Message-----
From: Christian Wenz [mailto:chw@hauser-wenz.de]
Sent: Saturday, July 29, 2006 9:24 AM
To: internals@lists.php.net
Subject: [PHP-DEV] RE: CVS Account Request: cleong

Hi Andi,

ASP.NET is using OLEDB, as well, and in my experiences this
does not add to much penalty to communicating with MSSQL
(however obviously more exhaustive performance tests are
required). However I am wondering whether the OLEDB way would
still work on non-Windows PHP versions? If
not: Having two compatible, but internally completely
different MSSQL extensions for win32 and non-win32 sounds
dangerous to me.

--Christian

Hi Chung,

Any idea on the performance of OLEDB? My understanding was
that due to
it going through the COM layer, performance will be relatively poor.

Any idea?

Andi

-----Original Message-----
From: Chung Leong [mailto:chernyshevsky@hotmail.com]
mailto:chernyshevsky@hotmail.com%5D
Sent: Friday, July 28, 2006 2:37 PM
To: internals@lists.php.net
Subject: [PHP-DEV] CVS Account Request: cleong

I would like to submit a replacement for the Win32 mssql
extension
that I have recently completed. The extension provides
the same set
of functions as mssql, but uses OLEDB to talk to
SQLServer instead
of DBLIB. It allows users to retrieve varchar column
wider than 255
and also Unicode columns as UTF-8.

--
To
unsubscribe, visit: http://www.php.net/unsub.php