Method and apparatus for accessing a data source from a client using a driver

1. A method to access a data source from a client using an open database connectivity driver (ODBC driver), the method comprising:

providing, at a client side, a data source name (DSN) to connect to the data source using the ODBC driver, the DSN comprising an identifier comprising a class of the data source, and at least one of a library or an application of the data source that implements a driver interface to access the data source; and

using the ODBC driver, at the client side, to interface between the client and an implementation, at the data source side, of a driver interface of a Component Object Model (COM) based application or library to access the data source based on the DSN, using the ODBC driver comprising:

establishing a connection between the client and the implementation via the ODBC driver using the DSN; and

marshaling calls from the client to the data source using the ODBC driver.

2. The method of claim 1 , further comprising:

establishing a second connection between a driver manager that manages at the client side and the implementation via the ODBC driver using the DSN.

3. The method of claim 2 , wherein using the ODBC driver to interface between the client and the implementation comprises:

forwarding data requests from the driver manager to the implementation using the ODBC driver.

4. The method of claim 2 , further comprising:

providing a connection string including a driver name for the ODBC driver and an identifier for the implementation.

5. The method of claim 4 , wherein establishing the connection comprises:

loading the implementation using the identifier of the implementation.

6. The method of claim 5 , wherein the identifier identifies class, and identifies applications or libraries that implement the driver interface.

7. The method of claim 1 , wherein the ODBC driver connects to a particular version of the data source which is configured on a Windows based system.

8. An apparatus to access a data source from a client using an open database connectivity driver (ODBC driver), the apparatus comprising:

at least one processor configured to:

provide, at a client side, a data source name (DSN) to connect to the data source using the ODBC drive, the DSN comprising an identifier comprising a class of the data source, and at least one of a library or an application of the data source that implements a driver interface to access the data source; and

use the ODBC driver, at the client side, to interface between the client and an implementation, at the data source side, of a driver interface to access the data source based on the DSN, wherein the at least one processor is configured to use the ODBC driver to:

establish a connection between the client and the implementation via the ODBC driver using the DSN; and

marshal calls from the client to the data source using the ODBC driver; and

a memory coupled to the at least one processor.

9. The apparatus of claim 8 , wherein the at least one processor is further configured to:

establish a second connection between a driver manager that manages the client and the implementation via the ODBC driver using the DSN.

10. The apparatus of claim 9 , wherein the at least one processor is configured to use the ODBC driver to:

forward data requests from the driver manager to the implementation using the ODBC driver.

11. The apparatus of claim 9 , wherein the at least one processor is further configured to:

provide a connection string to include a driver name for the ODBC driver and an identifier for the implementation.

12. The apparatus of claim 9 , wherein the at least one processor is configured to:

load the implementation using the identifier of the implementation.

13. The apparatus of claim 12 , wherein the identifier identifies class, and identifies applications or libraries that implement the driver interface.

14. The apparatus of claim 8 , wherein the ODBC driver connects to a particular version of the data source which is configured on a Windows based system.

15. A computer-program product to access a data source from a client, the computer-program product comprising:

a non-transitory computer-readable medium comprising code to:

provide, at a client side, a data source name (DSN) to connect to the data source using an open database connectivity driver (ODBC driver), the DSN comprising an identifier comprising a class of the data source, and at least one of a library or an application of the data source that implements a driver interface to access the data source; and

use the ODBC driver, at the client side, to interface between the client and an implementation, at the data source side, of a driver interface to access the data source based on the DSN, wherein the non-transitory computer readable medium comprises code to use the ODBC driver to:

establish a connection between the client and the implementation via the ODBC driver using the DSN; and

marshal calls from the client to the data source using the ODBC driver.

16. The computer-program product of claim 15 , wherein the non-transitory computer readable medium comprises code to use the ODBC driver to:

establish a second connection between a driver manager that manages at the client side and the implementation via the ODBC driver using the DSN.

17. The computer-program product of claim 16 , wherein the non-transitory computer readable medium comprises code to use the ODBC driver to:

forward data requests from the driver manager to the implementation using the ODBC driver.

18. The computer-program product of claim 16 , wherein the non-transitory computer readable medium comprises code to use the ODBC driver to:

provide a connection string including a driver name for the ODBC driver and an identifier for the implementation.

19. The computer-program product of claim 16 , wherein the non-transitory computer readable medium comprises code to use the ODBC driver to:

load the implementation using the identifier of the implementation.

20. The computer-program product of claim 19 , wherein the identifier identifies class, and identifies applications or libraries that implement the driver interface.