-
Epic
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
-
ui push scalability
-
Empty show more show less
Context
See the notes from UHZ for pain points and initial findings
Questions for discovery
- Align with UI team: what improvements have been made already and identify remaining gaps. Effort was tracked in epic MGNLUI-7761. How much does that cover the needs of UZH, where do we still have room for improvements?
- How does UZH leverage hierarchical definition of user rights to improve to improve UI push scalability? See MultisiteJcrDataSourceObservation.java
and some comments re. this approach from rkovarik here: https://jira.magnolia-cms.com/browse/MGNLUI-6342?focusedId=339631&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-339631 - (How) can this be generalised?
- Do we even have to generalise it (and how much) or could we just recommend hierarchical user rights as best practice for multi site? (User who don't follow this won't get the scalability benefits).
- relates to
-
-
- Open
-
-
MGNLUI-7749 Reduce grid refresh rate
-
- Closed
-
-
MGNLUI-7762 Ability to disable JCR auto-observation
-
- Closed
-
-
MGNLUI-6342 Do not refresh grids in inactive apps and make DatasourceObservation extendable
-
- Closed
-
-
MGNLUI-8448 Review and improve exposed API method
-
- Open
-
-
-
- Closed
-
-
-
- Closed
-
- links to
