Push Notification, API, and bug fixes

NEW

• Push Notifiction: Now you can configure and use GCM Push Notifications Service.
• Push Notifiction API: You can use the API to listen for the Notification events, including the notification click.
• Few bugs fixed: We cleaned up the source code a little bit and fixed some bugs.
• Client API: Extra API methods.
• Fixed Method bug: Fixed problem for some rules, in requests that used the method POST.

Advantages

• Use of variables to build URLs and redirects
• Different strategies (offline-first, online-first or fastest)
• Easy-to-set rules for 404 pages, redirects, cache or use indexedDB, or outpus
• Trace requests to debug your configuration, rules and filters
• Decision over cache naming and versioning for each matching request
• Many named rules (for future debugging tooling...I imagine we can have a lighthouse-like page for debugging your service workers and your rules)
• Support for indexedDB
• Support for messaging and syncing events (under development)
• Quite simple JSON configuration and easy to start with the basic, or go further for more complex cases
• Client API with many possibilities
• API for Web Notifications
• Support (and API) for Push Notifications
• Support for opaque requests

Learning

Read the commented json configuration file: https://naschq.github.io/dsw/config-example.html

• How to install
• How to use it
• Push Notification support
  • Matching requests
  • Request Strategies
  • Possible actions for each request
    • Caching requests
    • Storing in IndexedDB
    • Tracing and debugging requests
• Drops/examples
  • Treating 404 pages
  • Treating 404 images
  • Caching requests
  • Uncacheable rules
  • Redirecting requests
  • Using variables in redirects
  • Caching everything
  • Caching static files
  • Bypassing requests
  • Sending credentials
• Using it programatically (require('dsw'))
• Client API
  • Notifications API
  • PUSH Notifications API
  • Connection Status API
• Contributing to the project