Decouple "decoded data" handling from ScriptResource |
|||
Issue descriptionDraft CL: https://chromium-review.googlesource.com/c/602606/ To resolve Issue 692856 , this issue tracks efforts to introduce ScriptResourceData. ScriptResource represents everything needed by the users of ScriptResource after loading finished, that is, almost everything needed by the users of ScriptResource except for ScriptStreamer. On load finish, ScriptResourceData is created (contains Request URL, ResourceResponse, SharedBuffer/String, etc.) and all other classes refer to ScriptResourceData, instead of ScriptResource directly. By doing so, revalidation of ScriptResource no longer affects ScriptResourceClients that are already notified of finish, because revalidation modifies ScriptResource, but doesn't modify the existing ScriptResourceData. In this way, this fixes Issue 692856 . Design doc to be written.
,
Aug 7 2017
Sounds great!
,
Aug 21 2017
I choose another short-term fix for Issue 692856 . Unblocking the related issues, making Pri-2, removing M-62 target. I postponed this issue, because I found more dependencies around CachedMetadataHandler.
,
Nov 14 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by hirosh...@chromium.org
, Aug 5 2017Labels: M-62