Service Worker: Cache.put() consumes request/response bodies

Source/modules/serviceworkers/Body.h

Index: Source/modules/serviceworkers/Body.h
diff --git a/Source/modules/serviceworkers/Body.h b/Source/modules/serviceworkers/Body.h
index 6aa5d1c39fcc6a74998ddb962447c16312105007..d5b03b540e3383b9cdfb084ffe578e1cb453fbf4 100644
--- a/Source/modules/serviceworkers/Body.h
+++ b/Source/modules/serviceworkers/Body.h
@@ -43,6 +43,9 @@ public:
     ScriptPromise json(ScriptState*);
     ScriptPromise text(ScriptState*);
 
+    // Sets the bodyUsed flag to true. This signifies that the contents of the
+    // body have been consumed and cannot be accessed again.
+    void setBodyUsed();

[gavinp, 2014/11/13 19:35:02]

Should we put this after bodyUsed() so the order matches that of Body.cc? I'm a
huge fan of definition order following declaration order. Blink coding style
doesn't discuss this, although Chromium and Google C++ style is for definition
order to follow declaration order.

Better yet, why not just inline these?

[jsbell, 2014/11/13 21:16:05]

Inlined, to minimize diff.

     bool bodyUsed() const;
 
     // ActiveDOMObject override.
@@ -55,10 +58,6 @@ protected:
     // Copy constructor for clone() implementations
     explicit Body(const Body&);
 
-    // Sets the bodyUsed flag to true. This signifies that the contents of the
-    // body have been consumed and cannot be accessed again.
-    void setBodyUsed();
-
 private:
     ScriptPromise readAsync(ScriptState*, ResponseType);
     void resolveJSON();