Re: [Geotools-devel] maxFeatures in datasource?

[Chris H. <ch...@op...>]

Yeah, that is a little.  I realized that I wrote my maxFeatures code at a
time when I was still a newbie on geotools and wasn't ready to suggest
changes to the datasource interface, so I just put them in the
constructor.  As for the offset call, I'm not a huge fan, but that's more
or less because I don't need it for a wfs.  It seems like it might force
some datasource to just hold all their features in memory.  I guess with
jdbc you could just skip to the row of the offset.  What are the use cases
where you would want maxFeatures at an offset?  I'm open to it, as I can
just not use the offset, but it seems like it could be a hassle for some
datasources to implement, and an extra field for clients to figure otu,
without that many advantages.

Chris

On Mon, 7 Apr 2003, James Macgill wrote:

> At 02:26 PM 4/7/2003 -0400, you wrote:
> >How do people feel about a setMaxFeatures call in the datasource
> >interface?  It's an optional part of the Wfs GetFeature query.  If set
> >than a getFeature call would return a feature collection of size no more
> >than the set maxFeatures.
> 
> Erm, seems a little odd, I would feel happier with
> 
> getFeatures(filter, maxFeatures);
> 
> rather than:
> setMaxFilters(n);
> getFeatures(filter);
> 
> As that would be hard to make thread safe.
> 
> Actually, I suspect you need:
> getFeatrues(filter, maxFeatures, offset);
> 
> So that multiple calls would enable you to get all the features.
> 
> James 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: ValueWeb: 
> Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
> No other company gives more support or power for your dedicated server
> http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
> _______________________________________________
> Geotools-devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>