Hi Paul, as far as I know, the plugin does not do any internal caching. However, it sets an HTTP header so that the client would do some caching of the response, see:
https://github.com/geoserver/geoserver/blob/d6d3d258351cb5a229c538edb9527921789cb9da/src/extension/sldService/src/main/java/org/geoserver/sldservice/rest/ClassifierController.java#L187 The default value is "600" seconds, or 10 minutes. You can set the "cache" parameter in your request to change it, and eventually set it to zero. See also the parameters here: https://docs.geoserver.org/stable/en/user/extensions/sldservice/index.html#classify-raster-and-vector-data Cheers Andrea On Wed, Sep 30, 2020 at 10:52 AM Paul Wittle < paul.wit...@dorsetcouncil.gov.uk> wrote: > Hi, > > > > I have a database view which I’m changing in the database using a process. > The plan is to use the SLD REST plugin to calculate the Natural Jenks for > the data in the view then make a change which alters the view and re-run > the Natural Jenks process a second time. The result should be two different > Natural Jenks results. > > > > Whilst the two requests will be sent separately; it is likely that the > GeoServer may hold a persistent connection and potentially cache some of > the process in RAM or some other temporary memory and hopefully the process > will not be slow; so the requests may be within a minute of each other. > > > > Does anyone know if this will work or will the GeoServer fail to recognise > that the min/max values have changed in the underlying data between the > requests? > > > > If the answer is that it might not re-request the data from the database; > is there a way to force a layer to have no caching at all, even in RAM? > > > > Thanks in advance for any tips. > > Paul > This e-mail and any files transmitted with it are intended solely for the > use of the individual or entity to whom they are addressed. It may contain > unclassified but sensitive or protectively marked material and should be > handled accordingly. Unless you are the named addressee (or authorised to > receive it for the addressee) you may not copy or use it, or disclose it to > anyone else. If you have received this transmission in error please notify > the sender immediately. All traffic may be subject to recording and/or > monitoring in accordance with relevant legislation. Any views expressed in > this message are those of the individual sender, except where the sender > specifies and with authority, states them to be the views of Dorset > Council. Dorset Council does not accept service of documents by fax or > other electronic means. Virus checking: Whilst all reasonable steps have > been taken to ensure that this electronic communication and its attachments > whether encoded, encrypted or otherwise supplied are free from computer > viruses, Dorset Council accepts no liability in respect of any loss, cost, > damage or expense suffered as a result of accessing this message or any of > its attachments. For information on how Dorset Council processes your > information, please see www.dorsetcouncil.gov.uk/416433 > _______________________________________________ > 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 > -- Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- *Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.*
_______________________________________________ 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
