[whatwg] Active workers when user leaves the page
robert at ocallahan.org
Fri Aug 8 15:29:37 PDT 2008
On Sat, Aug 9, 2008 at 7:01 AM, Jonas Sicking <jonas at sicking.cc> wrote:
> I do want to be agressive with killing workers when the user leaves a page
> since that makes for better user experience. However I'm also worried about
> stopping scripts halfway through breaking things and leaving the site with
> half-finished operations that are stored in databases or localStorage.
Aggressive killing of workers without warning when the user navigates away
would actually be a good feature.
There are various reasons outside anyone's control that a worker might die
abruptly. For example, power failure, browser crash, or "slow-script" style
timeout. Applications need to be able to handle those cases, for example by
using database transactions or careful use of atomic operations. But that's
hard to test and authors probably won't design or test well for those cases
since they're relatively uncommon. Expanding abrupt termination scenarios to
include navigate-away makes abrupt termination much easier to test, forces
authors to design for it early, and will ultimately simplify the application
design by reducing the different ways a worker can terminate.
This may sound a bit radical, but it's not a new idea. It's a principle
sometimes called "crash-only software". See e.g.
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg