[fdo-internals] providers.xml vs. FdoIConnectionInfo

[Traian Stanev]

May be then we should only store a list of paths to DLLs in the
providers.xml?

Traian


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jack Lee
Sent: Thursday, February 22, 2007 3:07 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] providers.xml vs. FdoIConnectionInfo

Hi Traian,

Applications should use the methods from the FdoIConnectionInfo class.
The providers.xml file is not documented and should not be access
directly. 


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: February 22, 2007 2:46 PM
To: FDO Internals Mail List
Subject: [fdo-internals] providers.xml vs. FdoIConnectionInfo

Hi,

FdoIConnectionInfo exposes the following functions:

    FdoString* GetProviderName()
    FdoString* GetProviderDisplayName()
    FdoString* GetProviderDescription()
    FdoString* GetProviderVersion()
    FdoString* GetFeatureDataObjectsVersion()
    

The same information is also available in the providers.xml file entry
for the provider.

Which copy of the information are applications supposed to use? What if
the two are out of sync?



Traian


_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals

_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals