Implement updateViaCache flag and no-cache by default for main service worker scripts

content/browser/service_worker/service_worker_registration.h

Index: content/browser/service_worker/service_worker_registration.h
diff --git a/content/browser/service_worker/service_worker_registration.h b/content/browser/service_worker/service_worker_registration.h
index bdf2c4026ba5cd98a0ab9e729c91335ca9017eeb..ff8011c3a9d61c2aced72088aad5d4fe2eb82926 100644
--- a/content/browser/service_worker/service_worker_registration.h
+++ b/content/browser/service_worker/service_worker_registration.h
@@ -51,11 +51,13 @@ class CONTENT_EXPORT ServiceWorkerRegistration
   };
 
   ServiceWorkerRegistration(const GURL& pattern,
+                            bool use_cache,
                             int64_t registration_id,
                             base::WeakPtr<ServiceWorkerContextCore> context);
 
   int64_t id() const { return registration_id_; }
   const GURL& pattern() const { return pattern_; }
+  bool use_cache() const { return use_cache_; }
 
   bool is_deleted() const { return is_deleted_; }
   void set_is_deleted(bool deleted) { is_deleted_ = deleted; }
@@ -194,6 +196,7 @@ class CONTENT_EXPORT ServiceWorkerRegistration
                          ServiceWorkerStatusCode status);
 
   const GURL pattern_;
+  const bool use_cache_;

[nhiroki, 2017/03/28 06:49:51]

Why don't you use ServiceWorkerRegistrationOptions::UseCache?

[yuryu, 2017/03/28 07:07:02]

I thought it would make sense to align the type with ServiceWorkerRegistration
in the spec
https://w3c.github.io/ServiceWorker/#serviceworkerregistration-interface

If this alignment is not necessary, I'll change it to
ServiceWorkerRegistrationOptions::UseCache.

[nhiroki, 2017/03/28 07:21:50]

IMO, we don't have to make the implementation completely aligned with the spec
if the implementation is much clearer and the user-facing behavior is not
changed.

[yuryu, 2017/07/20 10:15:12]

Acknowledged.

   const int64_t registration_id_;
   bool is_deleted_;
   bool is_uninstalling_;