[BlobAsync] Moving async handling into BlobStorageContext & quota out.

net/log/net_log_event_type_list.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // NOTE: No header guards are used, since this file is intended to be expanded
 // directly into net_log.h. DO NOT include this file anywhere else.
 
 // In the event of a failure, a many end events will have a |net_error|
 // parameter with the integer error code associated with the failure.  Most
 // of these parameters are not individually documented.
@@ skipping 2054 matching lines @@
 
 // This event is emitted when Service Worker is destroyed before it
 // finishes responding with a blob.
 EVENT_TYPE(SERVICE_WORKER_ERROR_KILLED_WITH_BLOB)
 
 // This event is emitted when Service Worker is destroyed before it
 // finishes responding with a stream.
 EVENT_TYPE(SERVICE_WORKER_ERROR_KILLED_WITH_STREAM)
 
 // This event is emitted when a request to be forwarded to a Service Worker has
-// request body blobs, and it may be necessary to wait for them to finish
-// construction. The END phase event parameter is:
+// request body, and it may be necessary to wait for sizes of files in the body
+// to be resolved. The END phase event parameter is:
 //   {
-//     "success": Whether the request blobs finished construction successfully.
+//     "success": Whether file sizes in the request body have been resolved
+//     successfully
 //   }
-EVENT_TYPE(SERVICE_WORKER_WAITING_FOR_REQUEST_BODY_BLOB)
+EVENT_TYPE(SERVICE_WORKER_WAITING_FOR_REQUEST_BODY_FILES)
 
 // This event is emitted when a request failed to be forwarded to a Service
 // Worker, because it had a request body with a blob that failed to be
 // constructed.
 EVENT_TYPE(SERVICE_WORKER_ERROR_REQUEST_BODY_BLOB_FAILED)
 
 // The start/end of dispatching a fetch event to a service worker. This includes
 // waiting for the worker to activate and starting the worker if neccessary.
 //
 // The BEGIN phase consists of the following parameters:
@@ skipping 965 matching lines @@
 // {
 //   "current_position": <Shows current read position>,
 // }
 //
 // The END phase contains the following information:
 // {
 //   "result": <Result of reading. Result > 0 is bytes read. Result == 0 means
 //              the end of file. Result < 0 means an error.>
 // }
 EVENT_TYPE(UPLOAD_DATA_STREAM_READ)