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 webworker #17

Open
psychemedia opened this issue Dec 7, 2024 · 0 comments
Open

Explore webworker #17

psychemedia opened this issue Dec 7, 2024 · 0 comments

Comments

@psychemedia
Copy link
Contributor

pglite has support for a multi-tab webworker. Would this make sense?

In JupyterLab or Jupuyterlite, we may have several notebooks open in different JupyterLab panels, and each of these notebooks may want a database?

Also, if we are using notebook rather than JupyterLab, each separate notebook will be running in its own tab. Once again, what are advantages and disadvantage of using a worker? Indeed, would a worked be necessary? What if different notebooks want to access the same database, from their own panel in the same JuptyerLab environment, or from separate notebook browser tabs? Or what if each notebook was accessing a different database? Should it haves its own worker? I think we could start different databases by options, so is the worker just there to keep down the number of threads?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant