Sounds like a decent approach.
The only wrinkle is the ContentDataStore implements currently work with a
supports yes/no approach that involves applying a wrapper if required. It
strikes me this transformation thing is going to be similar to the filter
support, a backend may support a partial transformation requiring us to
"split" the work between server and client.
--
Jody
Jody Garnett
On Mon, Apr 14, 2014 at 2:04 AM, Andrea Aime
<[email protected]>wrote:
> On Sun, Apr 13, 2014 at 4:25 PM, Jody Garnett <[email protected]>wrote:
>
>> For something this important/cool it we good to have more than one
>> datastore in position to implement.
>>
>
> I was thinking that ContentDataStore could "easily" get support for that
> by using the TransformFeatureSource
> (and as a result, have that new feature supported right away in jdbc and
> shapefile stores, and also the incoming
> wfs-ng) however, that would require that code to be moved from its own
> module to gt-data or gt-main (and of
> course, a candidate to do the work).
> Hmm...
>
> Cheers
> Andrea
>
> --
> ==
> Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
> for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
