already cached in the user object. When 1.6 is released, we will only
> I want to add the question:
> Will 1.6 cache the ACL data (like the menus data is cached in system
> cache)? Right now it produces tons of queries which can significantly
> slow the system with lots of users.
> I think that system cache should cache menus data, modules data and
> ACL data. Can help with the patch.
> On Sep 1, 5:54 pm, klas berlič <klas.ber...@gmail.com> wrote:
>> Currently in 1.5. we have quite a few cache related problems / bug/ feature
>> not implemented. As I will be working on those issues in the following weeks
>> it would be probably good to transfer those improvements to 1.6. or even to
>> first implement them in 1.6. and the backport them to 1.5. as Sam suggested?
>> To name few of them:
>> CMS level
>> a) cache is not implemented at all in core component except com_content
>> b) module cache usable only for modeules that stay the same on all pages. If
>> cache is enabled any module->framework interaction is totally disabled.
>> Framework level
>> Only file cache is fully implemented, all others are only half done (e.g. no
>> cache clean method)
>> So, what I would like to ask is:
>> a) is this work needed (or am I missing some information that changes my
>> perception)
>> b) Is somebody else on this or part of this?
>> c) Should I work on 1.5. issues first or vice versa?
>> P.S. please also advise if I should post this on some other list
