I think I can live with targeting GeoServer 2.25.0, i.e option 1 is fine
for me.
Den mån 18 dec. 2023 kl 16:21 skrev Jody Garnett :
> I was not considering back porting as this is an API change? Admittedly
> only a protected API between superclass and implementation.
>
> If we really need to
I was not considering back porting as this is an API change? Admittedly
only a protected API between superclass and implementation.
If we really need to backport then option 2 is the only one.
--
Jody Garnett
On Mon, Dec 18, 2023 at 6:04 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com>
Hi,
I agree with contextualizing on Query the various "canXYZ" methods in
ContentFeatureSource, and agree on the implementation
that deprecates the method without any parameter, having the new one
delegate back. It fits just fine with the main branch.
However, I'm worried about the backports. We
Hi,
TL;DR - I propose to add query as parameter for capability methods like
canOffset in ContentFeatureSource to allow native optimization to be
implemented for specific categories of queries. See JIRA issue at (1).
Longer story,
I recently discovered that fetching larger datasets from static
