On Fri, May 30, 2014 at 6:58 PM, Mauro Bartolomeoli <
[email protected]> wrote:
> Hi,
> moving on on this, I tried the following approach:
> - created a new LimitingVisitor interface with getStartIndex and
> getMaxFeatures methods, to be used by visitor aware stores
> - changed UniqueVisitor to implement this interface and added pagination
> capabilities to the visitor if those two properties are defined (this will
> handle stores that are not visitor aware)
> - made JDBCDataStore aware of LimitingVisitor, using it to get limits in
> aggregated queries, if limits are defined in Visitor instead that in Query
>
> This way, the old behaviour is mantained if limits are defined in Query,
> the new one (limits applied after aggregation) if they are defined in the
> visitor.
>
> What do you think?
> Can I move forward with it?
>
Seems a good approach to me, would be nice to hear from the other core devs
(thinking Christian, Justin as jdbc module co-maintainer,
and Jody since he designed the visitors in the first place, but of course
anybody is warmly welcomed to provide feedback)
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
-------------------------------------------------------
------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
