- From: Tomás Aparicio <notifications@github.com>
- Date: Sat, 28 Feb 2015 10:57:30 -0800
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Saturday, 28 February 2015 18:57:56 UTC
@jakearchibald Thanks for the reply If you take a look at this experimental library you will fastly take an idea about what I'm looking for... https://github.com/h2non/bock The idea is, essentially, to have more programmatic control about the worker live-cycle, to behave accordly from the worker consumer side, for example to react properly when the worker was eventually shutdown, in order to proceed with the scope synchronization, since the worker isolated scope was flushed. The need is not new in thread based programming: deal with data and state synchronization across thread. Indeed, web workers are strongly isolated by design, and that's fine, but also should provide alternative ways to make this more easy, specially in the case of Service Workers by its live-cycle nature --- Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/579#issuecomment-76540015
Received on Saturday, 28 February 2015 18:57:56 UTC