Render process changes for ResourceTiming sizes.

third_party/WebKit/Source/platform/network/ResourceResponse.h

Index: third_party/WebKit/Source/platform/network/ResourceResponse.h
diff --git a/third_party/WebKit/Source/platform/network/ResourceResponse.h b/third_party/WebKit/Source/platform/network/ResourceResponse.h
index d19e8520e992003c4e92c16e4ab97b4daa5edbe2..d2fe4014dfe5b06e536ae1f87ac0e6d943c89032 100644
--- a/third_party/WebKit/Source/platform/network/ResourceResponse.h
+++ b/third_party/WebKit/Source/platform/network/ResourceResponse.h
@@ -240,6 +240,12 @@ public:
     unsigned short remotePort() const { return m_remotePort; }
     void setRemotePort(unsigned short value) { m_remotePort = value; }
 
+    long long encodedBodyLength() const { return m_encodedBodyLength; }
+    void addToEncodedBodyLength(int value);
+
+    long long responseBodySize() const { return m_responseBodySize; }
+    void addToResponseBodySize(int value);
+
     const String& downloadedFilePath() const { return m_downloadedFilePath; }
     void setDownloadedFilePath(const String&);
 
@@ -366,6 +372,13 @@ private:
     // Remote port number of the socket which fetched this resource.
     unsigned short m_remotePort;
 
+    // Size of the response body in bytes prior to decompression.
+    long long m_encodedBodyLength;
+
+    // Sizes of the response body in bytes after any content-encoding is
+    // removed.
+    long long m_responseBodySize;

[kinuko, 2016/06/28 15:35:07]

The length/size terminology inconsistency bothers me a bit... looks like
encodedDataLength is existing terminology that's being used in Blink, but where
this 'responseBodySize' comes from? (I did quick code search but wasn't able to
find much precedence)

It's sad that we use different terminology depending on layers, but could we
still try to minimize # of variations?  Maybe... use the same terminology as
ResourceTiming (or encodedBodyLength and decodedBodyLength) here?

[Adam Rice, 2016/06/29 09:52:15]

I find it confusing that Response::decodedSize() exists and means something else
completely. I've chosen decodedBodyLength as it looks like the least-worst
alternative to me.

I've also updated the design doc to summarize the different names used at
different layers.

+
     // The downloaded file path if the load streamed to a file.
     String m_downloadedFilePath;
 
@@ -414,6 +427,8 @@ public:
     int64_t m_responseTime;
     String m_remoteIPAddress;
     unsigned short m_remotePort;
+    long long m_encodedBodyLength;
+    long long m_responseBodySize;
     String m_downloadedFilePath;
     RefPtr<BlobDataHandle> m_downloadedFileHandle;
 };