Project:
| View Revisions: Issue #20059 | [ Back to Issue ] | ||
| Summary | 0020059: Menu caching design defects | ||
| Revision | 2012-03-20 12:37 by alostale | ||
| Steps To Reproduce | N/A | ||
| Revision | 2012-03-20 12:37 by alostale | ||
| Description | Menu is served as part of MainLayoutComponent, which eTag is calculated as language + role + module version (client application module!) This means menu is not updated in the following cases: *Menu is changed by adding/removing access to any window *A new module is added but version of client application is not changed |
||
| Revision | 2012-03-20 12:02 by alostale | ||
| Steps To Reproduce | - | ||
| Revision | 2012-03-20 12:02 by alostale | ||
| Description | Menu is served as part of Application js, which eTag is calculated as language + role + module version (client application module!) This means menu is not updated in the following cases: *Menu is changed by adding/removing access to any window *A new module is added but version of client application is not changed Another related topic is quick launch is attached to a datasource that uses MenuManager, a request is done first time on session the quick launch is used to retrieve the menu again. This should be possible to be avoided as the actual menu information is served on login. But in fact, currently this is doing the quick launch not to have this caching issue. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |