Thursday 22 December 2005 3:49:49 pm
I wonder if its then wise to simply cache per user and hope that the extra filespace required is ok. But then you hit regeneration issues which simply wont scale with multiple users.... grrr. I recently added role support to the ezodcsm extension for menu popups, which i committed to pubsvn. This will increase the sql requests per node because of the permission checks in the templates but perhaps after caching it may help. With such checks i can restrict what the popup menu contains. I use the popup menu in other areas to help restrict functionality. For example on the big class icon i have a setting to hide or show the window controls (Relations, Locations, Translations...). By default they are off. If the user doesnt have permissions they dont see the option. To be frank the admin needs to be customisable per user per role. If im editor i dont want to see webshops, etc. If i may diverge, another thread discusses this type of optimisation: http://ez.no/community/forum/general/ez_speed_optimisation_faq Is there a way to combine the findings from this thread to that one? Everyone of us hits these problems time and time again. Paul
|