Bug 160341

Summary: Transmit efficiently DocumentThreadableLoader ResourceResponse to its client
Product: WebKit Reporter: youenn fablet <youennf>
Component: WebCore Misc.Assignee: youenn fablet <youennf>
Status: NEW    
Severity: Normal CC: achristensen, cdumez, commit-queue, japhet
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Modifying ThreadableLoaderClient approach none

youenn fablet
Reported 2016-07-29 07:14:28 PDT
DocumentThreadableLoader is now filtering the response given by the CachedResource. This filtering requires a copy to not modify the CachedResource response. It might be good to use that copy for clients that want to keep the response, typically XHR and Fetch API
Attachments
Modifying ThreadableLoaderClient approach (20.76 KB, patch)
2016-07-29 07:17 PDT, youenn fablet 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
youenn fablet
Comment 1 2016-07-29 07:17:53 PDT
Created attachment 284865 [details] Modifying ThreadableLoaderClient approach
youenn fablet
Comment 2 2016-07-29 07:22:09 PDT
I am not terribly convinced by this patch. A better approach might be something like a takeResponse() method added to ThreadableLoader. This method would be used by clients storing a response, namely XHR and FetchResponse
Note You need to log in before you can comment on or make changes to this bug.