On 11/15/2011 11:17 AM, Carlos Garcia Campos wrote:
> The thing is that in WebKit2 we only have the information in the UI
> process, the network stuff happens in the Web process
Oh, right. So yeah, I agree that the second approach in your original
mail (expose individual bits of data rather than t
El mar, 15-11-2011 a las 09:15 -0500, Dan Winship escribió:
> On 11/15/2011 05:46 AM, Sergio Villar Senin wrote:
> > En 15/11/11 11:08, Carlos Garcia Campos escribiu:
> >> I'm currently working on downloads API for WebKit2 and I need to expose
> >> NetworkResponse which is not wrapped in WebKit2 AP
On 11/15/2011 05:46 AM, Sergio Villar Senin wrote:
> En 15/11/11 11:08, Carlos Garcia Campos escribiu:
>> I'm currently working on downloads API for WebKit2 and I need to expose
>> NetworkResponse which is not wrapped in WebKit2 API yet. In WebKit1 we
>> have WebKitNetworkRequest and WebKitNetworkR
El mar, 15-11-2011 a las 11:46 +0100, Sergio Villar Senin escribió:
> En 15/11/11 11:08, Carlos Garcia Campos escribiu:
> > I'm currently working on downloads API for WebKit2 and I need to expose
> > NetworkResponse which is not wrapped in WebKit2 API yet. In WebKit1 we
> > have WebKitNetworkReques
En 15/11/11 11:08, Carlos Garcia Campos escribiu:
> I'm currently working on downloads API for WebKit2 and I need to expose
> NetworkResponse which is not wrapped in WebKit2 API yet. In WebKit1 we
> have WebKitNetworkRequest and WebKitNetworkResponse, which are mostly
> the same because a SoupMessa
I'm currently working on downloads API for WebKit2 and I need to expose
NetworkResponse which is not wrapped in WebKit2 API yet. In WebKit1 we
have WebKitNetworkRequest and WebKitNetworkResponse, which are mostly
the same because a SoupMessage represents both a request and response.
So, both Networ
