On Sun, May 4, 2014 at 1:55 PM, Rahkonen Jukka (Tike) <
[email protected]> wrote:
> Hi,
>
> OK, with the startindex values I did not see that startindex is changing
> the sorting to alphabetical. Plain GetFeature with maxFeatures returns
> features in order states.1, states.2, states.3 but adding startindex is
> really changing the order into states.1, states.10, states.11.
>
> I perhaps agree that current behaviour is acceptable bu it is not logical,
> and Geoserver users must know that they must load data in pages always with
> startindex because startindex=0 does not return the sama data than if
> parameter is not used at all.
>
It may be counter-intuitive, I agree, but forcing a sort is the only way to
get stable paging across all data sources.
But of course, we initiate that only if the client shows an intent to page,
without a startIndex we avoid it to get better performance.
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
-------------------------------------------------------
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
