[Webkit-unassigned] [Bug 65890] New: [Chromium] Add a field for request identifier to Chromium's ResourceRequest.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=65890

           Summary: [Chromium] Add a field for request identifier to
                    Chromium's ResourceRequest.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: dimich at chromium.org
                CC: fishd at chromium.org, jam at chromium.org


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.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.