Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-6443

Use push instead of polling to update search results

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • 6.2.6
    • 6.2.5
    • None
    • UI FW 18 (christmas), UI FW 19
    • 8

      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.
      Depending on network latency, these requests may take some time to complete. E.g. 100 - 200 ms.
      This may results in Admin Central UI becoming very sluggish and sometimes impossible to navigate as long as the search is running.

      Problem statement

      The polling could be endless with very long searches over large repositories.

      Solution

      Replace polls with a push.

      Together with MGNLUI-6398 this should solve MGNLPER-135

       

        Acceptance criteria

              sdemocko Šimon Demočko
              soenke.schmidt Sönke Schmidt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoR

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - Not Specified
                    Not Specified
                    Logged:
                    Time Spent - 3h 29m
                    3h 29m