In Portal, can you control how a slow event layer or a slow query layer gets cached?
- For example, only re-query the source every 5 minutes? And use cached data in between re-queries.
- And re-query ahead of time in the background, to avoid waiting for the slow layer to load (the data would be pre-loaded).
It seems like that kind of thing would solve a lot of issues with slow layers. It'd basically precompute the data.
Does that functionality exist in Portal? (I’m not a Portal manager, I’m just curious.)
More info here: Event layers/query layers: Control caching settings for better performance
