Re: [w3ctag/design-reviews] Extended lifetime shared workers (Issue #1089)

xiaochengh left a comment (w3ctag/design-reviews#1089)

Hi @domenic, thanks for pointing out the resource cost for preparing a shared worker to have an extended lifetime. There is a concern we previously raised that isn't addressed yet:

What if developers set `extendedLifetime: true` to every shared worker just to be "safe" (as it won't break any app) without realizing the resource cost of doing so?

Since using a shared worker causes so many detailed issues (like mismatching options, reconnection, etc), should we instead introduce a new type of worker that is designed for this use case? Namely, a worker dedicated to one page but has extended lifetime.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1089#issuecomment-2978793878
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1089/2978793878@github.com>