search

mfazliazran / webberig-applications-framework

Automatically exported from code.google.com/p/webberig-applications-framework
Other
0 stars 0 forks source link

Optimize Security::Allowed #8

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Please provide a description of your proposal
Each time Security::Allowed is used, it needs to perform a MySQL query. This 
function is often used in loops to check which modules are available to the 
user.

Every request contains several SQL queries that check this. Once 
Security::Allowed is called, it should retrieve all data and keep it in a 
variable. This should not be stored in the session.

What would be the benefit of this feature (ie. better usability,
performance, ...) ?
Possibly better performance

Original issue reported on code.google.com by math...@webberig.be on 14 Aug 2011 at 8:41

GoogleCodeExporter commented 9 years ago

Original comment by math...@webberig.be on 14 Aug 2011 at 8:55

GoogleCodeExporter commented 9 years ago 
Implemented changes in trunk - R33

Original comment by math...@webberig.be on 24 Sep 2011 at 10:54