For cases like the following:
Could some optional settings be added to a layer's properties to boost performance?
I wonder if that kind of thing might be useful for cases where a dynamic layer is slow or doesn't need to be real-time (to avoid unnecessary database hits).
It would be a lot more convenient to control that sort of thing in the application, instead of setting things up in the back-end via materialized views, triggers, scheduled tasks, etc.. And the user could toggle it on or off as needed, depending on the use case. Whereas if it's done in the back-end, the user doesn't have any control over how the data behaves in their map...in terms of currency, caching, etc..
I suppose some of the things I suggested might already be available: Set caching options.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.