I would go with FeatureSource as the "data access side" of the equation. I am also liking the code examples that are produced when you add it to FeatureCollection - but golly that class servers too many purposes as it is :-)
Andrea I am happy either way; want to write up a code example and choose yourself? Jody > FeatureSource and FeatureCollection are a more natural place, > but both have many implementations. FeatureSource seem to have > the easiest to deal with because it has "only" 8 top level > implementations where we could host a default null/emtpy set returning > method. FeatureCollection has a few more, a dozen as far I as I can > see (I'm speaking of 2.4.x here), but would have the advantage that > the honored hints may be dependent on the actual query performed, > whilst a method on FeatureSource could be only featuretype dependent. > > So, shall we add it to FeatureCollection? > Cheers > Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
