Bug 65890

Summary: [Chromium] Add a field for request identifier to Chromium's ResourceRequest.
Product: WebKit Reporter: Dmitry Titov <dimich>
Component: WebKit Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: fishd, jam
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Dmitry Titov
Reported 2011-08-08 16:55:58 PDT
This field will be used to plumb the unique WebCore identifier to the Chromium. We need the request's identifier associated with Chromium side structures to process WebCore notification that a resource in progress is transferred between pages. When this happens, WebCore informs the embedder about each request which is in progress, passing their unique identifier. In case of Chromium, the identifier will be used to map to the Chromium request representation, and it's routing_id should be updated to refer to the new RenderView object. If this is not doen, the request gets dropped when the original page closes. The http://crbug.com/55200 has more info on this. Most of the fix in in Chromium: http://codereview.chromium.org/7601011/, this patch is only a data field added to a ResourceRequest. Testing of this requires Chromium multiprocess architecture so the test is a part of the Chromium side of this fix.
Attachments
Patch (7.28 KB, patch)
2011-08-08 17:06 PDT, Dmitry Titov 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Dmitry Titov
Comment 1 2011-08-08 17:06:28 PDT
Created attachment 103318 [details] Patch
Dmitry Titov
Comment 2 2011-08-10 10:50:19 PDT
Comment on attachment 103318 [details] Patch Removing r? after chat with Darin Fisher. I'll try to do it in a different way, passing ResourceLoader into existing transferLoadingResourceFromPage notification.
Dmitry Titov
Comment 3 2011-08-12 13:56:37 PDT
Bug 66163 is now tracking the issue.
Note You need to log in before you can comment on or make changes to this bug.