[COMPASS-4517] Spike how to move the shell code execution to a background process in Compass Created: 25/Nov/20 Updated: 29/Oct/23 Resolved: 17/Dec/20 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Investigation | Priority: | Major - P3 |
| Reporter: | Massimiliano Marcon | Assignee: | Sergey Petushkov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | COMPASS-3935 | ||||||||
| Documentation Changes: | Not Needed | ||||||||
| Sprint: | Iteration Rambutan, Iteration Star Apple | ||||||||
| Description |
|
To avoid making the shell block the Compass UI in certain conditions, we want to be able to put the shell runtime in a background thread/worker. With this investigation we want to build a proof of concept to see and better estimate the amount of work needed to build a full implementation of a shell runtime that works in a separate thread. The proof of concept should explore the following areas:
|
| Comments |
| Comment by Githook User [ 22/Dec/20 ] |
|
Author: {'name': 'Sergey', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}Message: feat: Expose connection params of the native client through the data service
|
| Comment by Githook User [ 08/Dec/20 ] |
|
Author: {'name': 'Sergey Petushkov', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}Message: feat( |
| Comment by Githook User [ 07/Dec/20 ] |
|
Author: {'name': 'Sergey', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}Message: feat(
|