[fdo-dev] Classes and properties in SHP providers

[Dan Stoica]

> Currently, I've not discovered any better way of development of FDO
generic utils than checking for capabilities and react properly.

Checking the capabilities is a natural approach. It's just like writing
multi-platform code.

Dan.

-----Original Message-----
From: Mateusz Loskot [mailto:mateusz at loskot.net] 
Sent: Tuesday, October 31, 2006 2:09 AM
To: dev at fdo.osgeo.org
Subject: Re: [fdo-dev] Classes and properties in SHP providers

Haris Kurtagic wrote:
> I don't agree, I think every provider should implement data store
> command.
> In any case it can say: I am ok and ready to use that data store
>
> I would not prefer using OS commands.
> I think is much better to stay with FDO interface as much as possible,
> to be as much generic.

Generally, I'd agree but as I know from Robert Bray, data store commands
are not mandatory to implement by a provider.

> I would not like writing FDO client with bunch of "if that provider "

Currently, I've not discovered any better way of development of FDO
generic utils than checking for capabilities and react properly.

Cheers
-- 
Mateusz Loskot
http://mateusz.loskot.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe at fdo.osgeo.org
For additional commands, e-mail: dev-help at fdo.osgeo.org