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

explore the use of a dedicated worker to manage the burner #87

Open
3 tasks
gregoryguillou opened this issue Aug 7, 2022 · 0 comments
Open
3 tasks
Labels
question Further information is requested

Comments

@gregoryguillou
Copy link
Contributor

Objectives

There are several reasons behind this exploration. One being security and the fact that dedicated workers should only be called by the script that has initiated it. The second being that the worker lifecycle could expand beyond the scope of a page reload.

Success Criterias

here again, we do not want to implement this in the burner for now but to explore the idea. What we need to check is:

  • create a dedicated worker from the extension and describe worker reload lifecycle. What is the scope of a variable, especially when dealing with page refresh
  • explore the possibilities to store data in localStore/sessionStore depending on the security/incognito options
  • explore the possibilities to store data in an encrypted cookie or any alternate mecasnism
@gregoryguillou gregoryguillou added the question Further information is requested label Aug 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant