Difference between revisions of "Service Worker"
(→Other References) |
(→Context) |
||
| Line 7: | Line 7: | ||
*The simplest use of workers is for performing a computationally expensive task without interrupting the user interface. | *The simplest use of workers is for performing a computationally expensive task without interrupting the user interface. | ||
*The W3C and the WHATWG are currently in the process of developing a definition for an application programming interface ([[API]]) for web workers.<ref name="WHATWG"/> | *The W3C and the WHATWG are currently in the process of developing a definition for an application programming interface ([[API]]) for web workers.<ref name="WHATWG"/> | ||
| + | ==Problems== | ||
| + | *Native mobile apps deliver rich experiences and high performance, purchased at the expense of storage space, lack of real-time updates, and low search engine visibility.<ref>''Learn Everything About Progressive Web Apps.'' HTML Panda https://www.htmlpanda.com/blog/learn-everything-about-progressive-web-apps/</ref> | ||
| + | *Traditional web apps suffer from the inverse set of factors: lack of a native compiled executable, along with dependence on unreliable and potentially slow web connectivity. | ||
==Solution== | ==Solution== | ||
Revision as of 07:58, 18 May 2019
Full Title or Meme
A Service Worker, as defined by the World Wide Web Consortium (W3C) as a Web Worker and the Web Hypertext Application Technology Working Group (WHATWG), is a JavaScript script executed from an Web Site that runs in the background, independently of user-interface scripts that may also have been executed from the same HTML page.[1] Web workers are often able to utilize multi-core CPUs more effectively.[2] The W3C and WHATWG envision web workers as long-running scripts that are not interrupted by user-interface scripts (scripts that respond to clicks or other user interactions). Keeping such workers from being interrupted by user activities should allow Web pages to remain responsive at the same time as they are running long tasks in the background.
Context
- The simplest use of workers is for performing a computationally expensive task without interrupting the user interface.
- The W3C and the WHATWG are currently in the process of developing a definition for an application programming interface (API) for web workers.[1]
Problems
- Native mobile apps deliver rich experiences and high performance, purchased at the expense of storage space, lack of real-time updates, and low search engine visibility.[3]
- Traditional web apps suffer from the inverse set of factors: lack of a native compiled executable, along with dependence on unreliable and potentially slow web connectivity.
Solution
- Basic Service Worker Sample from Google to pre-cache script and other files for Web App.
References
- ↑ 1.0 1.1 Web Workers Web Hypertext Application Technology Working Group (2010-06-03)http://www.whatwg.org/specs/web-workers/current-work/
- ↑ web|url=https://html.spec.whatwg.org/multipage/workers.html#delegation%7Ctitle=HTML Living Standard (2017-01-30)
- ↑ Learn Everything About Progressive Web Apps. HTML Panda https://www.htmlpanda.com/blog/learn-everything-about-progressive-web-apps/
Other References
- Workers: an Introduction for Android
