...
- Right now we collect some unit config settings (e.g.
RewriteListeners,AggregatedTags) into a collections, that are stored in kApplication class instance. If Also we cache all collections however we must create instances of all objects that store collections on In-Portal start even if they won't be used (e.g. aggregated tag list).
If we'll be implementing tag filter concept (see [template parser] Tag filter concept [5.3.0-B1]), then we'll have one more collection as a result. Currently collection adding and using isn't very straight forward process and we should work to make it easier to use
...
. To solve this we might need to separate cache into one, that is used at every page and other on-demand caches. However that might result in additional sql queries (1 extra sql query per cache restore) if Memcache isn't used.