On Sun, May 26, 2019 at 8:01 PM Kevin Smith <[email protected]> wrote:
> There is a "Direct Integration Mode" setting which will cause requests > to GeoServer's regular WMS endpoint that have "tiled=true" set to check > if GWC can handle them, and if not they are handled normally. I don't > recommend relying on this as it is far to easy to end up bypassing the > cache without realizing it. I don't recommend turning this on as it > just leads to silent changes in behaviour. > Eh, certain functionality is liked by some and hated by others. At GeoSolutions we use direct integration a lot, enable it basically always, and check the response HTTP headers to verify if a request got tile-cached or not (you get a hit/miss information, and in case of miss, a miss reason). This allows to use just one protocol for most requests, the base request is cached, but when an advanced user comes in and adds filtering options, view params, or other elements that make the tile contents different, and depending on the configuration, non cacheable, then you still get a tile, but a non cached one (with a reason for it not being cached in the HTTP headers, as well). One gets a nice mix of tiles cached for the common user, and on the fly tile production for the minority of advanced users. It's certainly a mode that requires extra discipline to be used properly, the onus is on the client developer to be a bit more careful. The monitoring subsystem also reports if a certain request was cached or not, allowing for monitoring of cache % in direct mode requests (a useful second level check, sometimes a change in configuration makes tiles that were cacheable, no longer so). Cheers Andrea == 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
