Enhancement
Server cache range results
Issue description
For some topic types (think master data) it would make sense to cache the range retrieval results as they are currently recomputed hundreds of times per day, always with the same result. Topic types vary in the instance growth rate. For some it is next to 0 and some grow by thousand each day. This scale is a better conceptualisation than the master data/movement data distinction.
Range requests could be partially satisfied from a cache as long as the instance count remains unchanged. Store events that invalidate the cached result are: adding a new instance, removing and instance, freezing, and unfreezing an instance of the respective type. Also changing the name of an instance.
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.