[MGNLUI-1503] Optimize AppLauncherLayoutManager.getLayoutForCurrentUser() Created: 31/May/13 Updated: 04/Jan/16 Resolved: 04/Jan/16 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | applauncher |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Tobias Mattsson | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
getLayoutForCurrentUser() is called very frequently. For each location change in fact. The layout does not change very often. It should be possible to optimise this by caching. Also, it is often called just to check if an app is in the layout, we could add a method that does only this. |
| Comments |
| Comment by Mikaël Geljić [ 04/Jan/16 ] |
|
Closing as obsolete as it will most likely be addressed in MGNLUI-3380. |