It makes no sense to use a wmts service with variable parameters as the whole point of tiling is to allow you to cache the response. If everyone makes a different request each time there is no point in caching the tiles.
Ian On Thu, 13 Dec 2018, 17:17 mlebihan <mlebiha...@gmail.com wrote: > My problem is that the url parameters send by the browser in viewparams and > that are automatically split by geoserver in WMS mode and given to its SQL > views that way : SELECT * FROM TABLE where a= ... AND b = ... > (and may change each time the user do a call to that layer through his web > browser. Example : cityCode and year who would varying each call), > > aren't taken into account when the a WMTS service is targeted instead. > > What troubles me is that if the way of sending parameters is well > documented, and it should not have been an easy thing to develop for the > geoserver team, the way for doing so for a WMTS layer should be known by > someone. > > I'm searching the official way to do so. I am not alone over the Internet > who have met that problem. It would be strange if I was discovering it in > the end of 2018, have to do experiments and offer a solution that would > surely not convince my development team. They wouln't allow my code to go > in > production if I attempt to use an undocumented practice. > > I am not the one who can discovery it now. I must rely on official > knowledge > about linking parameters send in WMTS mode and SQL requests in geoserver. > > Maybe, if nothing is known, I will open an improvment request, but I don't > have the right (due to our quality checkings here) to attempt an > undocumented trick never experienced by anyone. Because my quality service > would reply to me : "/How many days will it works ?/", "/Where have you > read > about this practice ?/". If I reply : /"I have hacked it, but saw noone do > the same before/", my commit will be rejected for sure. > > Regards, > > > > -- > Sent from: > http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html > > > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
