[fdo-internals] providers.xml vs. FdoIConnectionInfo
traian.stanev at autodesk.com
Thu Feb 22 15:29:15 EST 2007
So basically it doesn't matter what the API calls return, since
Hammerhead would get the information from providers.xml.
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Mateusz
Sent: Thursday, February 22, 2007 3:14 PM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] providers.xml vs. FdoIConnectionInfo
Traian Stanev wrote:
> 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.
According to my understanding, the most important part of the
providers.xml registry is name + location of provider + its library.
Rest of information is only here for convenience, so it's not
required to scan and query every provider for these details, for
instance when application is about to list them in user-friendly way.
I had similar question when started to test my fdopostgis with the
Hammerhead. I revealed that when I put fdopostgis entry to the
providers.xml but the DLL is not available under specified path, the
Hammerhead doesn't complain but lists the fdopostgis in the Data Connect
Later, I was told that this behavior is intentional and providers should
not be loaded & queried on application launch. So, without these details
in the providers.xml, it would not be possible.
> Which copy of the information are applications supposed to use?
I think it depends if you want to load the provider or not.
> What if the two are out of sync?
I don't suppose this is a problem, except misinforming a user :-)
fdo-internals mailing list
fdo-internals at lists.osgeo.org
More information about the fdo-internals