[MGNLUI-6443] Use push instead of polling to update search results Created: 07/Dec/20 Updated: 07/Oct/21 Resolved: 05/Jan/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2.5 |
| Fix Version/s: | 6.2.6 |
| Type: | Task | Priority: | Major |
| Reporter: | Sönke Schmidt | Assignee: | Šimon Demočko |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | performance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 3h 29m | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||||||||||
| Epic Link: | UI framework implementation | ||||||||||||||||||||||||
| Sprint: | UI FW 18 (christmas), UI FW 19 | ||||||||||||||||||||||||
| Story Points: | 8 | ||||||||||||||||||||||||
| Description |
|
Running searches against a very big workspace using info.magnolia.periscope.search.jcr.JcrSearchResultSupplier might take a considerable amount of time. Especially during the initial search after logging in to Admin Central. E.g. as soon as you log in, a search is run against the website workspace without a query term. As long as the search is running Vaadin UIDL requests are constantly sent to Magnolia. Problem statementThe polling could be endless with very long searches over large repositories. SolutionReplace polls with a push. Together with
|