PTAL,
japhet@ as a platform/loader OWNER,
horo@ who might be familiar with CachedMetadata; this CL assumes that CachedMetadata is received from disk cache, if any, always after ResponseReceived() and before NotifyFinished(), possibly before or after the first DataReceived(). Is this assumption correct?
kouhei@ for scripting,
rmcilroy@ mythria@ leszeks@ FYI, this CL will change the lifetime of CachedMetadataHandler and thus affect V8 code caching statistics.
To view, visit change 786410. To unsubscribe, or for help writing mail filters, visit settings.
+yhirano@ also as a loading OWNER.
Hiroshige Hayashizaki would like Yutaka Hirano to review this change.
Create CachedMetadataHandler when a response is received
This CL creates CachedMetadataHandler when a response is received,
instead of creating when a Resource is constructed.
This is to
- Prepare for removing the reference from CachedMetadataHandler to
Resource in [1]. The data needed for CachedMetadataHandler is
available when a response is received, but not available when
the Resource is created. Also, this CL makes the lifetime of
CachedMetadataHandler match with the period where the corresponding
ResourceResponse is set in Resource::response_.
- Enable CachedMetadataHandler even after revalidation.
Previously, CachedMetadataHandler was cleared on failed revalidation
and was never re-created after that.
This CL creates a new CachedMetadataHandler everytime a
ResourceResponse is received, and thus re-creates a
CachedMetadataHandler on failed revalidation.
Bug: 784875
Change-Id: Ia32f5772cbd5970734f67098f235c2a1428b46ea
---
M third_party/WebKit/Source/platform/loader/fetch/Resource.cpp
M third_party/WebKit/Source/platform/loader/fetch/ResourceTest.cpp
2 files changed, 8 insertions(+), 10 deletions(-)
Patch set 8:Code-Review +1
Patch set 9:Code-Review +1
Patch set 10:Code-Review +1
Patch set 10:Commit-Queue +2
Hiroshige Hayashizaki uploaded patch set #11 to this change.
Create CachedMetadataHandler when a response is received
This CL creates CachedMetadataHandler when a response is received,
instead of creating when a Resource is constructed.
This is to
- Prepare for removing the reference from CachedMetadataHandler to
Resource in [1]. The data needed for CachedMetadataHandler is
available when a response is received, but not available when
the Resource is created. Also, this CL makes the lifetime of
CachedMetadataHandler match with the period where the corresponding
ResourceResponse is set in Resource::response_.
- Enable CachedMetadataHandler even after revalidation.
Previously, CachedMetadataHandler was cleared on failed revalidation
and was never re-created after that.
This CL creates a new CachedMetadataHandler everytime a
ResourceResponse is received, and thus re-creates a
CachedMetadataHandler on failed revalidation.
[1] https://chromium-review.googlesource.com/791494
Bug: 784875
Change-Id: Ia32f5772cbd5970734f67098f235c2a1428b46ea
---
M third_party/WebKit/Source/platform/loader/fetch/Resource.cpp
M third_party/WebKit/Source/platform/loader/fetch/ResourceTest.cpp
2 files changed, 8 insertions(+), 10 deletions(-)
To view, visit change 786410. To unsubscribe, or for help writing mail filters, visit settings.
Patch set 11:Commit-Queue +2
CQ is trying the patch.
Note: The patchset sent to CQ was uploaded after this CL was approved.
"Edit commit message" https://chromium-review.googlesource.com/c/786410/11
Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/chromium-review.googlesource.com/786410/11
Bot data: {"action": "start", "triggered_at": "2017-12-15T23:36:05.0Z", "cq_cfg_revision": "b547f51ef97353cccb06eebcda71133909f61295", "revision": "ed2d90d9406bfc721ec74a8afbcaabca61aa8371"}
Commit Bot merged this change.
Create CachedMetadataHandler when a response is received
This CL creates CachedMetadataHandler when a response is received,
instead of creating when a Resource is constructed.
This is to
- Prepare for removing the reference from CachedMetadataHandler to
Resource in [1]. The data needed for CachedMetadataHandler is
available when a response is received, but not available when
the Resource is created. Also, this CL makes the lifetime of
CachedMetadataHandler match with the period where the corresponding
ResourceResponse is set in Resource::response_.
- Enable CachedMetadataHandler even after revalidation.
Previously, CachedMetadataHandler was cleared on failed revalidation
and was never re-created after that.
This CL creates a new CachedMetadataHandler everytime a
ResourceResponse is received, and thus re-creates a
CachedMetadataHandler on failed revalidation.
[1] https://chromium-review.googlesource.com/791494
Bug: 784875
Change-Id: Ia32f5772cbd5970734f67098f235c2a1428b46ea
Reviewed-on: https://chromium-review.googlesource.com/786410
Commit-Queue: Hiroshige Hayashizaki <hiro...@chromium.org>
Reviewed-by: Tsuyoshi Horo <ho...@chromium.org>
Reviewed-by: Yutaka Hirano <yhi...@chromium.org>
Reviewed-by: Kouhei Ueno <kou...@chromium.org>
Reviewed-by: Nate Chapin <jap...@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524540}
---
M third_party/WebKit/Source/platform/loader/fetch/Resource.cpp
M third_party/WebKit/Source/platform/loader/fetch/ResourceTest.cpp
2 files changed, 8 insertions(+), 10 deletions(-)