[MGNLPER-52] Support async execution of result suppliers and result listing Created: 03/Sep/18 Updated: 31/Oct/18 Resolved: 30/Oct/18 |
|
| Status: | Closed |
| Project: | Periscope |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Cedric Reichenbach | Assignee: | Ilgun Ilgun |
| Resolution: | Done | 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
|
||||||||
| Documentation update required: |
Yes
|
||||||||
| Epic Link: | Periscope back-end MVP | ||||||||
| Sprint: | Basel 158, Basel 159 | ||||||||
| Story Points: | 8 | ||||||||
| Description |
|
Business benefit: Find Bar results come faster. Acceptance criteria:
More info: Currently, we're (synchronously) waiting for all results to load before we list anything, including REST ones fetched over the network. Obviously, some suppliers are much faster than others, so we should already list results while some are still loading. We might just want to distinguish between sync and async suppliers, such that sync ones would be executed and listed just like now, and async results would dribble in later. Perhaps async results should be completely separated from sync ones for usability reasons (preventing unexpected "jumps" once an async result arrives). |