Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keeping expensive computation out of main thread with Service Workers #39

Open
jwold opened this issue Feb 8, 2021 · 1 comment
Open

Comments

@jwold
Copy link

jwold commented Feb 8, 2021

Feature description

As a developer, I want to keep expensive computation out of main thread by using Workers to play back offline video, to download content, to sync posters, ...


Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

This is incredibly valuable to have to not pollute main JS thread with all this complexity, it should be a matter of a worker doing that job in parallel, but it would still work in the application if it didn't happen initially.

Implementation brief

QA testing instructions

Demo

Changelog entry

@jwold jwold added enhancement New feature or request WS: Performance Phase: 3 and removed enhancement New feature or request labels Feb 8, 2021
@jwold jwold added this to Backlog in Application Development via automation Feb 8, 2021
@jwold jwold moved this from Backlog to Blocked/Revisit Later in Application Development Feb 8, 2021
@jwold jwold added Phase: 1 and removed Phase: 1 labels Feb 10, 2021
@jwold
Copy link
Author

jwold commented Feb 10, 2021

Derek > We want to describe the problem more clearly. This is about separating the thread and having two separate threads and having worker in background to do the work. Needs more definition.

@jwold jwold added Phase: 2 and removed Phase: 3 labels Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Application Development
Blocked/Revisit Later
Development

No branches or pull requests

1 participant