[webkit-qt] QtQuick WebView and QNetworkAccessManager

Jocelyn Turcotte jocelyn.turcotte at digia.com
Thu Dec 6 06:07:37 PST 2012

On Thu, Dec 06, 2012 at 01:03:52PM +0100, Alberto Mardegan wrote:
> On 12/06/2012 12:19 PM, Jocelyn Turcotte wrote:
> >This is something that makes sense to add in future versions, I think that it's too late for 5.0 though.
> >There would be no way to set different values on individual WebView of the same process, since there is only one WebContext instance per application.
> Ah, then it wouldn't solve my problem.
> >For what kind of use do you need the cookie jars to be independent?
> Ubuntu Online Accounts: we perform OAuth authentications on behalf
> of applications; in order to support multiple accounts for the same
> website, we have a cookie jar per account.

Ok, I'm not aware of this kind of use case being on the roadmap.
The only way I could see this being possible in the near future would be that you allow only one WebView to load at a time, and that we add some WKCookieManager* alike API to reset the cookies each time you want to show a different account.

The backend of WebKit2 is still moving a lot. For example with Apple currently doing work to have all the networking done in a separate NetworkProcess, to allow multiple WebProcesses. It's difficult to see a way to expose the QNetworkAccessManager in the public API the same way that it is with WebKit1.

Sorry of not being of better help.
If you can think of something missing in the API that could also help others, and would like to help, please come chat on #qtwebkit.

// Jocelyn

More information about the webkit-qt mailing list